-
Notifications
You must be signed in to change notification settings - Fork 72
{2025.06}[2025a] LLVM 20.1.7 #1318
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
PetrKralCZ
commented
Nov 24, 2025
|
These are also part of #1257, but LLVM has some build issues that need to be resolved first. |
|
Let me trigger a build test, it's probably worth fixing whatever problems we have with LLVM through this PR and make #1257 a bit smaller? bot: build repo:eessi.io-2025.06-software instance:eessi-bot-mc-aws for:arch=x86_64/amd/zen2 |
|
New job on instance
|
easystacks/software.eessi.io/2025.06/eessi-2025.06-eb-5.1.2-2025a.yml
Outdated
Show resolved
Hide resolved
|
bot: build repo:eessi.io-2025.06-software instance:eessi-bot-mc-aws for:arch=x86_64/amd/zen2 |
|
New job on instance
|
|
bot: build repo:eessi.io-2025.06-software instance:eessi-bot-jsc for:arch=aarch64/nvidia/grace |
|
New job on instance
|
|
bot: build repo:eessi.io-2025.06-software instance:eessi-bot-mc-aws for:arch=aarch64/generic |
|
New job on instance
|
|
This is an excerpt of the failures in #1318 (comment) Details
Curious to see with #1318 (comment) if this is |
|
The generic build also has 36 failed tests: |
|
~20 of those should be ignored, the rest seems to be the same as for the grace test, so I would say they are |
Test errorsBOLTSince BOLT is the optimizer i would probably ignore these errors to avoid blocking the PR
FuzzerIt seems the fuzzer tests that are failing, are not sucessfully triggering a stack overflow that is expected to be caught by the sanitizer. libomptarget
Known failure as in
needs fix upstream. LLDB-unit
|
easystacks/software.eessi.io/2025.06/eessi-2025.06-eb-5.1.2-2025a.yml
Outdated
Show resolved
Hide resolved
|
bot: build repo:eessi.io-2025.06-software instance:eessi-bot-jsc for:arch=aarch64/nvidia/grace |
|
New job on instance
|
|
@Thyre Verified that also happen on a non-EESSI build, so it is only the BOLT failures that seems to be EESSI specific. I would still go for ignoring them for now to avoid blocking everything depending on LLVM, but might need more looking into for the future |
easystacks/software.eessi.io/2025.06/eessi-2025.06-eb-5.1.2-2025a.yml
Outdated
Show resolved
Hide resolved
|
bot: build repo:eessi.io-2025.06-software instance:eessi-bot-mc-aws for:arch=x86_64/amd/zen2 |
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
Some jobs failed in the "check missing" step, while the builds themselves actually succeeded: Rerunning those... bot: build repo:eessi.io-2025.06-software instance:eessi-bot-mc-aws for:arch=x86_64/intel/icelake |
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
bot: build repo:eessi.io-2025.06-software instance:eessi-bot-mc-aws for:arch=x86_64/intel/haswell |
|
New job on instance
|
|
Staging PR merged. |