Skip to content

docs(ci): explain nested testsuite workflow refs #1014

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
bketelsen wants to merge 1 commit into from
Closed

docs(ci): explain nested testsuite workflow refs #1014

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions docs/skills/ci/references/failure-modes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.