Open trz42 opened 1 month ago
Instance eessi-bot-mc-aws
is configured to build:
x86_64/generic
for repo eessi-hpc.org-2023.06-compat
x86_64/generic
for repo eessi-hpc.org-2023.06-software
x86_64/generic
for repo eessi.io-2023.06-compat
x86_64/generic
for repo eessi.io-2023.06-software
x86_64/intel/haswell
for repo eessi-hpc.org-2023.06-compat
x86_64/intel/haswell
for repo eessi-hpc.org-2023.06-software
x86_64/intel/haswell
for repo eessi.io-2023.06-compat
x86_64/intel/haswell
for repo eessi.io-2023.06-software
x86_64/intel/skylake_avx512
for repo eessi-hpc.org-2023.06-compat
x86_64/intel/skylake_avx512
for repo eessi-hpc.org-2023.06-software
x86_64/intel/skylake_avx512
for repo eessi.io-2023.06-compat
x86_64/intel/skylake_avx512
for repo eessi.io-2023.06-software
x86_64/amd/zen2
for repo eessi-hpc.org-2023.06-compat
x86_64/amd/zen2
for repo eessi-hpc.org-2023.06-software
x86_64/amd/zen2
for repo eessi.io-2023.06-compat
x86_64/amd/zen2
for repo eessi.io-2023.06-software
x86_64/amd/zen3
for repo eessi-hpc.org-2023.06-compat
x86_64/amd/zen3
for repo eessi-hpc.org-2023.06-software
x86_64/amd/zen3
for repo eessi.io-2023.06-compat
x86_64/amd/zen3
for repo eessi.io-2023.06-software
aarch64/generic
for repo eessi-hpc.org-2023.06-compat
aarch64/generic
for repo eessi-hpc.org-2023.06-software
aarch64/generic
for repo eessi.io-2023.06-compat
aarch64/generic
for repo eessi.io-2023.06-software
aarch64/neoverse_n1
for repo eessi-hpc.org-2023.06-compat
aarch64/neoverse_n1
for repo eessi-hpc.org-2023.06-software
aarch64/neoverse_n1
for repo eessi.io-2023.06-compat
aarch64/neoverse_n1
for repo eessi.io-2023.06-software
aarch64/neoverse_v1
for repo eessi-hpc.org-2023.06-compat
aarch64/neoverse_v1
for repo eessi-hpc.org-2023.06-software
aarch64/neoverse_v1
for repo eessi.io-2023.06-compat
aarch64/neoverse_v1
for repo eessi.io-2023.06-software
Instance eessi-bot-mc-azure
is configured to build:
x86_64/amd/zen4
for repo eessi-hpc.org-2023.06-compat
x86_64/amd/zen4
for repo eessi-hpc.org-2023.06-software
x86_64/amd/zen4
for repo eessi.io-2023.06-compat
x86_64/amd/zen4
for repo eessi.io-2023.06-software
bot: build repo:eessi.io-2023.06-software arch:x86_64/amd/zen3
eessi-bot-mc-aws
(click for details)eessi-bot-mc-azure
(click for details)New job on instance eessi-bot-mc-aws for architecture x86_64-amd-zen3 for repository eessi.io-2023.06-software in job dir /project/def-users/SHARED/jobs/2024.05/pr_577/10793 |
date | job status | comment |
---|---|---|---|
May 15 13:27:32 UTC 2024 | submitted | job id 10793 awaits release by job manager |
|
May 15 13:27:49 UTC 2024 | released | job awaits launch by Slurm scheduler | |
May 15 13:28:51 UTC 2024 | running | job 10793 is running |
|
May 15 13:33:56 UTC 2024 | finished | :cry: FAILURE (click triangle for details)
|
|
May 15 13:33:56 UTC 2024 | test result | :grin: SUCCESS (click triangle for details)
|
bot: build repo:eessi.io-2023.06-software arch:x86_64/amd/zen3
eessi-bot-mc-aws
(click for details)eessi-bot-mc-azure
(click for details)New job on instance eessi-bot-mc-aws for architecture x86_64-amd-zen3 for repository eessi.io-2023.06-software in job dir /project/def-users/SHARED/jobs/2024.05/pr_577/10794 |
date | job status | comment |
---|---|---|---|
May 15 13:49:09 UTC 2024 | submitted | job id 10794 awaits release by job manager |
|
May 15 13:50:00 UTC 2024 | released | job awaits launch by Slurm scheduler | |
May 15 13:51:02 UTC 2024 | running | job 10794 is running |
|
May 15 14:34:46 UTC 2024 | finished | :grin: SUCCESS (click triangle for details)
|
|
May 15 14:34:46 UTC 2024 | test result | :grin: SUCCESS (click triangle for details)
|
@trz42 Can you do your check of the log to see if this worked as expected. I would really like to get #576 merged ASAP
@trz42 Can you do your check of the log to see if this worked as expected. I would really like to get #576 merged ASAP
Checked the logs. Didn't find anything that lists the "build" time of the GROMACS executable. I'd say, just go ahead with deploying #576
We are interested in verifying if the ReFrame tests run are using the updated GROMACS build. We probably have to inspect the log files on the build cluster for this.