# EESSI test suite sync meetings

## Planning

- every 2 weeks on Thursday at 14:00 CE(S)T
- next meetings:
- Thu 8 Aug'24 14:00 CEST (Caspar, Satish, Sam (maybe), Lara/Kenneth?)

---

## Meeting (2024-07-25)

Attending: Sam Moors, Caspar van Leeuwen

- Caspar worked on [Tutorial for writing a portable test](https://hackmd.io/mFovCXgSSDmF_Aybt47DOg)
- Based on `mpi4py` all-reduce example
- Substantial progress, but not finished yet. Now at the stage where we have a standard ReFrame test and discuss the steps how to make it portable.

- Three releases (0.3.0, 0.3.1, 0.3.2) by the end of June, used for the deliverable in MultiXscale
- Still todo: update docs:
- Describe ESPResSo test cases (Satish)
- Update tag names (Satish)
- Add small section on debugging if a test doesn't succeed
- Where to find the full logs
- How to run manually

- Apply memory limits using memory hook for _all_ tests
- Caspar will go through the tests and update them where needed
- Suggestion: run `top` and dump info to figure out max memory useage, e.g. `for i in {1..4}; do sleep 0.1 && top -b -n1 | grep "MiB Mem" ; done > cron.txt` or for a specific process `for i in {1..4}; do sleep 0.1 && top -b -n1 -p <pid>; done > cron.txt`. More info: https://www.tecmint.com/save-top-command-output-to-a-file/
- Suggestion 2: get it directly from `/proc/<pid>/status`
- Suggestion 3: get the maximum useage from the C-group at the end of the job `cat /sys/fs/cgroup/memory/$(</proc/self/cpuset)/memory.max_usage_in_bytes`

- OpenFOAM test
- Satish has a test that works, but no ReFrame test => No progress

- Merged PRs
- Improve hook to allow launching 1 task per physical CPU _or_ hardware thread, depending on what makes sense for the application[#160](https://github.com/EESSI/test-suite/pull/160)
- Added LJ test to ESPResSo [#155](https://github.com/EESSI/test-suite/pull/155)
- Fix memory request units for ESPResSo [#158](https://github.com/EESSI/test-suite/pull/158)

- Open PRs
- PyTorch: Caspar still needs to set `OMP_NUM_THREADS`, then Sam will look at it again

- CP2K:
- OOM on Snellius for 1/8th node test (16 cores). Caspar will rerun to see if it is consistent, if so, try to increase memory request until it succeeds.
- Caspar will rerun on Karolina to see if the failures on 16 Nodes are consistent
- LAMMPS:
- _Seems_ to be ready for review, but Lara isn't here to check
- Caspar will try to run it on Snellius / Karolina, maybe Vega
- Sam will try to have a look too

-------

## Previous meetings

- 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)