failure
CI
queued <1s ran 6s total 6s
1 jobs
1 failed
6s duration
— tests
0 artifacts
Action fetch failed The action couldn't be fetched from the git host — GitHub may be rate-limiting anonymous requests. A maintainer can configure an actions token.
fmt / vet / test / build
failurefmt / vet / test / build
successCheckout <1s
failureSet up Go 2s
skippedgofmt
skippedgo vet
skippedgo test
skippedgo build
skippedCross-compilation smoke test
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.