Support multiple EESSI versions by using ReFrame environments#326
Support multiple EESSI versions by using ReFrame environments#326casparvl wants to merge 15 commits into
Conversation
… in a single run, by configuring ReFrame environments and using ReFrame's own find_modules function
|
Ok, I now simply wrap the |
|
Oh, this broke that's something we might want to fix if we do the wrapped thing (if it's easy...) |
|
Metallwalls should also be adapted, since I think it doesn't use EESSI_mixin (?): |
|
For me: At first look, that looks quite good: all CUDA-enabled modules are only scheduled on our GPU partitions, all non-CUDA modules only on the CPU partitions. Modules are discovered accross both EESSI 2023.06 and EESSI 2025.06. The execution takes quite long - possibly also because we don't cache (yet). Anyway, I'm not disappointed with the current state: it needs some work to fix the last tests, but not a bad starting point. |
…ssi_environments' into support_multiple_eessi_environments
…n of sys:part +feat notation directly
|
i must be doing something wrong here (with my suggested fix above). |
|
ok, solved it by removing |
Co-authored-by: Sam Moors <smoors@users.noreply.github.com>
I have no clue why
|
|
yes, i get the expected behavior now: checking the ReFrame source code, the way it works as i understand: when it tries to load a module (here |
|
i looked a bit into implementing a cache for the modules, but it's not as trivial as i thought: we need to create a separate cache for each environment. also, the so, i'm now thinking to keep using our own |
…an still load environments for testing local modules
|
Discussed in the test suite sync, we can actually cache the triplets that That means @smoors is right and the only way to properly cache is to implement the caching functionality inside the Something like Ok, we need to figure out the last part (what does |
|
CI is failing because the eessi mixin class and the metallwalls test set the |
…ult', as we now use ReFrame environments to test over multiple versions of EESSI
|
Ah, the issue with the CI is a bit more subtle: the GH actions One thing that's a bit weird is that ReFrame's standard environment is called Anyway, I'll just remove it. That way, the |
|
MetalWalls works now here as well: |
@casparvl I am not sure if process binding errors belong to the test right on top or bottom of them. But they are referring to nodes so most likely not or something is wrong with the terminology within the warning. Any comments there? |
Add initial functionality to schedule test for all EESSI environments in a single run, by configuring ReFrame environments and using ReFrame's own find_modules function.
For now, these work:
Still need to work on the other tests.