-
Notifications
You must be signed in to change notification settings - Fork 80
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
Tmp/mwang/tunneler ci2 #15225
base: main
Are you sure you want to change the base?
Tmp/mwang/tunneler ci2 #15225
Conversation
Are these deterministically passing now? If you would like to do extra testing, I recommend using the custom test dispatch workflow to run your test in a loop on our VM infrastructure |
Thanks for offering. We move this test from post-commit to micro-benchmark pipeline to make it run on BM machines instead of VMs as it is to check performance. |
You can still custom dispatch onto BMs as well using the labels
And this should target our N300 perf BM. I would recommend such to sniff out stability / non-determinant failure issues. By the way, how long should these tests take? |
d5e6ede
to
91d3c31
Compare
Thanks for letting me know! The codes have been modified to get rid of the prior failure (which is related to how fast a node can be set up on the machine). And it has been tested with for loops on both local and CI machines. The tests only take a few minutes to run. |
How was running it? Did it look ok / stable? |
Yes, it is stable https://github.com/tenstorrent/tt-metal/actions/runs/12044418841 |
Beautiful, 10x |
91d9c01
to
35ec7a1
Compare
Problem description
Add tunneler tests to micro benchmark test so that they can be run on BM machines.
Checklist