failure
ci
queued 1s ran 3s total 3s
1 jobs
1 failed
3s 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.
test
failuretest
successSet up job
cloning rickub/portal @ fe0fb3124c55eec335cd34ad6816afe1751e6947
successactions/checkout@v1 <1s
(checkout already performed by the runner — delivered as the read-only work disk)
failurego build ./... 2s
Run
go build ./...
ciguest: network up (172.30.0.2/30 via 172.30.0.1)ciguest: starting dockerd (overlay2, data-root on scratch)ciguest: dockerd is readyciguest: loaded baked image postgres_16-alpine.tar.gz: Loaded image: postgres:16-alpineciguest: 1 baked image archive(s) loaded (no per-job registry pull needed)ciguest: logged into registry registry.rickub.com as rickubbash: line 1: go: command not found
skippedgo vet ./...
Run
go vet ./...
(skipped: step if: condition evaluated to false)
skippedgo test ./...
Run
go test ./...
(skipped: step if: condition evaluated to false)step failed: exit code 127 — go build ./...
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.