nvx-triage-ci-run
Triage a failed, cancelled, or hanging microsoft/nvx GitHub Actions run: classify supersession and queueing, find the first causal failure for the exact head, reproduce it on the matching platform, and fix it locally without committing. Use for workflow run URLs or IDs, red pull-request checks, runner, matrix, and artifact-handoff failures, and performance-gate or benchmark-host failures.
- License 许可
- MIT
- 所属仓库
- microsoft/nvx
- 最近更新
- 2026-11-15
- Stars
- ★ 841
- Forks
- 59
01 前言 Front Matter
- name
- nvx-triage-ci-run
- description
- Triage a failed, cancelled, or hanging microsoft/nvx GitHub Actions run: classify supersession and queueing, find the first causal failure for the exact head, reproduce it on the matching platform, and fix it locally without committing. Use for workflow run URLs or IDs, red pull-request checks, runner, matrix, and artifact-handoff failures, and performance-gate or benchmark-host failures.
- argument-hint
- <workflow run URL or ID, or #pull-request>
03 SKILL.md 正文
Triage An NVX CI Run
Find the first causal failure of one exact head, reproduce it at the narrowest
scope, and fix repository defects without committing or pushing. Commands use
python3; use python on Windows.
-
Record the branch,
HEAD, the status of NVX andopenvmm/, and any Git operation in progress. Never reset, clean, discard, switch, stash, or update the submodule without permission. -
Classify the run before treating it as a defect:
python3 scripts/ci_triage.py <run URL, run ID, or #PR>It resolves exactly one run and reports its attempt, event, and head; the pull request's current head and draft state; a classification; the failed jobs with their first failed step, runner, and matrix values; the first error in each failed log; earlier failures of the same jobs on
dev; and open issues that name them. Act on the classification:superseded: report the replacement run and stop, unless the cancelled run's cleanup failed.merge-group-cancelled: check the pull request's queue outcome first.dev-push-cancelled:devpushes queue rather than replace each other, so investigate it.benchmark-host-changed: the runner is no longer the host of its series' history, an infrastructure change; accept the host and reset the history only on request, as Expected benchmark hosts describes.
A run that started while its pull request was Ready keeps running after the pull request becomes a draft; that is not the draft guard failing. Bind every conclusion to that run's attempt and head, and never take an older green run as evidence for the current head.
-
Read the complete logs of the failed jobs where the excerpt is not enough (
gh run view RUN --repo microsoft/nvx --job JOB --log-failed), and the workflow, actions, scripts, and tests as they were at the run's commit (git show SHA:PATH). Separate the first cause from matrix cancellations, cleanup failures, and secondary errors. State one falsifiable hypothesis that a decisive log line and the owning code path support, and classify it as a product, test, workflow, dependency or toolchain, transient infrastructure, or missing-prerequisite failure. Change no code for an external or transient failure unless the repository has a concrete robustness defect. -
Reproduce the earliest actionable failure with the narrowest equivalent command, on the run's platform and backend:
- quality and CLI failures:
python3 scripts/local_gates.py --run --only GATE --files PATH..., with the paths that the run's change touched (git diff --name-only BASE SHA), since--onlykeeps only the gates that those paths select and fails for any other; or the failed step's command; - boot, microVM, snapshot, guest-console, and benchmark acceptance failures: nvx-run-microvm, after nvx-prepare-host selects a profile with the run's backend and host type;
- performance regressions: compare the platform, ABI, processor count, metric direction, sample, and baseline window first, and reproduce only on the same host and series, with nvx-collect-benchmarks.
Do not switch the checkout to the run's commit, install packages, change runners, elevate privileges, or repair hosts without approval, and report when the exact commit cannot run.
- quality and CLI failures:
-
Fix the controlling code path with the smallest coherent change, never by weakening assertions, disabling tests, broadening retries, swallowing errors, or hiding output. Rerun the reproduction, then the original failed command, then
python3 scripts/local_gates.py --run, and add regression coverage when behavior changes. -
Do not commit, push, rerun or cancel runs, or change the pull request unless asked. When asked to push and follow CI, follow only the run of the pushed head, with one watcher, and rebind once when a newer head supersedes it.
Report
Report the run's URL, attempt, and head; the failed job and step; the
classification; the decisive evidence and the root cause; the files changed;
the reproduction and validation commands with their results; any replacement
run; blocked checks; and the final status of NVX and openvmm/. Confirm that
nothing was committed or pushed.
04 同仓库更多 Skills
nvx-run-microvm
Boot an NVX microVM with nvx-rs on Linux/KVM, Linux/MSHV, or Windows/WHP, exercise the guest, and debug failed boots. Use for boot smoke tests, guest shell sessions, virtio-fs mounts, networking, kernel command lines, missing boot markers, OpenVMM errors, guest hangs, and benchmark acceptance failures.
nvx-rebase-openvmm-chain
Rebase or reorganize the OpenVMM microVM chain onto the latest upstream main as a new feature/microvm/release branch, validate and publish it, pin it in NVX with a remapped roadmap, and land it. Use for microVM release rebases and reorganizations, chain commits that upstream landed, rebase conflicts and fixups, and the release landing order.
nvx-promote-openvmm-pin
Pin a reviewed OpenVMM revision in NVX: verify its provenance and signature, commit the gitlink and the OpenVMM roadmap mapping, validate the exact pin, and land the OpenVMM pull request by fast-forward. Use for OpenVMM pin updates, clean replacement pull requests, source-equivalence checks, and mapping new chain commits in the OpenVMM upstream roadmap.
nvx-prepare-host
Prepare a local host or a configured SSH host for NVX work: resolve its profile, probe its KVM, MSHV, or WHP backend and checkout, check out the requested revision in a temporary worktree, and stage nvx-rs and the artifacts. Use before running, debugging, or benchmarking NVX on a host, or to diagnose a host's prerequisites.
nvx-fix-issue
Fix one microsoft/nvx issue end to end: reproduce it on the configured hosts, commit signed fixes, open a Ready pull request against dev, and drive CI and review until only a maintainer's approval remains. Use when invoked with an NVX issue number or URL.
nvx-collect-benchmarks
Collect fresh NVX benchmark results on a prepared Linux/KVM, Linux/MSHV, or Windows/WHP host with the smoke, CI-equivalent, or canonical profile. Use for acceptance runs, performance suites, p50 collection, benchmark artifacts, and same-host performance comparisons.