{2025.06}[GCCcore/14.3.0] modkit v0.6.4 - #1543
Conversation
|
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
|
|
bot: build repo:eessi.io-2025.06-software instance:eessi-bot-mc-aws for:arch=x86_64/amd/zen3 |
|
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
|
|
Haswell builds randomly fail while compiling libraries: |
|
bot: build repo:eessi.io-2025.06-software instance:eessi-bot-mc-aws for:arch=x86_64/intel/haswell |
Unable to download or merge changes between the source branch and the destination branch. |
|
bot: build repo:eessi.io-2025.06-software instance:eessi-bot-mc-aws for:arch=x86_64/intel/haswell |
|
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
|
|
New job on instance
|
|
Another build attempt on Haswell fails with: Note that the previous build attempt failed with error: could not compile |
|
Setting target-cpu=native --> target-cpu=x86-64 or even target-cpu='' in $RUSTFLAGS via a post_prepare_hook through interactive builds did not resolve the failure. |
|
I could also reproduce this on a haswell node. I tried several things, and suddenly it worked with This reproduces the issue. Also on a generic node this fails for me, so I don't understand how that worked in this PR, maybe we were really lucky? Let's retry that with the bot. |
|
bot: build repo:eessi.io-2025.06-software instance:eessi-bot-mc-aws for:arch=x86_64/generic |
|
New job on instance
|
|
And, as Richard mentioned, it fails at another crate almost every time, so it's really unpredictable/random. Sometimes the error is just something like: But I also got this one a few times: Setting |
|
Also reproduced it on a clean (manually launched) VM, same instance type ( worked fine... But then I tried it again, and it failed at the 5th attempt: Going to try and update some OS packages, let's see if that makes any difference... |
|
Upgraded all the packages, rebooted the VM, and reran the test. It failed again (at attempt 13). Meanwhile, the generic build on the same node type succeeded again. I'm utterly confused... |
missing packages: