Skip to content

test: Remove Windows nextest thread cap #12999

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
anthonyshew merged 1 commit into from
Jun 1, 2026
Merged

test: Remove Windows nextest thread cap #12999

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 0 additions & 13 deletions .config/nextest.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,19 +4,6 @@
[profile.default]
failure-output = "immediate-final"

[test-groups]
windows-turbo-subprocess-heavy = { max-threads = 2 }

[[profile.default.overrides]]
# Windows runners can fail subprocess-heavy tests under high nextest fanout with
# DLL initialization error 0xc0000142. Keep full coverage, but cap the
# integration files that create many git repos, run package managers, or spawn
# child `turbo` processes so they do not stampede process startup while the rest
# of the package still runs at normal concurrency.
filter = 'package(turbo) and (binary(run_summary) or binary(workspace_config_deps_test) or binary(lockfile_aware_caching_test) or binary(one_script_error_test) or binary(inference_test))'
platform = 'cfg(windows)'
test-group = 'windows-turbo-subprocess-heavy'

[[profile.default.overrides]]
# These tests run package installs from the network during setup, which can
# take 20-60s+ on cold CI runners. Give them extra time instead of retries.
Expand Down
Loading