Skip to content

GB-014: a live validation row failed

Generated from ops/errors/catalog.yaml by ops/ci/check-error-catalog.py --write; do not edit here. GB-014 is printed by goatbuilder. The same text offline: goat explain GB-014 or goatbuilder explain GB-014.

What it means

the candidate deployed and a live row on the goatnet failed. On dev the candidate is dead; on preprod after a dev pass it stays open for investigation.

Why it happens

  • a row exited 2 — it was never run: its toolchain is missing on this laptop (Playwright for the intake rows, a goat context for the invite rows); the candidate is untested, not dead
  • a real regression in the candidate
  • the row's runner settings are stale for this goatnet

What to do

One line per step or alternative:

if the row exited 2: install what it names (goatbuilder doctor --browser-tests fails on a missing browser toolchain, tool:live-rows; tool:goat-contexts names a missing goat context), then resume with --from rows — do not delete the tag
ops/validation/flow-map.yaml names the rows; read the failed row's evidence under ops/validation/evidence/
fix on main and cut the next rc (dev), or investigate before graduating (preprod)

Read more

Exit code

goatbuilder exits with 1.