GB-042: the live rows cannot run from this machine — the candidate is UNTESTED, not dead¶
Generated from ops/errors/catalog.yaml by ops/ci/check-error-catalog.py --write; do not edit here. GB-042 is printed by goatbuilder. The same text offline: goat explain GB-042 or goatbuilder explain GB-042.
What it means¶
a release step reached the live acceptance rows, and this machine lacks what they need (the console's Playwright toolchain for a browser row, or a tool or context the runner reported with exit 2). The rows did not run; nothing about the candidate failed.
Why it happens¶
- a browser row is mapped and ops/goat-id-console/web/e2e/node_modules is missing, or node/npm is not installed
- the acceptance runner exited 2 (a tool or a goat context missing on this machine or on the host it runs goat on)
What to do¶
One line per step or alternative:
(cd ops/goat-id-console/web/e2e && npm ci && npx playwright install chromium), then re-run the same command
read the runner's output above for the missing tool or context, fix it, re-run the same command — never delete the tag
Read more¶
Exit code¶
goatbuilder exits with 1.