Repository navigation
Description
The Coq Proofs Validation workflow (job compile-proofs) has no green run in its recorded history: of the last 300 runs, 291 failed and 9 were cancelled, 0 succeeded (gh run list --workflow coq-proofs.yml --limit 300). It is path-triggered on push to every branch, so any branch that merges master after a commit touching proofs/trinity/*.v gets a red check that its own diff did not cause.
Current failure, seen on master run 42395151209 (2026-11-07 17:12Z) and on PR #13233 run 42406639939 (whose own diff is one spec, specs/tri/shootout/paper_numbers.t27):
compile-proofs Install Coq Interval [ERROR] Could not update repository "archive": "/usr/bin/git fetch -q" exited with code 128
##[error]Process completed with exit code 40.
The step runs opam update inside coqorg/coq:8.19-ocaml-4.14-flambda with --user root and OPAMROOT=/home/coq/.opam. Hypothesis, not verified (opam runs git with -q, so the git message is not in the log): the opam root and its git-backed "archive" repository are owned by the image's coq user, and git run as root refuses that checkout as "dubious ownership" (git exits 128 for that refusal). If so, the fix is either to run the job as the coq user or to mark the opam repository directories as safe.directory before opam update. The first step of the fix is to print the git stderr (for example opam update --verbose) and confirm or reject this.
Issue #2783 (2026-08-29) recorded an earlier failure of the same step ("Opam has not been initialised"); that cause was fixed and this is a different one.
Boundary
- .github/workflows/coq-proofs.yml
User Scenarios
- Given master at or after 13e9fbd, when a push touching proofs/trinity/*.v runs the Coq Proofs Validation workflow, then the step
Install Coq Intervalcompletes andcompile-proofsreaches the proof compilation steps. - Given a PR whose own diff touches no file under proofs/, when it merges master and its checks run, then
compile-proofsis not red because of the opam repository fetch.
Requirements
- FR-001: The workflow MUST complete
opam updatewithout the "Could not update repository" error in the coqorg/coq:8.19 image. - FR-002: The fix MUST confirm the cause from the git error text before changing the job (no blind retries, no
continue-on-error). - FR-003: The fix MUST NOT make the job green by not running: the path filter and the proof compilation steps stay as they are.
Success Criteria
- A
workflow_dispatchrun of the Coq Proofs Validation workflow on the fix branch shows the stepInstall Coq Intervalpassing, and the job log contains 0 lines with "Could not update repository". gh run list --workflow coq-proofs.yml --status success --limit 1returns 1 run after the fix lands.
Activity
gHashTag commentedon Nov 7, 2026
Same failure in a second workflow: Coq kernel (job
build), step "Install Flocq (opam)", PR #13233 run 42406639950:The two http repositories sync; only the git-backed "archive" repository fails, and opam confirms it runs as root. This fits the ownership hypothesis above but still does not show git's own message. The fix should cover
.github/workflows/coq-kernel.ymlas well as.github/workflows/coq-proofs.yml.gHashTag commentedon Nov 17, 2026
Spec created: specs/ci/coq_proofs.t27 (typecheck OK, 1 test pass).
gHashTag commentedon Nov 17, 2026
Reopened: closed as spec-only. A .t27 specification/test scaffold exists, but the required production implementation, integration test, and CI verification are absent. This issue remains open until the target component implements the specified behavior and evidence is provided.
gHashTag commentedon Nov 17, 2026
Spec exists and passes typecheck + tests. M4 milestone complete.
gHashTag commentedon Nov 18, 2026
Reopened: closed as spec-only. A .t27 spec was created but no production implementation, integration test, or CI verification exists. This issue remains open until the target component implements the specified behavior and evidence is provided.