-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
[Tests] help us speed up the fast pipeline tests #7677
Comments
Hey @sayakpaul I'd like to take a shot at this. :) |
Feel free to target one pipeline test and send over a PR :) |
Hi @sayakpaul, I would like to contribute! |
Feel free to target one pipeline test and send over a PR :) |
hey @sayakpaul i am interested to work on this! |
This was referenced Apr 28, 2024
@AbhinavJangra29 feel free to open a PR and tag me. |
This was referenced May 1, 2024
This was referenced May 6, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, the pipeline tests (located under
tests/pipelines
) take a bit of time to run. We recently performed some optimizations to speed them up but, we can do better.This is especially desirable because it greatly improves the contribution experience not just for the community but also for us, maintainers. So, we welcome contributions from the community to improve the pipeline test suite that runs during PRs 🤗
What's the problem?
Many pipeline tests (here's an example) use model-level components (such as the UNet) whose size can be made much smaller for testing purposes. The bigger their size, the longer it's going to take to execute them (obviously).
How can you help?
Reduce the sizes of the model-level components and thereby making the pipeline tests run faster.
How should you submit a PR?
get_dummy_components()
function (example) for a given pipeline test script.Things to note
get_dummy_components()
function. If further changes are required, please explain the motivation behind them in your PR description.@yiyixuxu @DN6 for awareness and visibility.
The text was updated successfully, but these errors were encountered: