Sync meeting on EESSI test suite (2026 01 21) - EESSI/meetings GitHub Wiki
EESSI test suite sync meetings
Planning
- every 2 weeks on Thursday at 14:00 CE(S)T
- next meetings:
- Th 12th of February @13:00: regular test suite meeting (Expected: Lara, Sam, Satish Caspar)
Meeting (2025-01-21)
Attending: Lara, Caspar, Sam, Satish
-
Caspar will re-review: https://github.com/EESSI/test-suite/pull/301, https://github.com/EESSI/test-suite/pull/302, https://github.com/EESSI/test-suite/pull/310
-
Satish will review: https://github.com/EESSI/test-suite/pull/305, https://github.com/EESSI/test-suite/pull/312
-
Big discussion regarding https://github.com/reframe-hpc/reframe/pull/3613 . Several options:
- If this gets accepted, we can simply set
valid_systems = module_info[0], as our other features get appended (and then respected because of the PR ) - If this doesn't get accepted:
- We can add the partition name as a requested feature (extract it from
module_info[0]) in valid systems and add it as a feature in the ReFrame config file (probably want some convenience function that does this) - We can use the upstream
find_modulesand try to deduplicate between the partitions (i.e. and then NOT setvalid_systems = module_info[0]) => works as long as all partitions have the same environments with the same modules - We can alter our own
find_modulesto load environments before doing module discovery. That works, as long as all partitions have the same environments with the same modules - Stick with the current situation: don't use ReFrame environments, just loop over EESSI environments by calling ReFrame multiple times.
- We can add the partition name as a requested feature (extract it from
- If this gets accepted, we can simply set
-
Lara will review https://github.com/EESSI/test-suite/pull/314