ci: raise test-step / job timeouts for the full debug test suite#445
Merged
Conversation
Once CompressionFamily resolved (v10.9.3 always-URL dep + the published public repo), CI got past dependency resolution and reached the test step for the first time — where ci.yml's `Run tests` hit its 20-minute step cap mid-suite. The full ~6000-test debug `swift test --parallel` on a GitHub macOS runner exceeds 20 min (the local *release*-mode full run is ~13 min on a warm M2; CI runs debug on a slower runner). The earlier fast CompressionFamily-resolution failure had masked this. - `swift test` steps: 20 → 60 min (ci, code-quality, swift-build-test; dicomkit's downstream test step too). - Jobs that build + test: → 75 min, to cover a cold debug build + tests + release build (ci build-macos, code-coverage, all conformance jobs, swift-build-test, jp3d, interactive-testing, performance, dicomkit-build). - Lint-only and `swift package resolve/describe`-only jobs unchanged. Co-Authored-By: Claude Opus 4.7 <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
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.
Why
With
CompressionFamilynow published and v10.9.3's always-URL dependency in place, CI resolves the package and — for the first time — reaches the test step.ci.yml'sRun testsstep then hit its 20-minute cap mid-suite:The full ~6000-test debug
swift test --parallelon a GitHub macOS runner exceeds 20 min. (The local release-mode full run is ~13 min on a warm M2; CI runs debug on a slower runner.) The earlier fast CompressionFamily-resolution failure had masked this — the build/test never previously ran far enough to hit it.Not a regression and not a code defect: the tests pass (local release-mode gate 22/22, full suite 6148/0). Purely a CI step-timeout.
Change
swift teststeps → 60 min (ci.yml,code-quality.yml,swift-build-test.yml; the DICOMKit downstream test step).cibuild-macos,code-coverage, all 6conformancejobs,swift-build-test,jp3d-compliance,interactive-testing, bothperformancejobs,dicomkit-build).swift package resolve/describe-only jobs unchanged.All 8 workflow YAMLs parse.
🤖 Generated with Claude Code