Explain what you would like to see improved and how.
Now that roottest is part of the main repo (!!thanks!!), one potential upgrade is that, when a tests fails, there is something like gcc-problem-matcher running behind that annotates the failing test output on the (changed or not) test file. It would then appear with the log under the "Files changed" tab.
To do this, the test failures should always print __FILE__, not sure if that's easy to change though...
An alternative would be to just put the annotation in the definition of the CMakeLists target.
Or to just put the annotation somewhere in the Files changed tab.
A problem is that Windows reruns tests multiple times, so it should be excluded.
The current workaround is to click on "Test Results" of the logs, eg https://github.com/root-project/root/pull/20016/checks?check_run_id=51624533514 but this does not tell you the 'source file'.
ROOT version
/
Installation method
/
Operating system
/
Additional context
Also, very often, the gcc-problem-matcher does not correctly annotate compilation warnings or errors, especially for things such as things compiled within roottest and ctests, etc.
Related:
root-project/jenkins-pipelines#10
root-project/gcc-problem-matcher-improved#10
Explain what you would like to see improved and how.
Now that roottest is part of the main repo (!!thanks!!), one potential upgrade is that, when a tests fails, there is something like gcc-problem-matcher running behind that annotates the failing test output on the (changed or not) test file. It would then appear with the log under the "Files changed" tab.
To do this, the test failures should always print
__FILE__, not sure if that's easy to change though...An alternative would be to just put the annotation in the definition of the CMakeLists target.
Or to just put the annotation somewhere in the Files changed tab.
A problem is that Windows reruns tests multiple times, so it should be excluded.
The current workaround is to click on "Test Results" of the logs, eg https://github.com/root-project/root/pull/20016/checks?check_run_id=51624533514 but this does not tell you the 'source file'.
ROOT version
/
Installation method
/
Operating system
/
Additional context
Also, very often, the gcc-problem-matcher does not correctly annotate compilation warnings or errors, especially for things such as things compiled within roottest and ctests, etc.
Related:
root-project/jenkins-pipelines#10
root-project/gcc-problem-matcher-improved#10