-
Notifications
You must be signed in to change notification settings - Fork 116
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
#0: Allow Users to provide extra tag for T3K choose your own pipeline #14873
Conversation
@@ -23,7 +28,7 @@ jobs: | |||
ARCH_NAME: ${{ matrix.test-group.arch }} | |||
LOGURU_LEVEL: INFO | |||
LD_LIBRARY_PATH: ${{ github.workspace }}/build/lib | |||
runs-on: ["arch-wormhole_b0", "config-t3000", "in-service", "pipeline-perf"] | |||
runs-on: ["arch-wormhole_b0", "config-t3000", "in-service", "pipeline-functional", ${{ inputs.extra-tag }}] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
shoud set extra-tag as default to in-service.
That way you can use this workflow to triage OOS units as well
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oh good catch!
Looks like it is working now. Sorry I had to iteratively hack. https://github.com/tenstorrent/tt-metal/actions/runs/11733788167 |
Ticket
NA
Problem description
Choose your own pipeline workflow dispatch does not allow users to target specific runners.
What's changed
Allow an optional extra tag to be supplied during workflow dispatch.
Currently only applied to T3K workflows.
Checklist