Skip to content

Mark PPC64LE Fedora Stable Clang as unstable#696

Merged
vstinner merged 1 commit intopython:mainfrom
encukou:fedora-clang-unstable
Mar 31, 2026
Merged

Mark PPC64LE Fedora Stable Clang as unstable#696
vstinner merged 1 commit intopython:mainfrom
encukou:fedora-clang-unstable

Conversation

@encukou
Copy link
Copy Markdown
Member

@encukou encukou commented Mar 31, 2026

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
Copy link
Copy Markdown
Member

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

Copy link
Copy Markdown
Member

@vstinner vstinner left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@vstinner
Copy link
Copy Markdown
Member

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

@zware
Copy link
Copy Markdown
Member

zware commented Mar 31, 2026

Current incident: https://www.githubstatus.com/incidents/ml7wplmxbt5l

@vstinner
Copy link
Copy Markdown
Member

"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).

@vstinner vstinner merged commit 6fc5c7c into python:main Mar 31, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants