fix(ci): match staged KVM processes - #7929
Conversation
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
|
🚀 Security Guard has started processing this pull request |
There was a problem hiding this comment.
Copilot review overview
🟡 Changes recommended
The system-wide probes can mistake unrelated virtualization processes for AWF processes, causing false failures or liveness results.
Once you've addressed the issues Copilot identified, you can request another Copilot review.
Review tier: Balanced
Findings: 1
New issues introduced by this change (1)
| Severity | Finding |
|---|---|
scripts/ci/cloud-hypervisor-live-smoke.sh — This system-wide pattern now treats any host virtiofsd using --shared-dir as residue from this… |
What changed in this PR
Updates live-KVM process probes to recognize AWF’s staged Cloud Hypervisor artifacts.
Changes:
- Removes source artifact-directory prefixes from process probes.
- Adds staged virtiofsd regression coverage.
| File | Description |
|---|---|
scripts/ci/cloud-hypervisor-live-smoke.sh |
Broadens residue and liveness probes. |
scripts/ci/cloud-hypervisor-ci-scripts.test.ts |
Updates process-probe assertions. |
Suppressed comments (2)
scripts/ci/cloud-hypervisor-live-smoke.sh:572
- The broadened probe can be satisfied by any unrelated Cloud Hypervisor process on the host. Because the surrounding checks are also global, that can make this loop conclude the crash fixture is ready and SIGKILL the AWF owner before this run's VMM has started. Match the verified AWF snapshot path under
/run/awf-cloud-hypervisor/trusted-artifacts/run-*instead of any executable namedcloud-hypervisor.
sudo pgrep -f '[c]loud-hypervisor --api-socket' >/dev/null; then
scripts/ci/cloud-hypervisor-live-smoke.sh:594
- This check no longer proves that the VMM belonging to the killed AWF run survived; any host process whose command line contains
cloud-hypervisor --api-socketmakes it pass. Scope the probe to AWF's trusted per-run snapshot hierarchy so a foreign VMM cannot mask premature termination of the process under test.
sudo pgrep -f '[c]loud-hypervisor --api-socket' >/dev/null || {
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
|
✅ Copilot review passed with no inline comments. @lpcox Add the |
✅ Coverage Check PassedOverall Coverage
📁 Per-file Coverage Changes (1 files)
Coverage comparison generated by |
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
|
🔌 Smoke Services — All services reachable! ✅
|
|
📰 VERDICT: Smoke Docker Sbx has concluded. All systems operational. This is a developing story. 🎤
|
|
🛡️ Smoke Copilot Network Isolation confirmed the egress allowlist is enforced. ✅ Warning Firewall blocked 1 domainThe following domain was blocked by the firewall during workflow execution:
To allow these domains, add them to the network:
allowed:
- defaults
- "example.com"See Network Configuration for more information.
|
|
✅ Smoke Copilot BYOK AOAI (Entra) completed. Copilot AOAI BYOK (Entra) mode operational. 🔓
|
|
✨ The prophecy is fulfilled... Smoke Codex has completed its mystical journey. The stars align. 🌟 Warning Firewall blocked 2 domainsThe following domains were blocked by the firewall during workflow execution:
To allow these domains, add them to the network:
allowed:
- defaults
- "msfeed25.pkgs.visualstudio.com"
- "registry.npmjs.org"See Network Configuration for more information.
|
|
✅ Smoke Copilot BYOK completed. Copilot BYOK mode operational. 🔓
|
|
✅ Build Test Suite completed successfully!
|
|
❌ Smoke Gemini reports failed. Facets need polishing...
|
|
✅ Contribution Check completed successfully! Contribution check complete: the PR description is clear, references the related issue/PR context, and the change stays within the correct
|
|
Chroot tests passed! Smoke Chroot - All security and functionality tests succeeded.
|
|
📰 VERDICT: Smoke Copilot has concluded. All systems operational. This is a developing story. 🎤
|
|
📡 Smoke OTel Tracing completed. All tracing scenarios validated. ✅
|
|
✅ Smoke Copilot BYOK AOAI (api-key) completed. Copilot AOAI BYOK (api-key) mode operational. 🔓
|
|
🚀 Security Guard has started processing this pull request |
|
✅ Smoke Claude passed Warning Firewall blocked 1 domainThe following domain was blocked by the firewall during workflow execution:
To allow these domains, add them to the network:
allowed:
- defaults
- "api.anthropic.com"See Network Configuration for more information.
|
|
EGRESS_RESULT allow=pass deny=pass ✅ Allowed domain (github.com) reachable: allowed=200 Overall: PASS @lpcox network isolation egress enforcement verified. Warning Firewall blocked 1 domainThe following domain was blocked by the firewall during workflow execution:
To allow these domains, add them to the network:
allowed:
- defaults
- "example.com"See Network Configuration for more information.
|
Smoke Test: Copilot BYOK (Direct) Mode — ✅ PASS
Running in direct BYOK mode (COPILOT_PROVIDER_API_KEY) via api-proxy → api.githubcopilot.com.
|
|
Smoke Test: GitHub Actions Services Connectivity — FAIL
Overall: FAIL —
|
|
Smoke Test: Copilot Engine — @lpcox
Overall: PASS
|
Chroot Version Comparison Results
Overall: FAILED — Node.js version mismatch between host and chroot environments. Label not added since not all tests passed.
|
|
Smoke Test: Docker Sbx — @lpcox
✅ GitHub.com connectivity (HTTP 200) Overall: FAIL
|
Smoke Test: Claude Engine Validation
Overall result: PASS Warning Firewall blocked 1 domainThe following domain was blocked by the firewall during workflow execution:
To allow these domains, add them to the network:
allowed:
- defaults
- "api.anthropic.com"See Network Configuration for more information.
|
|
fix: avoid self-matching KVM process probes (#7927) ✅ Playwright title check Warning Firewall blocked 2 domainsThe following domains were blocked by the firewall during workflow execution:
To allow these domains, add them to the network:
allowed:
- defaults
- "msfeed25.pkgs.visualstudio.com"
- "registry.npmjs.org"See Network Configuration for more information.
|
|
✅ fix: avoid self-matching KVM process probes (#7927) Running in direct BYOK mode (COPILOT_PROVIDER_API_KEY + COPILOT_PROVIDER_BASE_URL) via api-proxy -> Azure OpenAI (Foundry, o4-mini-aw) Overall: PASS
|
|
fix: avoid self-matching KVM process probes
|
|
Smoke Test: API Proxy OTEL Tracing — Results
Overall: all scenarios pass or behave as expected for current development state.
|
🏗️ Build Test Suite Results
Overall: 8/8 ecosystems passed — PASS Notes:
|

Summary
Context
#7927 was externally merged while its labeled live-KVM run was still executing. That run proved the self-excluding path-specific expression no longer matched itself, but also revealed it could not match AWF's staged runtime copy. This follow-up preserves the narrow probe fix while matching the real command line.
Validation
npm test -- --runInBand scripts/ci/cloud-hypervisor-ci-scripts.test.ts scripts/ci/test-cloud-hypervisor-workflow.test.tsbash -n scripts/ci/cloud-hypervisor-live-smoke.shnpm run buildnpm run lintnpm test -- --runInBand