failure
build
queued <1s ran 23s total 24s
4 jobs
1 failed
24s 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.
failurenim-test
successactions/checkout@v4 <1s
successapt-get update -qq && apt-get install -y -qq libssl-dev 8s
Run
apt-get update -qq && apt-get install -y -qq libssl-dev
successThe Nim suite 10s
Run
cd nim && for t in tests/t*.nim; do nim c -r --hints:off --path:src "$t"; done
successBuild libfrqcore.so 4s
Run
cd nim && nim c --app:lib --mm:orc -d:release --hints:off --path:src \ --out:../build/nim/libfrqcore.so src/frq_core.nim # Diagnostic, not a gate: prints what the .so will want at # runtime, so a missing libssl in the Dart job is obvious # from this log rather than from a StateError in that one. objdump -p ../build/nim/libfrqcore.so | grep NEEDED || true
failureactions/upload-artifact@v4 <1s
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.