{2023.06}[2023a] acpype v2023.10.27#1332
Conversation
|
bot: build repo:eessi.io-2023.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
|
|
AmberTools 23.6 is picking up the wrong Python: |
79112a9 to
ef843c4
Compare
easystacks/software.eessi.io/2023.06/eessi-2023.06-eb-5.2.0-2023a.yml
Outdated
Show resolved
Hide resolved
|
bot: build repo:eessi.io-2023.06-software instance:eessi-bot-mc-aws for:arch=x86_64/amd/zen2 |
|
New job on instance
|
easystacks/software.eessi.io/2023.06/eessi-2023.06-eb-5.2.0-2023a.yml
Outdated
Show resolved
Hide resolved
|
bot: build repo:eessi.io-2023.06-software instance:eessi-bot-mc-aws for:arch=x86_64/amd/zen2 |
|
New job on instance
|
|
bot: build repo:eessi.io-2023.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
|
|
This is the status of all the
|
|
🫤 |
|
The very last test timed out: |
|
Let's try it again, it wouldn't be the first case where it works the second time... bot: build repo:eessi.io-2023.06-software instance:eessi-bot-deucalion for:arch=aarch64/a64fx |
|
New job on instance
|
|
Sincerely, considering the comments they have in the code for the test itself, i would not feel to bad ignoring this test. This test seems to be doing the roundtrip check for ~14k files in the Also up to try and debug this but would need access to the machine to play with the code. |
|
Got access to Deucalion to test and OFC running it in an interactive job worked 😅 EDIT: for clarity i started an interactive job and than built the OpenBabel with BUILD SCRIPT
export OMP_NUM_THREADS=${SLURM_CPUS_PER_TASK}
module --force purge
source /cvmfs/software.eessi.io/versions/2023.06/init/bash
module load EESSI-extend
ROOTDIR=/projects/I20240007/crivella
eb test.eb \
--failed-install-logs-path $ROOTDIR/failed-logs \
--rebuild -rUsed EB shell output
This is my eb --show-config
Is the bot doing anything different, or should we just run it until it passes ? TEST REPORT
All the test before takes less than 1 s each (beside one that took 10s) |
|
@Crivella The best way to test with the configuration like the bot uses is to use |
|
Yeah that was with EESSI extend (modified the install dir from $HOME to avoid hitting the 25k file limit) |
|
So also running the test manually inside an I am for either retrying this build 1~2 more times and if it fails again i can try and make an hook to ignore the test... More detailsInside
|
|
bot: build repo:eessi.io-2023.06-software instance:eessi-bot-deucalion for:arch=aarch64/a64fx |
|
bot: build repo:eessi.io-2023.06-software instance:eessi-bot-deucalion for:arch=aarch64/a64fx |
|
New job on instance
|
|
bot: build repo:eessi.io-2023.06-software instance:eessi-bot-deucalion for:arch=aarch64/a64fx |
|
New job on instance
|
|
bot:status last_build |
|
This is the status of all the
|
5 similar comments
|
This is the status of all the
|
|
This is the status of all the
|
|
This is the status of all the
|
|
This is the status of all the
|
|
This is the status of all the
|
No description provided.