[CI] rejig the frequency of test suites in CI #12518
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
Author
|
@stevhliu, the doc-related error on the CI seems familiar to you? |
Contributor
|
This issue has been automatically marked as stale because it has not had recent activity. If you think this still needs to be addressed please comment on this thread. Please note that issues that do not follow the contributing guidelines are likely to be ignored. |
Member
|
hi, the doc error should be fixed in #12522 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
As the title mentions. Some changes:
push_tests_fasts.ymlSkyReelsV2Transformer3DTestsas that's not how it's supposed to be tested.is_torch_compile.run_torch_compile_testsfrom thepush_testsand ensures that the compilation-related tests only run nightly.pytest -m "is_torch_compile" tests/ --collect-only -q > collected_tests.txtgives me exactly the kinds of tests we wanna run for compilation. I have verified it.