failure
build
queued 1m11s ran 28s total 1m39s
2 jobs
1 failed
1m39s duration
— tests
1 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.
Stage 1
Stage 2
successcheck-common
successSet up job
cloning nandi/frq @ 41bcb21f91e3c96a7904248af5109c23fc99e1b2
successactions/checkout@v4 <1s
(checkout already performed by the runner — delivered as the read-only work disk)
successpython3 tools/check-common.py common 4s
Run
python3 tools/check-common.py common
ciguest: network up (172.30.0.10/30 via 172.30.0.9)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 rickubcommon/ is clean: nothing here that only one backend has.
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.