EESSI test suite sync meetings

Planning

• every 2 weeks on Thursday at 14:00 CE(S)T
• next meetings:
  • 19th June 2025: cancelled
  • 2nd of July 2025: next meeting. Sam might be on holiday. Lara, Satish, Caspar should be there

---

Meeting (2025-06-12)

Attending: Satish, Caspar, Kenneth, Sam

• Open PRs
  • Docs PR for API documentation
    • Comment from Lara: it doesn't error out when you don't have a local clone of the test suite (but does fail to then generate API docs of course). Should produce an error.
  • OpenFOAM lid driven cavity #243
    • TODO: drop down to quarter node, and add a 'skip-if' in case there's <8 cores.
    • TODO: add the comment in the code about the multiple invocations of mpirun
    • Will add a 1M mesh in the future that will run at smaller scales (will be tagged CI)
    • Sam: tested on Skylake nodes, worked fine.
  • Create a follow-up PR for creating a standard function that sets a minimum core count in the EESSI mixin class.
    • Use a standard phrase for the test skip.
    • Tests currently using this kind of functionality are: CP2K, OSU and OpenFOAM.

Done: - Satish removed the list of tests, as it's already in the table of contents

TODO - API docs: ready for re-review - Satish will explore Stream - Sam: find time to write a BLAS test :) - Working on the BLIS test, that's provided through the BLIS sources - Very poor performance on zen5 (specifically), spent time trying to figure that out - No support for autodetecting zen5, so had to override to zen3

• Other business:

  • Caspar: working on deliverable for MultiXscale "Portable test suite for shared software stack"

• Discussion

  • Austrian system (Musica?), looking to adopt EESSI as basis for their software stack. One of their support staff (Siegel, Moritz) also very interested in EESSI test suite. Tried to write a test, but that was too difficult. Did manage to get the test suite running.
  • Sam: we have some Zen5 nodes in local cluster. New Belgian Tier1 will also be Zen5
    • Caspar: might be nice to put a build bot on your local cluster, so you can build an optimized stack for the Tier1 before it comes in
    • But, fallback to zen4 also works - though we (Satish) have seen some issues with zen3 stack on zen4 systems.