-
Notifications
You must be signed in to change notification settings - Fork 52
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
{2023.06}[foss/2023a] Siesta 5.2.2, EasyBuild 5.0.0 #966
Conversation
ocaisa
commented
Mar 10, 2025
```bash 14 out of 76 required modules missing: * test-drive/0.5.0-GCCcore-12.3.0 (test-drive-0.5.0-GCCcore-12.3.0.eb) * json-fortran/9.0.2-GCC-12.3.0 (json-fortran-9.0.2-GCC-12.3.0.eb) * flook/0.8.4-GCC-12.3.0 (flook-0.8.4-GCC-12.3.0.eb) * mctc-lib/0.3.1-GCC-12.3.0 (mctc-lib-0.3.1-GCC-12.3.0.eb) * mstore/0.3.0-GCC-12.3.0 (mstore-0.3.0-GCC-12.3.0.eb) * libfdf/0.5.1-GCC-12.3.0 (libfdf-0.5.1-GCC-12.3.0.eb) * TOML-Fortran/0.4.2-GCC-12.3.0 (TOML-Fortran-0.4.2-GCC-12.3.0.eb) * ruamel.yaml/0.17.32-GCCcore-12.3.0 (ruamel.yaml-0.17.32-GCCcore-12.3.0.eb) * xmlf90/1.6.3-GCC-12.3.0 (xmlf90-1.6.3-GCC-12.3.0.eb) * libPSML/2.1.0-GCC-12.3.0 (libPSML-2.1.0-GCC-12.3.0.eb) * Simple-DFTD3/1.2.1-gfbf-2023a (Simple-DFTD3-1.2.1-gfbf-2023a.eb) * libGridXC/2.0.2-gompi-2023a (libGridXC-2.0.2-gompi-2023a.eb) * PnetCDF/1.12.3-gompi-2023a (PnetCDF-1.12.3-gompi-2023a.eb) * Siesta/5.2.2-foss-2023a (Siesta-5.2.2-foss-2023a.eb) ```
Instance
|
Instance
|
bot: build repo:eessi.io-2023.06-software instance:eessi-bot-mc-aws arch:aarch64/neoverse_v1 |
Updates by the bot instance
|
Updates by the bot instance
|
New job on instance
|
@migueldiascosta When I build this on Neoverse V1 I get:
and digging deeper
Is that something to worry about? |
@AnthoniAlcaraz Can you maybe comment? |
Hm, those 0.0 values do look like something to worry about... Maybe Siesta's own ELSI (with ELPA and PEXSI) has issues on Arm (weird that only one test is failing though) let me see if I can reproduce that on a64fx |
bot: build repo:eessi.io-2023.06-software instance:eessi-bot-mc-aws arch:aarch64/neoverse_n1 Also trying it on another architecture to see if the problem is unique to neoverse_v1 |
Updates by the bot instance
|
Updates by the bot instance
|
Updates by the bot instance
|
Updates by the bot instance
|
New job on instance
|
I can reproduce the error in the elsi-pexsi verification test if the parent test is RUN TWICE. In that case, the second run reads the DM file generated by the first run instead of starting from scratch and the subsequent data is all different. I see that you have a categorization by 'labels'. Is it possible that the 'long' tests are run in addition to the whole battery of tests? Since the elsi-pexsi test is labelled as 'long', that would explain the second run. On the other hand, this re-use of the DM is not exclusive of the elsi-pexsi test, so I am surprised that you do not get other spurious errors in other tests that might be run twice. What exactly do you do with ctest? |
The tests are called with (and a number of tests are excluded). @migueldiascosta probably knows more since he worked on the easyconfigs. |
yeah, we're simply running, after building, @albgar what exactly did you mean by "I see that you have a categorization by 'labels'"? |
I thought that maybe the labels were used to run specific subsets of tests, and that some of those subsets might overlap (and thus forcing the elsi-pexsi to run twice). Alberto
|
bot: build repo:eessi.io-2023.06-software instance:eessi-bot-mc-aws arch:aarch64/neoverse_v1 |
Updates by the bot instance
|
Updates by the bot instance
|
Updates by the bot instance
|
Updates by the bot instance
|
New job on instance
|
I opened a patch PR at easybuilders/easybuild-easyconfigs#22562 |
bot: build repo:eessi.io-2023.06-software instance:eessi-bot-mc-aws arch:aarch64/neoverse_v1 |
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
|
I'm a bit lost here, for Haswell only, once I reach hybrid MPI/OpenMP tests things just hang:
I'll disable UCX and libfabric and see if that helps. |
Ok, I managed to get this to pass by setting
This should already be in the case in the job context on our AWS build cluster but I suspect it is not being passed through when we initialise Gentoo Prefix. |
Strange, this should have been solved by #531 but it seems not to be. |
bot: build repo:eessi.io-2023.06-software instance:eessi-bot-mc-aws arch:x86_64/intel/haswell |
Updates by the bot instance
|
Updates by the bot instance
|
Updates by the bot instance
|
Updates by the bot instance
|
Updates by the bot instance
|
New job on instance
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
Label |
1 similar comment
Label |
@trz42 Thanks for your help with this, all staging PRs ingested and available |
PR merged! Moved |
PR merged! Moved |