failure
web
queued 1s ran 12s total 13s
2 jobs
1 failed
13s duration
— tests
0 artifacts
Image build failed A container image build step failed. Check the build context and Dockerfile in the log.
Stage 1
image
deploy
queued
failureimage
successactions/checkout@v4 <1s
failureBuild and push 11s
Run
set -euo pipefail
image="$RICKUB_REGISTRY_HOST/${{ github.repository }}-web:${{ github.sha }}"
moving="$RICKUB_REGISTRY_HOST/${{ github.repository }}-web:latest"
docker build -f .modal/web/Dockerfile -t "$image" -t "$moving" .
docker push "$image"
docker push "$moving"
echo "image=$image" >> "$GITHUB_OUTPUT"
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.