Repository navigation
fix: skip POSIX outcome API fixtures on Windows - #71247
Conversation
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
|
✅ Design Decision Gate 🏗️ completed the design decision gate check. See the comment below for the result and any generated ADR draft. Design Decision Gate 🏗️Outcome: The agent completed and reported no action. A no-op output alone does not verify that all required work was completed or that publication was possible. Agent messages are omitted from this comment. The category uses structured run status, not interpretation of agent prose.
|
|
🧠 Matt Pocock Skills Reviewer has completed the skills-based review. ✅
|
|
✅ Test Quality Sentinel completed test quality analysis. Test Quality SentinelOutcome: The agent completed and reported no action. A no-op output alone does not verify that all required work was completed or that publication was possible. Agent messages are omitted from this comment. The category uses structured run status, not interpretation of agent prose.
|
|
✅ PR Code Quality Reviewer completed the code quality review.
|
|
✅ Ponytail Reviewer completed successfully! Ponytail ReviewerOutcome: The agent completed and reported no action. A no-op output alone does not verify that all required work was completed or that publication was possible. Agent messages are omitted from this comment. The category uses structured run status, not interpretation of agent prose.
|
There was a problem hiding this comment.
Skills-Based Review 🧠
Small, surgical fix — approving.
📋 Analysis
This change adds a runtime.GOOS == "windows" skip guard to installOutcomeAPIFixture, with the exact same skip message already used in run_workflow_validation_test.go. Applying /diagnosing-bugs and /codebase-design lenses:
- Root cause matches symptom: the fixture writes a POSIX
#!/bin/shscript asgh, which Windows cannot execute — skipping on Windows is the correct, minimal fix rather than attempting to fake cross-platform shell execution. - Consistent with existing convention: identical skip pattern and message already established elsewhere in the test suite, so no new abstraction or vocabulary is introduced.
- Scope is appropriately narrow: only the fixture-installing helper is skipped; the PR description confirms platform-independent cache tests remain enabled on Windows, preserving coverage where possible.
- No regression test is needed here since this is a CI-environment compatibility fix, not a logic bug — the "regression" being prevented is a false failure, not behavior.
Nothing actionable found; this is a model example of fixing a flaky/broken-on-Windows test the same way prior precedent did.
🧠 Reviewed using Matt Pocock's skills by Matt Pocock Skills Reviewer · copilot · sonnet50 · ~13 AIC · ⌖ ~15 AIC · ⊞ 10.2K
Comment /matt to run again
There was a problem hiding this comment.
Review summary
No blocking correctness issues found in the changed test-only platform guard. The Windows skip is consistent with the POSIX shell fixture limitation; cache-only tests remain available on Windows. Static review only; no tests were run by this review.
🔎 Code quality review by PR Code Quality Reviewer · copilot · gpt50 · ~2 AIC · ⌖ ~1 AIC · ⊞ 1.6K
Comment /review to run again
There was a problem hiding this comment.
🟢 Approval recommended
The minimal, test-only guard targets the unsupported fixture without affecting portable tests or production code.
No open issues 🎉
What changed in this PR
Fixes Windows CI failures by skipping outcome API tests that depend on a POSIX shell-backed gh fixture.
Changes:
- Adds a Windows-only skip in the shared fixture helper.
- Leaves platform-independent cache tests enabled and production behavior unchanged.
| File | Description |
|---|---|
pkg/cli/outcome_api_cache_test.go |
Imports runtime and skips the unsupported shell fixture on Windows. |
Review effort: Max
|
🎉 This pull request is included in a new release. Release: |
Summary
Windows CI fails because the outcome API test fixture installs a POSIX shell script as
gh, which Windows cannot execute. Skip tests using this fixture on Windows, matching the existing convention for shell-backed CLI mocks.Platform-independent cache tests remain enabled on Windows. Production behavior is unchanged.
Validation
make build,make fmt, andmake agent-report-progresspassed, including impacted tests and workflow drift checks.