You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems to me that the expected behavior should be to use the runner's parallel option when --parallel flag is provided without a value or not provided at all instead of forcing it to 3.
It means the above PR should be reverted but it would bring back the old behavior described in #13782
I could open a PR to fix this but I'm not sure what the expected solution is.
Looks like #13782 about when is not set default should be 1, but works when change it to another value. Looks like 1 (sequentional running) is very slow when you processing large amount of libs, and it's bad as defaults. More over 3 is really bad too. Maybe use 6 as default (mostly modern CPU provide 6+ cores) or maybe when create project check available cores and provide better values or check when running and tell if user can use more cores for it.
But my bug about I can't set parallel from nx.json
Current Behavior
nx run-many --exclude=some-libs --target=lint --quiet run only 3 parallel default jobs
Expected Behavior
run parallel jobs based on information from nx.json tasksRunnerOptions (I have 6)
workaround: add
--parallel=6
manually to commandGitHub Repo
No response
Steps to Reproduce
Nx Report
Failure Logs
No response
Additional Information
only 3 jobs in parallel
That is regression previous versions works good
previous bug #10756
The text was updated successfully, but these errors were encountered: