failure
build
queued <1s ran 13s total 13s
4 jobs
1 failed
13s 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.
failuredart-test
successactions/checkout@v4 <1s
failureapt-get update -qq && apt-get install -y -qq nim 10s
Run
apt-get update -qq && apt-get install -y -qq nim
skippedcd nim && nim c --app:lib --mm:orc -d:release --hints:off --path:src \
Run
cd nim && nim c --app:lib --mm:orc -d:release --hints:off --path:src \ --out:../build/nim/libfrqcore.so src/frq_core.nim
skippedcd dart/frq_core && dart pub get && dart test -r expanded
Run
cd dart/frq_core && dart pub get && dart test -r expanded
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.