Skip to content

Sync meeting on EESSI test suite (2024 02 15)

Caspar van Leeuwen edited this page Feb 15, 2024 · 1 revision

Meeting (2024-02-14)

  • Unify test names EESSI_<SOFTWARE_NAME> #108

    • Merged
  • Filter invalid scales in ReFrame config #111

    • Requires ReFrame config files to be adapted and set ALL scales as features (unless you want to exclude them)
    • Merged
    • Related docs PR #156
      • Merged
  • Software layer bot config added #112

    • Merged
    • Removed again in #113
      • Since it relates to software-layer CI, it makes more sense to keep it there. Now part of #467.
      • Merged
  • common_eessi_init function now works for both pilot and production repos #114

    • Merged
  • Disable running CUDA-capable modules on CPU #110

    • Hook now defines that if it is a CUDA module and the requested device type is CPU, the partition should have both the CPU and GPU features
    • Should we do this at the hook level (i.e. apply to all software?) Or only for OSU in particular?
      • E.g. GROMACS, TensorFlow or PyTorch built against GPU would run just fine.
      • Let's discuss this comment
  • Always request GPUs on partitions that require it #116

    • Satish: did you plan to review?

TODO before 0.2.0 release:

TODO before 0.2.0 release:

  • common_config update to use EESSI_CVMFS_REPO, so that it can be used with software.eessi.io => Done!
  • GROMACS PR to software-layer => what's the status?
    • GROMACS might take a longer time to actually make it into the production repo.
    • The only relation with the test suite is that we would like to swap the CI for the test suite to use software.eessi.io, but can't as long as GROMACS is missing there
    • We don't want to wait for this, it is not essential to have that CI swap before the 0.2.0 release
  • OSU test LD_LIBRARY_PATH removed and implement hook for filtering CUDA module based tests on pure CPU nodes => #110
  • Sam will try to clean up the code style before the 0.2.0
  • Let's aim for a release in 29/02/2024

Next steps?

  • Satish: OpenFOAM test
    • Example in the OpenFOAM demo is not part of OpenFOAM 11 anymore, but we could still copy it from an older version and ship it with the test suite
    • software-layer demo is also broken for this reason
  • ESPResSo (ask Xin?)
  • PyTorch
  • LAMMPS (Lara)
    • will reach out to Tilen Potisk
  • Sam: Cleanup! :)
    • Test json-export format from ReFrame
  • CP2K
Clone this wiki locally