Workflow to track client integration build #318
Merged
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
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.
Issue
No tracking issue, but a follow up issue will be #321
tt-lens is a private repo, so it is not trivial to add a build job such as this one.
Description
Adding a job, which won't be mandatory, which tries to build newest tt-metal with the current umd (a branch from this PR if triggered on PR, or main if on main).
The idea is that to see asap if something is going to break tt-metal build, which seems to be happening often in the past period.
List of the changes
Testing
CI on this branch passed.
API Changes
There are no API changes in this PR.