Mark PPC64LE Fedora Stable Clang as unstable

[encukou]

This buildbot has been failing for a while; unfortunately it looks like the clang bug is not getting backported (upstream nor in Fedora).

@stratakis, does that sound right?

We should mark the builder unstable until clang 22 hits the repos.

[vstinner]

Sadly I failed to get a fix (at least on Fedora) when I asked two months ago at: llvm/llvm-project#179695.

[vstinner]

LGTM

[vstinner]

I tried to merge the change but I got a server error :-( If I try again, it fails with "Merge already in progress" ?!

[zware]

Current incident: https://www-githubstatus-com.sihan.fun/incidents/ml7wplmxbt5l

[vstinner]

"PPC64LE Fedora Stable Clang 3.x" is affected and uses clang 21.1.8.

"PPC64LE Fedora Rawhide Clang 3.x" doesn't seem to be affected even it uses clang -Og. It uses clang version 22.1.1.

"PPC64LE Fedora Stable Clang Installed 3.x" and "PPC64LE Fedora Rawhide Clang Installed 3.x" are not affected because they build Python in release mode (clang -O3).

[stratakis]

This buildbot has been failing for a while; unfortunately it looks like the clang bug is not getting backported (upstream nor in Fedora).

@stratakis, does that sound right?

We should mark the builder unstable until clang 22 hits the repos.

For the time being it seems the request for the fix is not resolved, I'll see if I can get a fix pushed in upstream and/or Fedora.