success
build
queued <1s ran 2m00s total 2m00s
3 jobs
0 failed
2m00s duration
— tests
1 artifacts
Stage 1
successdart-test
successactions/checkout@v4 <1s
successDart ${{ env.DART_VERSION }} 13s
Run
set -euo pipefail
url="https://storage.googleapis.com/dart-archive/channels/stable/release/${DART_VERSION}/sdk/dartsdk-linux-x64-release.zip"
curl -fsSL -o /tmp/dart.zip "$url"
echo "${DART_SHA256} /tmp/dart.zip" | sha256sum -c -
sudo unzip -q /tmp/dart.zip -d /opt
echo "/opt/dart-sdk/bin" >> "$GITHUB_PATH"
successsudo apt-get update -qq && sudo apt-get install -y -qq libssl3 1s
Run
sudo apt-get update -qq && sudo apt-get install -y -qq libssl3
successactions/download-artifact@v4 <1s
successcd dart/frq_core && dart pub get && dart test -r expanded 5s
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.