build
successactions/checkout@v4 <1s
successactions/setup-python@v5 6s
successpip install --disable-pip-version-check modal 3s
successBuild the web bundle, on Modal 1m45s
failureFetch the bundle out of the volume 1s
skippedactions/upload-artifact@v4
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.