[
https://issues.apache.org/jira/browse/HDDS-9301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated HDDS-9301:
---------------------------------
Labels: pull-request-available usability (was: usability)
> Fail checks in Summary step instead of Test
> -------------------------------------------
>
> Key: HDDS-9301
> URL: https://issues.apache.org/jira/browse/HDDS-9301
> Project: Apache Ozone
> Issue Type: Sub-task
> Components: CI
> Reporter: Attila Doroszlai
> Assignee: Attila Doroszlai
> Priority: Minor
> Labels: pull-request-available, usability
>
> 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
