failure
CI
queued <1s ran 3s total 4s
2 jobs
2 failed
4s 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.
failureBuild
successSet up job
cloning yatho/demo-angular-migration @ a99aac6e5752fb86510f90959f79833c5af471b4action pnpm/action-setup@v4: node20 (_actions/pnpm/action-setup/v4)action actions/setup-node@v4: node20 (_actions/actions/setup-node/v4)
successCheckout road-trip 2s
ciguest: network up (172.30.0.2/30 via 172.30.0.1)ciguest: starting dockerd (overlay2, data-root on scratch)ciguest: dockerd is readyciguest: loaded baked image postgres_16-alpine.tar.gz: Loaded image: postgres:16-alpineciguest: 1 baked image archive(s) loaded (no per-job registry pull needed)ciguest: logged into registry registry.rickub.com as rickubFrom http://172.30.255.1:8888/ci/git/yatho/demo-angular-migration * branch HEAD -> FETCH_HEAD
failureCheckout ui-kit <1s
fatal: could not read Username for 'https://github.com': terminal prompts disabled
skippedpnpm/action-setup@v4
(skipped: step if: condition evaluated to false)
skippedactions/setup-node@v4
(skipped: step if: condition evaluated to false)
skippedBuild ui-kit
Run
pnpm install --frozen-lockfile pnpm build
(skipped: step if: condition evaluated to false)
skippedInstall road-trip
Run
pnpm install --frozen-lockfile
(skipped: step if: condition evaluated to false)
skippedBuild road-trip
Run
pnpm build
(skipped: step if: condition evaluated to false)
Post actions/setup-node@v4
(post step skipped: the action's main step did not run)
Post pnpm/action-setup@v4
(post step skipped: the action's main step did not run)step failed: exit code 128 — Checkout ui-kit
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.