-
Notifications
You must be signed in to change notification settings - Fork 15
Description
I am wondering if it might be beneficial to use the CI scripts in the CI workflow. I started thinking about it because right now we are accidentally breaking the dashboard-ingestion script everytime we use a newer test-suite version. For instance on hortense we are now using the test-suite version that is already using Reframe version 4.8.1 while on Tier2 I'm using v0.5.1 (ReFrame version 4.7.3).
If we update https://github.com/EESSI/test-suite/blob/main/.github/workflows/test.yml to also use the CI scripts than it will automatically pick up the ReFrame version specified in that script. which would also produce a report-file.
I would than also like to expend this CI worflow so that we can test the parsing done with https://github.com/EESSI/dashboard-ingestion/blob/fix_reframe_4_7/inject.py of the report-files. This way we know that the injestion scripts breaks when we bump the ReFrame version. Because I only just now noticed that we have not been uploading the hortense data since the end of August.