Full local bin/test runs fail 60 s time limits that CI passes
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
Research direction
Start by reading bin/test and check how it sets SWT_EXPERIMENTAL_MAXIMUM_PARALLELIZATION_WIDTH; compare the Swift versions used locally and in CI described in the issue. Then run bin/test --all and inspect the listed BoardModel suites and ProcessTests.runsMoreCommandsAtOnceThanThereAreCPUs if time limits still fail. Done means the full run passes without reducing any test's coverage.
Written by the indexing model from the issue text.
Description
A full local bin/test run fails tests that have a 60 s time limit, while CI passes them. The failing suites are the BoardModel suites with .timeLimit(.minutes(1)) (BoardModelAcknowledge, BoardModelPlan*, BoardModelStartNow, BoardModelSuggestions) and ProcessTests.runsMoreCommandsAtOnceThanThereAreCPUs. In a full parallel run, every app test reports 50 to 68 s, so the 60 s limits trip. One run had 49 such failures (seen on #329). A later run at load 10.8 had 76, and each of those tests passed when run alone.
Cause
xcode-select -p on this Mac points at /Applications/Xcode-26.0.0.app, whose Swift is 6.2. The Command Line Tools at /Library/Developer/CommandLineTools have Swift 6.4.2, and CI's macos-26 runner has Swift 6.3.3.
bin/test sets SWT_EXPERIMENTAL_MAXIMUM_PARALLELIZATION_WIDTH=2 so that only two tests run at once. Swift Testing reads that variable from Swift 6.3, and the 6.2 one ignores it, so a local run starts every test at once. Swift Testing's .timeLimit clock starts when the test starts, so it counts the time a @MainActor test waits for the main actor and the time an async test waits for a cooperative-pool thread. With every test started at once, those waits reach a minute.
Done when
A full local bin/test --all run passes without these time-limit failures, and no test checks less than it does now.
- Dominant language
- Swift
- Stars
- 0
- Forks
- 0
- Avg merge
- 6h 15m
- Merged PRs (30d)
- 308
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from haacked/switchboard
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
haacked/switchboard#420 ·
Maintainers usually reply within 1 day
-
priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
haacked/switchboard#403 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
haacked/switchboard#395 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
haacked/switchboard#391 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 66/100
haacked/switchboard#419 ·
Maintainers usually reply within 1 day
All issues in haacked/switchboard
Similar issues
-
area: sidebar enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
ZigaoWang/zigzag#351 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
manaflow-ai/cmux#46584 ·
Maintainers usually reply within 1 day
-
android:core ios:core
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
An exit-test child that can't find its exit test runs the whole suite (can fork-bomb)Possibly taken @grynspan claimed this today. Openai-assisted bug command-line experience exit-tests
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
swiftlang/swift-testing#2054 · 1 comment ·
Maintainers usually reply within 1 day