-
Notifications
You must be signed in to change notification settings - Fork 3.6k
Support special test parametrizations #10462
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
Conversation
for more information, see https://pre-commit.ci
This reverts commit b01f26d.
|
Build Error! No Linked Issue found. Please link an issue or mention it in the body using #<issue_id> |
2 similar comments
|
Build Error! No Linked Issue found. Please link an issue or mention it in the body using #<issue_id> |
|
Build Error! No Linked Issue found. Please link an issue or mention it in the body using #<issue_id> |
|
Hey @carmocca, This is really dope! However, do we believe it is worth adding an extra 2 min to the CI to isolate the parametrization? I believe the overhead is coming from DDP being instantiated and processes behind created for each combination. IMO, even if this is awesome, I think we shouldn't merge it as the overhead will only grow in the future. |
|
That's totally sensible. This PR was exploratory. I have one more idea to try which would be collecting only once, instead of as many times as we have special tests. That might just have a few seconds of extra runtime. |
What does this PR do?
Kudos to @SeanNaren for the idea.
This adds ~2 minutes to the special test runtime. This comes from the overhead of running pytest one added time for each test with
--collect-onlyI have rolled back some of the parameterizations. If you know of any others, feel free to push a change to this PR.
The current list of tests is:
Does your PR introduce any breaking changes? If yes, please list them.
None
Before submitting
PR review