EESSI test suite sync meetings

# EESSI test suite sync meetings ## 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_ci` with `is_ci_test` https://github.com/EESSI/test-suite/pull/301/changes - Can be tested, pretty uncontroversial - Demote missing `read_only_files` and `required_memory_per_node` to 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 `--setvar` on CLI, see e.g. the `test.yml` - 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_nodes` option, 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 ## Meeting (2025-11-12) Attending: Anirudh, Rodrigo, Satish, Caspar, Lara - ALL + LAMMPS: just swap the in-file for something that uses ALL - Rodrigo: we have some examples, it's in the dev.eessi.io-lammps-obmd repo - https://github.com/multixscale/dev.eessi.io-lammps-plugin-obmd/pull/7 - in.balance.staggered.global - and in.balance.staggered.local are the relevant ones - Satish: we need something to validate against to implement as a sanity check in reframe - Jonas will supply us with a job script - Lara will implement the test. The job script generated by ReFrame will be sent back to Jonas/Rodrigo for validation - Walberla: it seems the current installation in EESSI is incomplete, i.e. it contains the benchmarks, but they are not compiled - Easiest way to go is probably to fix this, and make sure the installation of walberla contains already compiled benchmarks - Then, we can easily write a test. Each benchmarks comes with its own input file, and the way to run it is simply `mpirun -np <x> app_name input_file` ## Meeting (2025-10-23) Attending: .... - [BLAS test](https://github.com/EESSI/test-suite/pull/268) Merged! - Removed single-threaded tests (1_core is still single threaded of course) - `herk` and `hemm` routines for 2023a seem to have poor performance, equal to single-threaded performance [#287](https://github.com/EESSI/test-suite/issues/287) - If he finds time, Sam may investigate further - [TensorFlow](https://github.com/EESSI/test-suite/pull/275) & [MareNostrum config](https://github.com/EESSI/test-suite/pull/277): - So the _plan_ is to have a feature `FEATURES.OFFLINE`, such as is set in the MareNostrum config - The TF test will, if this feature is set, set the `EESSI_TEST_SUITE_DISABLE_DOWNLOAD` environment variable. - In the test code itself, if this variable is set, the data will not be downloaded but will be looked for in a certain path. - If that path does not exist, the test will call `hooks.filter_valid_for_offline_partitions`, which will add `-offline`. This way, the test will be skipped on offline systems - Only remaining issue is that `hooks.filter_valid_for_offline_partitions` is missing :) - Probably the PRs should be merged together, since both need the `FEATURES.OFFLINE` constant (or #275 also needs to add this to `constants`) - Since Lara is not around: if Caspar finds time soon, he'll push that hook, merge the feature branchs into one, and test. - [1M case for OpenFOAM](https://github.com/EESSI/test-suite/pull/278) - Can be merged - [64M case for OpenFOAM](https://github.com/EESSI/test-suite/pull/281) - Should be tested on another system than Snellius, code should be very similar to 1M case - As soon as both 1M and 64M cases are merged, Satish will create a new PR to deduplicate code by using a base class - Numpy test: use compact binding [#286](https://github.com/EESSI/test-suite/pull/286) - Caspar will test this end of this afternoon, and compare to the unbound numpy performance just to be sure - Should probably make a new release - We have new tests, e.g. numpy ## Meeting (2025-10-08) Attending: Lara, Sam, Caspar - [BLAS test](https://github.com/EESSI/test-suite/pull/268) can use a (re)-review, should be done - Remark from SAM: you may remember that I saw bad performance for BLIS before. That was because of a name conflict with a single-threaded library with the same name. - [TensorFlow](https://github.com/EESSI/test-suite/pull/275) test is done. We should test carefully - either on an offline system, or check the logs carefully to verify that it doesn't actually (re)download the data if the environment variable is set. - At least when the data is _not_ there, it should print an informative error. That can be checked easily. If we then put the data in place and the error is resolved again, that proves the functionality. - can be merged - we don't have access, so we cant test, but there's no point in keeping it open until we do. - We can at least test similar config arguments for e.g. Snellius and see if it gives the expected behavior - [1M case for OpenFOAM](https://github.com/EESSI/test-suite/pull/278) final comments from Sam - Plan is to introduce the base class in a follow-up PR - [64M case for OpenFOAM](https://github.com/EESSI/test-suite/pull/281) - Ready for testing - Plan: it would be nice to have a standardized way to skip tests if a certain resource X (GPUs, CPUs, memory) doesn't meet a certain requirement. So move that from the test, to the mixin class. That way the error messages on the skip are standardized, instead of different for each test. - In the mixin class, we can define one function for which the arguments are the resource, count and limit, and have that print a standardized message - Discussed various changes to the dashbaords: - Symbol S now indicates skipped tests - Symbol A for aborted tests - Discussed QuantumESPRESSO test, but that was because of the missing hook https://www.eessi.io/docs/known_issues/eessi-2023.06/#failed-to-modify-ud-qp-to-init-on-mlx5_0-operation-not-permitted - Updated the ingestion script so that it can now also ingest data from ReFrame Data Version of the report file 4.1: https://github.com/EESSI/dashboard-ingestion/pull/7 ## Meeting (2025-09-24) Attending: Lara, Satish - Merged PRs - Small typo correction in the hooks. [#283](https://github.com/EESSI/test-suite/pull/283) - Open PRs. - [lara] Testing OpenFoam tests - OpenFOAM 64M test case [Ready for testing] [#281](https://github.com/EESSI/test-suite/pull/281) - 1M test case which should also become CI [Ready for review] [#278](https://github.com/EESSI/test-suite/pull/278) - Done and everything passed. Waiting to be merged. - [satish] Testing Offline tests - Add configuration file for MareNostrum5 [Offline nodes] [#277](https://github.com/EESSI/test-suite/pull/277) - Make sure TensorFlow also works on offline machines [#275](https://github.com/EESSI/test-suite/pull/275) - Can be tested on online systems as well. Still in my pipeline tasks. - ReFrame let us know that we should adopt all the HPCtestlibs we want if we want to make them compatible with offline systems - Tests may need to be moved to our test-suite completely. - [lara] Metalwalls test is not using the EESSI-Mixin class yet. - [satish] Failures and missing data of OSU tests in surf. - Somehow `/scratch-shared` was not accessible to the jenkins user under which these tests are being run because of which the pipeline was failing. - Tests have started to run after last maintenance but need to find the reason why the above was happening in the first place since end of July. - [satish] Move tests to the OpenFOAM [ORG version](https://openfoam.org/) . ## Meeting (2025-08-14) Attending: Lara, Satish - Merged PRs - Small change to hortense config - Config vsc_hortense: remove old partition and use new [#282](https://github.com/EESSI/test-suite/pull/282) - skip tests which require internet access on offline machines [#279](https://github.com/EESSI/test-suite/pull/282) - - Open PRs - [lara] Testing OpenFoam tests - OpenFOAM 64M test case [Ready for testing] [#281](https://github.com/EESSI/test-suite/pull/281) - 1M test case which should also become CI [Ready for review] [#278](https://github.com/EESSI/test-suite/pull/278) - [satish] Testing Offline tests - Add configuration file for MareNostrum5 [Offline nodes] [#277](https://github.com/EESSI/test-suite/pull/277) - Make sure TensorFlow also works on offline machines [#275](https://github.com/EESSI/test-suite/pull/275) - ReFrame let us know that we should adopt all the HPCtestlibs we want if we want to make them compatible with offline systems - Metalwalls test is not using the EESSI-Mixin class yet - Failures and missing data of OSU tests in surf --- ## Meeting (2025-08-14) Attending: Caspar, Lara, Sam, Satish - Merged PRs - Numpy tests merged [#PR 276](https://github.com/EESSI/test-suite/pull/276) - Open PRs - Discussed in the issues themselves (review comments) --- ## Meeting (2025-07-31) Attending: Caspar, Lara, Sam, Satish - Merged PRs - None :( - Open PRs - Mare Nostrum 5 config https://github.com/EESSI/test-suite/pull/277 - OpenBLAS https://github.com/EESSI/test-suite/pull/268 - Caspar: tested, works with local stack, fails with EESSI due to lack of RPATH-ing (see [here](https://github.com/EESSI/test-suite/pull/268#issuecomment-3078623051)) - numpy https://github.com/EESSI/test-suite/pull/276 - TensorFlow https://github.com/EESSI/test-suite/pull/275 => You can use the resource dir from the test with `self.current_system.resourcesdir`. That, icm with adding the `path` variable to the `tf.datasets` call should hopefully help to progress this - OpenFOAM smaller test case (1M): https://github.com/EESSI/test-suite/pull/278 - Not tested yet, but minimal changes compared to 8M test case. "should work" (famous last words :)) - Issues - Satish: there's an uncaught if-elif still in the API docs PR. https://github.com/EESSI/docs/blob/67457e1d08ccca72979cf7c03202f8c7f73a2991/docs/generate_eessi_testsuite_api_docs.py#L37 - Satish will make a fix for this => Still open - [WIP] [#513](https://github.com/EESSI/docs/pull/513) Discussed - GROMACS & Metallwalls test download stuff on the fly - Offline testing of e.g. GROMACS is problematic, because it's a test from `hpctestlib`, and we can't easily change that to use the `resourcesdir`. Asked Vasileos on chat, but not sure if there's a response yet. - 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. - Satish will explore Stream - Improve docstrings so that autogenerated API docs actually become useful (maybe with some AI help?) --- ## Meeting (2025-07-17) Attending: Lara, Satish, Caspar - Merged PRs - Fix output of full_modulepath [#274](https://github.com/EESSI/test-suite/pull/274) - Open PRs - Mare Nostrum 5 config https://github.com/EESSI/test-suite/pull/277 - OpenBLAS https://github.com/EESSI/test-suite/pull/268 - Caspar: tested, works with local stack, fails with EESSI due to lack of RPATH-ing (see [here](https://github.com/EESSI/test-suite/pull/268#issuecomment-3078623051)) - numpy https://github.com/EESSI/test-suite/pull/276 - TensorFlow, introduce pre-download support for offline batch nodes https://github.com/EESSI/test-suite/pull/275 - Issues - Satish: there's an uncaught if-elif still in the API docs PR. https://github.com/EESSI/docs/blob/67457e1d08ccca72979cf7c03202f8c7f73a2991/docs/generate_eessi_testsuite_api_docs.py#L37 - Satish will make a fix for this - [WIP] [#513](https://github.com/EESSI/docs/pull/513) TODO - 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. - Satish will explore Stream - Improve docstrings so that autogenerated API docs actually become useful (maybe with some AI help?) --- ## Meeting (2025-07-02) Attending: Caspar, Kenneth, Sam, Satish - Open PRs - OpenBLAS https://github.com/EESSI/test-suite/pull/268 - Tried dry-run, but not creating test instances - Issues - full modulepath is printed to stderr, whereas ReFrame tries to read it from stdout. Thus, it ends up as 'None' in the report_files - LMOD_REDIRECT can be set to no or yes, changing the behaviour of where LMOD prints. This was different between EESSI and local modulestack at UGent. Thus, for local modules, they were seeing the modulepath - Fix: let's do a redirect `2>&1` in the `eessi_mixin` class for the `module --location show` command. => Lara will implement a fix - Satish: there's an uncaught if-elif still in the API docs PR. https://github.com/EESSI/docs/blob/67457e1d08ccca72979cf7c03202f8c7f73a2991/docs/generate_eessi_testsuite_api_docs.py#L37 - Satish will make a fix for this Done: - Docs PR for API documentation is merged! Live on e.g. https://www.eessi.io/docs/testsuite_api/eessi/testsuite/eessi_mixin/ - OpenFOAM lid driven cavity was merged [#243](https://github.com/EESSI/test-suite/pull/243) - OpenFOAM added to list of available tests https://www.eessi.io/docs/test-suite/available-tests/ TODO - 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. - 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. - --- ## 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](https://github.com/EESSI/test-suite/pull/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. ## Planning - every 2 weeks on Thursday at 14:00 CE(S)T - next meetings: - 12th June 2025: Sam, Lara, Satish, Caspar should all be able to make it. - 19th June 2025: cancelled --- ## Meeting (2025-05-15) Attending: Satish, Caspar, Lara, Sam - [Merged PRs](https://github.com/EESSI/test-suite/pulls?q=is%3Apr+is%3Aclosed+merged%3A2025-04-28..2017-05-15) - Docs PR: https://github.com/EESSI/docs/pull/445 - Small fix to docstring: https://github.com/EESSI/test-suite/pull/265 - 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](https://github.com/EESSI/test-suite/pull/243) (Caspar: I've converted to draft) - Ready to be tested, scales: 2 nodes and up, otherwise it's to slow (it's an 8M mesh) - Will add a 1M mesh in the future that will run at smaller scales (will be tagged CI) - Sam: might test on our new Zen5 nodes TODO - Satish will remove the list of tests, as it's already in the table of contents - API docs: Caspar actively working on it - Satish will explore Stream => Focussed on OpenFOAM first, based on the one from the ExaFOAM project - Sam: find time to write a BLAS test :) - 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. ## Meeting (2025-04-28) Attending: Satish, Caspar, Lara, Sam - [Merged PRs](https://github.com/EESSI/test-suite/pulls?q=is%3Apr+is%3Aclosed+merged%3A2025-04-02..2025-04-28+) - [#262](https://github.com/EESSI/test-suite/pull/262) Set SLURM_EXPORT_ENV=ALL in `prepare_cmds` for example config - In response to some issues seen at EUM'25 hands-on, this is a good 'default'. It doesn't hurt anyone - even non-SLURM users - [#250](https://github.com/EESSI/test-suite/pull/250) Resolve failing to submit to Hortense GPU partition - Indeed resolved in the end by setting `'env_vars': [['SLURM_CONF', '/etc/slurm/slurm.conf_dodrio']]` at the `system` level - [#264](https://github.com/EESSI/test-suite/pull/264) Drop Python 3.6 support in tests and bump Ubuntu versions - Should we fix this more decently (e.g. run in container) and keep Python 3.6 support? - Open PRs - OpenFOAM lid driven cavity [#243](https://github.com/EESSI/test-suite/pull/243) (Caspar: I've converted to draft) - Updates? => Test works now! Now adding sanity checks for each of the steps. Should be ready end-of-week (8M mesh case) - There are other input files with larger mesh sizes, but won't be in the _current_ test instance - N.B. test for .com-version of OpenFOAM TODO - Satish will update the supported Python version at https://www.eessi.io/docs/test-suite/installation-configuration/ to 3.7 or higher, and provide some instructions on how to install a newer python in user space in case the system Python is <= 3.6 - API docs: Caspar will implement the changes himself => still todo Sam: should we sync the update of the API docs with the test suite releases? Yes, good idea, instead of periodic schedule creating API docs PRs, I'll make a manual schedule that needs to be triggered _as part of the release cycle_ for the test suite - Satish will explore Stream => Focussed on OpenFOAM first, based on the one from the ExaFOAM project - Satish will make a PR on the short term to docs to update the list of tests and instructions to run it. Long term, we want this info to be in the API docs, so we want to put this in the docstring of the test class - Other business: - Caspar: working on deliverable for MultiXscale "Portable test suite for shared software stack" - Discussion - Test suite is a bit on the DL... how do we revive efforts? Attract others to contribute? - Should we focus on more tests vs more features - E.g. performance checking? - Portable library tests? - A more clear strategy on how to deal with dependent tests (as mixture classes don't work so well) - SAM: BLAS test could be a good attempt - Satish: getting fixtures in was difficult. Mixture class helps but _only_ if you use it in one of the classes from the fixtures. - Libraries that could be good to add tests for: PETSc, Trilinos, - End-user software that could be good to add tests for: jax, inference-based tests for PyTorch / TensorFlow, - More low-level tests like: stream, HPL, GPU burn ------- ## Previous meetings - https://github.com/EESSI/meetings/wiki/Sync-meeting-on-EESSI-test-suite-(2025-04-28) - https://github.com/EESSI/meetings/wiki/Sync-meeting-on-EESSI-test-suite-(2025-04-02) - https://github.com/EESSI/meetings/wiki/Sync-meeting-on-EESSI-test-suite-(2025-03-13) - https://github.com/EESSI/meetings/wiki/Sync-meeting-on-EESSI-test-suite-(2025-02-26) - https://github.com/EESSI/meetings/wiki/Sync-meeting-on-EESSI-test-suite-(2025-01-09) - https://github.com/EESSI/meetings/wiki/Sync-meeting-on-EESSI-test-suite-(2024-12-11) - https://github.com/EESSI/meetings/wiki/Sync-meeting-on-EESSI-test-suite-(2024-11-28) - https://github.com/EESSI/meetings/wiki/Sync-meeting-on-EESSI-test-suite-(2024-11-13) - https://github.com/EESSI/meetings/wiki/Sync-meeting-on-EESSI-test-suite-(2024-10-31) - https://github.com/EESSI/meetings/wiki/Sync-meeting-on-EESSI-test-suite-(2024-10-10) - https://github.com/EESSI/meetings/wiki/Sync-meeting-on-EESSI-test-suite-(2024-09-19) - https://github.com/EESSI/meetings/wiki/Sync-meeting-on-EESSI-test-suite-(2024-08-08) - https://github.com/EESSI/meetings/wiki/Sync-meeting-on-EESSI-test-suite-(2024-07-25) - https://github.com/EESSI/meetings/wiki/Sync-meeting-on-EESSI-test-suite-(2024-06-27) - https://github.com/EESSI/meetings/wiki/Sync-meeting-on-EESSI-test-suite-(2024-06-13) - https://github.com/EESSI/meetings/wiki/Sync-meeting-on-EESSI-test-suite-(2024-05-23) - https://github.com/EESSI/meetings/wiki/Sync-meeting-on-EESSI-test-suite-(2024-05-03) - https://github.com/EESSI/meetings/wiki/Sync-meeting-on-EESSI-test-suite-(2024-04-18) - https://github.com/EESSI/meetings/wiki/Sync-meeting-on-EESSI-test-suite-(2024-03-28) - https://github.com/EESSI/meetings/wiki/Sync-meeting-on-EESSI-test-suite-(2024-03-14) - https://github.com/EESSI/meetings/wiki/Sync-meeting-on-EESSI-test-suite-(2024-02-29) - https://github.com/EESSI/meetings/wiki/Sync-meeting-on-EESSI-test-suite-(2024-02-15) - https://github.com/EESSI/meetings/wiki/Sync-meeting-on-EESSI-test-suite-(2024-02-01) - https://github.com/EESSI/meetings/wiki/Sync-meeting-on-EESSI-test-suite-(2024-01-18) - https://github.com/EESSI/meetings/wiki/Sync-meeting-on-EESSI-test-suite-(2023-12-06) - https://github.com/EESSI/meetings/wiki/Sync-meeting-on-EESSI-test-suite-(2023-11-22) - https://github.com/EESSI/meetings/wiki/Sync-meeting-on-EESSI-test-suite-(2023-11-08) - https://github.com/EESSI/meetings/wiki/Sync-meeting-on-EESSI-test-suite-(2023-10-19) - https://github.com/EESSI/meetings/wiki/Sync-meeting-on-EESSI-test-suite-(2023-10-04) - https://github.com/EESSI/meetings/wiki/Sync-meeting-on-EESSI-test-suite-(2023-09-20) - https://github.com/EESSI/meetings/wiki/Sync-meeting-on-EESSI-test-suite-(2023-09-06) - https://github.com/EESSI/meetings/wiki/Sync-meeting-on-EESSI-test-suite-(2023-08-25) - https://github.com/EESSI/meetings/wiki/Sync-meeting-on-EESSI-test-suite-(2023-08-09) - https://github.com/EESSI/meetings/wiki/Sync-meeting-on-software-testing-(27%E2%80%9007%E2%80%902023) - https://github.com/EESSI/meetings/wiki/Sync-meeting-on-EESSI-test-suite-(2023-06-28) - https://github.com/EESSI/meetings/wiki/Sync-meeting-on-EESSI-test-suite-(2023-06-15) - https://github.com/EESSI/meetings/wiki/Sync-meeting-on-EESSI-test-suite-(2023-05-31) - https://github.com/EESSI/meetings/wiki/Sync-meeting-on-EESSI-test-suite-(2023-05-17) - https://github.com/EESSI/meetings/wiki/Sync-meeting-on-EESSI-test-suite-(2023-04-20) - https://github.com/EESSI/meetings/wiki/Sync-meeting-on-EESSI-test-suite-(2023-03-30) - https://github.com/EESSI/meetings/wiki/Sync-meeting-on-EESSI-test-suite-(2023-03-10) (incl. 2023-02-23) - https://github.com/EESSI/meetings/wiki/Sync-meeting-on-EESSI-test-suite-(2023-02-09)