ci: run swift build and swift test on every push and PR - #14
Merged
Conversation
This repo carried a full test suite that no CI job ever executed, so a failing test produced a green tick. Recorded fleet-wide as ecosystem#40, where 12 of the 14 repos in the OCCT stack had the same gap. swift build and swift test are separate steps deliberately: swift build does not compile test targets, so on its own it is a weaker signal than it appears. Baseline measured locally before rollout.
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Files Reviewed (1 file)
Reviewed by nemotron-3-ultra-550b-a55b:free · Input: 62.1K · Output: 2.3K · Cached: 34.6K |
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
1 participant
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.
Adds a blocking
testsworkflow runningswift buildthenswift teston every push and PR.Part of the fleet-wide rollout in ecosystem#40: 12 of the 14 repos in the OCCT stack ran no tests in CI at all, so a failing test produced a green tick. This repo was one of them.
That gap is not hypothetical. Five assertions in OCCTSwiftAIS sat broken for nine days (OCCTSwiftAIS#46) because nothing in its pipeline ever compiled a test target.
swift buildandswift testare separate steps on purpose.swift builddoes not compile test targets, so it is a weaker signal than it looks: OCCTSwiftIO built clean with zero errors while carrying three real breaks in its test target during the OCCTSwift v3.0.0 repin.Modelled on
OCCTSwiftScripts/.github/workflows/tests.yml, which already solved this once:macos-15,actions/cacheon.buildkeyed byPackage.resolved, blocking rather thancontinue-on-error.Baseline was measured locally before rollout rather than assumed. See the workflow's own header comment for this repo's count.
Notes for the reviewer
Nothing but the workflow file is added. No source, manifest or doc change.