success
build
queued <1s ran 2m11s total 2m11s
3 jobs
0 failed
2m11s duration
— tests
1 artifacts
Stage 1
successnim-test
successactions/checkout@v4 <1s
successOpenSSL headers 3s
Run
sudo apt-get update -qq && sudo apt-get install -y -qq libssl-dev
successNim ${{ env.NIM_VERSION }} 1s
Run
set -euo pipefail
url="https://nim-lang.org/download/nim-${NIM_VERSION}-linux_x64.tar.xz"
curl -fsSL -o /tmp/nim.tar.xz "$url"
echo "${NIM_SHA256} /tmp/nim.tar.xz" | sha256sum -c -
mkdir -p /opt/nim && tar -xJf /tmp/nim.tar.xz -C /opt/nim --strip-components=1
echo "/opt/nim/bin" >> "$GITHUB_PATH"
successThe Nim suite 24s
Run
cd nim && for t in tests/t*.nim; do nim c -r --hints:off --path:src "$t"; done
successBuild libfrqcore.so 5s
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. Worth reading: Nim resolves OpenSSL through # dlopen rather than a link-time NEEDED, so libssl will not appear # here and the Dart job still has to have one installed. objdump -p ../build/nim/libfrqcore.so | grep NEEDED || true
successactions/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.