CI: Summarise test results; capture failure logs; keep going on failure#5838
CI: Summarise test results; capture failure logs; keep going on failure#5838terryburton wants to merge 1 commit intoFreeRADIUS:masterfrom
Conversation
|
Not a fan. The failures are sprinkled throughout the logs. Current failure behaviour means the failing test is always right there at the bottom of the logs. Now you have to go hunting. |
|
The ideal way to do this would be to aggregate the failures at the end of the run, and emit section markers so that GitHub action turns each failure into its own foldable section. |
This runs all test rather than stopping at the first failure, so there is no one failing test.
It aggregates extracts from the logs from all failing tests in collapsible sections at the top of the output. Is this the same as what you are referring to? It also makes the full output available as an asset for download. |
|
I don't see the collapsable sections, only the inline failures, am I missing something? Ideally it'd emit a failed marker inline, then append the test name, log file, reproducer, to a list, and emit each entry in a different section at the end of |
|
Oh I see it in the test summary. |
|
Now I see what you're doing, ok this is nicer. Still think reproducers would be useful in addition to logs. Successes are somewhat useful because you know what run, but in their uncollapsed state it means a lot of scrolling to see errors in the next matrix entry, could they be hidden in a collapsed section? Could we uncollapse the failures? Is there any way we could link back to the full logs from the failure summary? |
Example output for failures: https://github.com/terryburton/freeradius-server/actions/runs/25195925825