Corryvreckan issueshttps://gitlab.cern.ch/corryvreckan/corryvreckan/-/issues2023-11-24T10:51:20+01:00https://gitlab.cern.ch/corryvreckan/corryvreckan/-/issues/87CI-Testing: Allow multiple #PASS conditions2023-11-24T10:51:20+01:00Jens KroegerCI-Testing: Allow multiple #PASS conditionsAfter a discussion with @simonspa we concluded:
It would be a really powerful improvement to allow for multiple #PASS conditions in the CI automated testing.
This could be done as follows:
Instead defining the ctest as running corry an...After a discussion with @simonspa we concluded:
It would be a really powerful improvement to allow for multiple #PASS conditions in the CI automated testing.
This could be done as follows:
Instead defining the ctest as running corry and parsing the terminal output for the pass condition, the terminal output could be written to a log file and then parsed multiple times for different conditions.
Currently, the whole analysis needs to be re-run as a separate test for a different pass condition.https://gitlab.cern.ch/corryvreckan/corryvreckan/-/issues/83Add Tests for FileWriter & FileReader to CI2019-12-06T13:37:44+01:00Simon SpannagelAdd Tests for FileWriter & FileReader to CIWe need to make sure what we write to file makes sense. I suggest two tests, one for storing data using the FileWriter, the second one (with a `#DEPENDS` on the first one) to read that very file back and continue reconstruction.We need to make sure what we write to file makes sense. I suggest two tests, one for storing data using the FileWriter, the second one (with a `#DEPENDS` on the first one) to read that very file back and continue reconstruction.Lennart HuthLennart Huthhttps://gitlab.cern.ch/corryvreckan/corryvreckan/-/issues/40Add Test Cases and a CI Testing Stage2018-12-12T10:07:22+01:00Simon SpannagelAdd Test Cases and a CI Testing StageFor every detector/DUT supported, we should add one test case with abbreviated data files, placed on the newly created EOS project space to be found at `/eos/project/c/corryvreckan/`. A script should be able to download these files and e...For every detector/DUT supported, we should add one test case with abbreviated data files, placed on the newly created EOS project space to be found at `/eos/project/c/corryvreckan/`. A script should be able to download these files and execute the framework with the corresponding configuration files.
The output checked should e.g. be the number of tracks found.
This way we can monitor that new additions or changes do not break compatibility with our existing setups and data sets.Simon SpannagelSimon Spannagel