GB-065: the trunk could not be fetched, so the checkout cannot be shown current¶
Generated from ops/errors/catalog.yaml by ops/ci/check-error-catalog.py --write; do not edit here. GB-065 is printed by goatbuilder. The same text offline: goat explain GB-065 or goatbuilder explain GB-065.
What it means¶
A real run proves its checkout is current with the trunk before any host is touched (contract C3). The trunk remote did not answer a fetch, so that proof is missing and the run is refused. An islanded site, cut off by design, runs with --offline: it is judged against the cached trunk and the ledger row it writes says source: offline.
Why it happens¶
- no route to the git remote (the laptop is offline, the forge is down)
- the remote's credentials are not loaded (an ssh key not in the agent)
What to do¶
One line per step or alternative:
restore the connection to the trunk remote and re-run
on an islanded site: re-run with --offline
Read more¶
Exit code¶
goatbuilder exits with 1.