Add tt mlir override #866
Merged
Add tt mlir override #866
Conversation
This file contains 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
vmilosevic
requested review from
kmabeeTT,
tt-mpantic,
pilkicTT and
nvukobratTT
pilkicTT
approved these changes
Dec 10, 2024
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.
The tt-forge-fe workflows accept a tt-mlir SHA override input, ensuring the specified SHA is used for building Docker images, compiling, and testing, instead of the committed version of tt-mlir.
This will be used as part of integration testing to ensure that integrating a newer version of tt-metal doesn't break downstream projects.
Users can manually trigger the workflow to run with a specific version of tt-mlir, and in CI tt-mlir will trigger this workflow to run with the uplift branch.
Relates to #214