[REFACTOR] Phase out te.schedule python components #17658
Merged
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
spectrometerHBH
approved these changes
Feb 16, 2025
yongwww
approved these changes
Feb 16, 2025
This PR phases out te.schedule python components. te.compute is kept around for future usages. tir.Schedule is a more modern version of the scheduling that we can use onwards. Doing so also helps us to cleanup the testcases that relies on explicit full build and execution. As we move future unit testcases towards structural equality based unit tests.
The main rationale is that we should only have very few target dependent UT in tests/python/codegen and possible a new category in future for op-level integration if needed.
ShiboXing
pushed a commit
to ShiboXing/tvm
that referenced
this pull request
Aug 10, 2025
* [REFACTOR] Phase out te.schedule python components This PR phases out te.schedule python components. te.compute is kept around for future usages. tir.Schedule is a more modern version of the scheduling that we can use onwards. Doing so also helps us to cleanup the testcases that relies on explicit full build and execution. As we move future unit testcases towards structural equality based unit tests. * Simplify CI to focus on UT The main rationale is that we should only have very few target dependent UT in tests/python/codegen and possible a new category in future for op-level integration if needed. * Re-enable wasm * fix lint * remove hybrid,sparse autodoc and remove tests --------- Co-authored-by: Siyuan Feng <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
This PR phases out te.schedule python components.
te.compute is kept around for future usages.
tir.Schedule is a more modern version of the scheduling that we can use onwards.
Doing so also helps us to cleanup the testcases that relies on
explicit full build and execution. As we move future unit testcases
towards structural equality based unit tests.