[REFACTOR] Phase out relay python components #17656
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
cpptest should only run on cpu and test most basic stuffs Use python test for broader coverage. NOTE for future, we can potential restructure additional tests that links libtvm but donot rebuild libtvm if strictly needing them.
Hzfengsy
approved these changes
Feb 15, 2025
yongwww
approved these changes
Feb 15, 2025
ShiboXing
pushed a commit
to ShiboXing/tvm
that referenced
this pull request
Aug 10, 2025
This PR starts the step 0 to phase out relay from the current development main branch. This PR focuses on the python components of relay, autotvm, auto_scheduler. To make the change manageable, we will also do followup steps on te.Schedule and c++ components in followup PRs. To continue support community members who depends on legacy flows, the [v0.19.0](https://github.com/apache/tvm/tree/v0.19.0) branch will continue contain these components. As noted in [discussion on phasing out legacy components](https://discuss.tvm.apache.org/t/phasing-out-legacy-components/17703/30), this would help us to do two purposes: - By removing outdated or redundant elements, we can significantly reduce complexity and improve maintainability. - Unify our focus: Concentrating our efforts on the new unity flow will allow for more efficient development and innovation. It is also a good opportunity for us to revisit and reduce CI time. The past relay legacy flow contains a lot of end to end tests that requires hardware resources to run and causing long CI time. Moving onwards, we can focus more on unit-tests that focuses on structural equality and runs within seconds, while be mindful about tests that requires hardware resources (by restricting them to specific folders and CI nightly in some cases). --- 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 starts the step 0 to phase out relay from the current development main branch. This PR focuses on the python components of relay, autotvm, auto_scheduler. To make the change manageable, we will also do followup steps on te.Schedule and c++ components in followup PRs.
To continue support community members who depends on legacy flows, the v0.19.0 branch will continue contain these components.
As noted in discussion on phasing out legacy components, this would help us to do two purposes:
It is also a good opportunity for us to revisit and reduce CI time. The past relay legacy flow contains a lot of end to end tests that requires hardware resources to run and causing long CI time. Moving onwards, we can focus more on unit-tests that focuses on structural equality and runs within seconds, while be mindeful about tests that requires hardware resources (by restricting them to specific folders and CI nightly in some cases).