From e05c73e15f81b2f675f626330744d9995cb7d420 Mon Sep 17 00:00:00 2001 From: Brian Ketelsen Date: Fri, 7 Aug 2026 11:33:45 -0400 Subject: [PATCH] docs(ci): explain nested testsuite refs Document that a reusable workflow uses ref and its test checkout ref control separate delivery layers, so promotion triage checks both. Refs #929 Assisted-by: GPT-5.6 Sol via GitHub Copilot Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- docs/skills/ci/references/failure-modes.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/docs/skills/ci/references/failure-modes.md b/docs/skills/ci/references/failure-modes.md index 86c20ebb..ce13c833 100644 --- a/docs/skills/ci/references/failure-modes.md +++ b/docs/skills/ci/references/failure-modes.md @@ -7,5 +7,12 @@ | Workflow did not trigger | Event, branch, and path filters in the YAML | | Promotion is blocked | Exact digest, required check, and merge-group state | | Shared action behaves incorrectly | Reusable workflow source and its callers | +| Tests update but E2E setup stays stale | Compare the reusable workflow `uses` ref with its test checkout ref | Always inspect the failed run logs before changing a workflow. + +A reusable testsuite workflow has two independent refs: `uses` selects the +workflow definition and `test_ref` selects the test tree it checks out. A +managed `test_ref` does not deliver workflow-level fixes such as VM disk sizing +when `uses` is pinned to an older commit. Keep both layers on the documented +managed ref, and verify the nested workflow shown in the run log.