Details
-
Sub-task
-
Status: Resolved
-
Minor
-
Resolution: Implemented
-
None
Description
Ozone's CI check scripts (integration.sh, etc.) have 2 main conventions:
- exit with non-zero code if there are failed tests
- list failures in summary.txt or similar
Most CI jobs have a "Summary of failures" step, which provides a quick overview by showing the contents of summary.txt.
Github automatically expands the failed step, which according to these conventions is the main "Execute tests" step. The problem is that this can have very long output.
It would be better to exit with failure in the "summary" step, thus focusing the developer's attention on the quick overview, keeping the long output collapsed by default.
Attachments
Issue Links
- links to