nandi/frqpublic Fork
⑂ main
Commits
⬇ Clone ▾
git clone https://git.rickub.com/nandi/frq.git
git clone ssh://git@rickub.com/nandi/frq.git

Host key fingerprint (ed25519): SHA256:iycHnxEyq0Q7uyVpB7JlznP0G7JrTPXLYRcAU5CSLhc — verify it before your first connect.

Download ZIP
failure

build #5

push · main · f7aea3bbran in 13s
queued <1s ran 13s total 13s
4 jobs
1 failed
13s duration
— tests
0 artifacts
failuredart-test → apt-get update -qq && apt-get install -y -qq nim View log
Unclassified failure The failure didn't match a known signature. Open the log — and this is a signal our classifier needs a new pattern.
check-common
nim-test
dart-test
web
queued
successnim-test 12s
successactions/checkout@v4 <1s
successcd nim && for t in tests/t*.nim; do nim c -r --hints:off --path:src "$t"; done 11s
Run
cd nim && for t in tests/t*.nim; do nim c -r --hints:off --path:src "$t"; done

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.