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
When a build is created by an external contributor, the tests are not split up across the machines due to them not having access to the record keys. We still parallelize the job (up to 7 machines) which means we are using up CI time and increasing the likelihood that the job fails due to flake.
Desired behavior
We should not be parallelizing jobs if the tests cannot be split up, or we should use our own logic for splitting the tests across machines
Current behavior
When a build is created by an external contributor, the tests are not split up across the machines due to them not having access to the record keys. We still parallelize the job (up to 7 machines) which means we are using up CI time and increasing the likelihood that the job fails due to flake.
Desired behavior
We should not be parallelizing jobs if the tests cannot be split up, or we should use our own logic for splitting the tests across machines
Test code to reproduce
Check out a build from an external contributor e.g. https://app.circleci.com/pipelines/github/cypress-io/cypress/37271/workflows/1ad10bf4-86c3-4bff-bad8-044b3952ad4b/jobs/1499238/parallel-runs/5?filterBy=ALL
Cypress Version
9.6.0
Other
No response
The text was updated successfully, but these errors were encountered: