failure
Release
queued <1s ran 27s total 28s
1 jobs
1 failed
28s duration
— tests
0 artifacts
Unclassified failure The failure didn't match a known signature. Open the log — and this is a signal our classifier needs a new pattern.
release
failurerelease
successactions/checkout@v4 1s
successResolve the tag 2s
successInstall Nim and zig 3s
successVersions <1s
successactions/cache@v4 <1s
successTest 2s
successBootstrap nimstatic on the host 3s
failureBuild the static binary with itself 12s
skippedAttach the binaries to the release
skippedactions/upload-artifact@v4
No test reports for this run.
Tell a job where its test runner writes its report and this tab fills in: how many tests passed, failed and were skipped, a bar of the result at a glance, then every failure first — with the assertion that failed and the output around it — over a per-suite list of cases and their durations. No scrolling a log for the word FAIL.
It is one reports: key on the job — a job key, not a step, so the report is collected whatever the job concluded. JUnit XML and go test -json are both understood, and most runners already emit one of them. reports: is a rickub extension and works only in .rickub/workflows/; in .github/workflows/ it is a parse error on purpose, because those files are also meant to run on github.com.