Sync meeting on EESSI test suite (2025 12 18) - EESSI/meetings GitHub Wiki
Planning
- every 2 weeks on Thursday at 14:00 CE(S)T
- next meetings:
- Th 15th of January @14:00: regular test suite meeting
Meeting (2025-12-18)
Attending: Lara, Caspar, Sam, Satish
-
Replace
bench_name_ciwithis_ci_testhttps://github.com/EESSI/test-suite/pull/301/changes- Can be tested, pretty uncontroversial
-
Demote missing
read_only_filesandrequired_memory_per_nodeto warning by default, to make development easier (you just want the test to run initially) https://github.com/EESSI/test-suite/pull/302- Can then be promoted to error by setting
--setvaron CLI, see e.g. thetest.yml
- Can then be promoted to error by setting
-
The PRTE variable in https://github.com/EESSI/test-suite/pull/305 was tested by Caspar but didn't work. Sam will try to confirm
- Caspar did try with the command-line option, that worked
- Debugging output wasn't informative as to why it would be different / not working with the env var
- Should probably send an issue upstream and ask if we're doing the right thing (documentation on this env var is non-existent)
-
https://github.com/EESSI/test-suite/pull/308 showed poor performance on full node
- Probably due to oversubscription of cores causeing cache trashing
- Satish noticed that thread binding helps performance
- Caspar will call the thread binding hook
-
https://github.com/EESSI/test-suite/pull/303 LAMMPS + OBMD + ALL is still problematic / failing
- Failures are erratic
- Caspar noticed it did succeed if he runs interactively in an
salloc - Caspar will look for environmet differences to see what's causing this
Two issues:
- Change all configs to set the
set_num_nodesoption, and also put this in our EESSI docs https://github.com/EESSI/test-suite/issues/304 - Add sanity check for checking task binding: https://github.com/EESSI/test-suite/issues/307