Some tests produce too much output?
The tests that configure all HLT2 lines in Moore (see list below) have very long job options. By default we dump them and they are collected into the CTest output and end up uncompressed in the
Test.xml such as this one. This makes for a very large file (250MB).
@clemenci is this a problem nowadays? Sometimes I get timeouts (when trying to open the Moore test results) and it takes a few minutes afterwards before I can open any page in the dashboard. Could this be the reason?
Possible solutions could be:
- We should see if we can compress the job option dump fields, which would help all across our tests and not only for the very large ones.
- We should perhaps switch off the dumps for these tests. The dumps can be very useful when debugging locally, so if there is a way we should only remove them from the xml artifacts.
Hlt2Conf.streaming.test_hlt2_all_lines_with_reco_with_streams_mdf Hlt2Conf.test_hlt2_all_lines Hlt2Conf.test_hlt2_all_lines_with_reco Hlt2Conf.hlt2_pp_thor Hlt2Conf.sprucing.test_spruce_all_lines_realtime Hlt2Conf.streaming.test_hlt2_all_lines_with_reco_with_streams
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information