-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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.
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
feat(test): add --parallel
flag, soft deprecate --jobs
#15259
Conversation
Defaults to number of available CPUs when used with | ||
--jobs flag and no value is provided. | ||
Defaults to 1 when --jobs flag is not used. | ||
DENO_JOBS Number of parallel workers used for the --parallel |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I thought about renaming this, but DENO_MAX_PARALLELISM
is long. Additionally, cargo uses CARGO_JOBS
for this env variable, so I think it makes sense? We can also reuse this env var for deno fmt and lint in the future. Thoughts?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sounds good to me 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Soft deprecation of
--jobs
flag. There are some problems with it as outlined in #14533 (comment)In summary:
--jobs
is not easy to use on its own as a binary option because it doesn't require an equals sign after it. So if you do something likedeno test --jobs test_file.ts
it will fail parsing "test_file.ts" to a number."parallel": true
to the config file in the future.Supersedes #15225
Closes #14533
Co-authored-by: @mrkldshv