Repository navigation
🐛🧑💻 - Dogfooding make Windows verification fixture startup and failure evidence explicit #488
Description
Description
Hosted Windows job 115329566454 failed in the standalone verification-environment PowerShell fixture after about 61 seconds. The nested script collapses every child error or nonzero exit to code 2, so Jest shows Expected 0 / Received 2 and hides the child error code. This is ordinary Windows PowerShell/tool coverage, unrelated to the retired Codex-on-Windows-services integration.
Expected: the fixture should report bounded child status/error evidence and use the same explicit trusted system-module startup as the existing production probes. Keep real execution, the sandbox distinction, current timeouts and all platform gates. Do not skip or weaken the Windows fixture.
Additional live evidence: hosted Windows job 115329838256 on PR #487 passed all 95 isolated runtime fixture cases. Its full suite then passed the literal-argv execution assertions, but cleanup at agent_executable_invocation.test.ts:141 raised EPERM removing the unique temporary fixture directory. Include the same finite rmSync retry pattern already used by other Windows fixtures; preserve every execution assertion and require eventual cleanup success. Do not attribute the lock to a specific process without evidence.
Reproducing the issue
- Run the existing Setup Platform Smoke matrix on PR [#482] 🐛 - Dogfooding progress cards remain active after native issue closure #483, head e462afe.
- In the hosted Windows isolated agent runtime fixtures, inspect agent_windows_runtime.test.ts:48–65.
- The fixture resolves the trusted system root, starts real PowerShell and requests Get-FileHash using implicit command/module discovery, while other trusted probes already import the exact system modules explicitly.
- A child failure becomes only exit 2. Record the failing job and repeat the same Windows job after the correction; preserve the original failure instead of declaring a root cause from the elapsed time alone.
copilot Version
3.3.1; master c485de3.
Metadata
Metadata
Assignees
Labels
Type
Projects
- Status
Activity
[-]Dogfooding: make Windows verification fixture startup and failure evidence explicit[/-][+]🐛 - Dogfooding make Windows verification fixture startup and failure evidence explicit[/+]vypbot commentedon Oct 13, 2026
Hi! I’m @vypbot, the Copilot assistant for this repository.
I can answer questions, explain the codebase, propose implementation and test plans, review issues and pull requests for potential bugs or security problems, and help authorized maintainers apply changes.
Try
/copilot helpto see the available commands, or mention @vypbot with your question.11 remaining items
vypbot commentedon Oct 13, 2026
Issue closed — historical progress
Current status: closed as completed.
The last estimate is retained below as history. Closure does not certify a new percentage, tests, or branch alignment.
Action required: none for this closed issue. If work continues, reopen the issue; a fresh assessment can update this same card.
Last assessment before closure (historical)
vypbot commentedon Oct 13, 2026
Branch synchronized
developwas merged intobugfix/488-dogfooding-make-windows-verification-fixture-startup-and-failure-evidence-explicitand pushed as35a2ad50d9337321e0b10f3329545d1cee3e083f.6 verification checks passed.
vypbot commentedon Oct 13, 2026
Branch synchronization needs attention. Open the current status.
Merge pull request #489 from vypdev/bugfix/488-dogfooding-make-window…