Repository navigation
ci: exclude desktop gate tests from the headless run - #4
Merged
Merged
Conversation
The Phase1 gate tests launch real apps and stall on a headless runner, so no test has produced a usable CI result. They still run locally. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Excludes the
Phase1*Gatetests from CI so the rest of the suite can produce a result.Those tests launch real desktop apps, with no guard for a headless runner. With the hang timeout from #3,
Phase1GateTests.CalculatorGate_ArithmeticFlow2Plus3Equals5failed in 1 second and the run then stalled until it was killed, so no test has given CI a usable result.Trade-off
The gate tests stop running in CI, so a regression there won't show up. They never finished in CI before, so this loses no real coverage, and they still run locally with
dotnet test. A better long-term fix is a runner with an interactive desktop, or skip guards in the tests.Verification
This PR's CI run is the test. Only
.github/workflows/ci.ymlchanges.🤖 Generated with Claude Code