github: workflows: Move to KMD 2.7.0#1004
github: workflows: Move to KMD 2.7.0#1004jgrowdenTT wants to merge 2 commits intotenstorrent:mainfrom
Conversation
|
I think we need some variation of #1008 with this, but I'm still trying to figure out how to build KMD in the metal container. The version of Ubuntu they use may simply be too old |
Probably wise to wait for that, no issue. Still in comms with metal team about a potential fix for 0xBAADFOOD, so we have time. If your PR takes awhile, it's probably okay to throw this over the wall without it though... Eventually our runners will settle on 2.7.0 as all the PRs on 2.5.0 go away, and in the meantime we might see red if a runner was stuck on old KMD and starrted running new container... Not ideal, but not the first time we've been seeing red. |
|
@jgrowdenTT Just to confirm, the issues you saw with KMD 2.7.0 before were related to metal bugs that have been fixed, and not any issues with KMD 2.7.0 itself right? |
|
@alexapostolu Yes, what was turning metal red was a bug in metal that was addressed. |
Move to use KMD 2.7.0 with the most up to date metal container Signed-off-by: James Growden <jgrowden@tenstorrent.com>
The current actions makes a very long string with the metal container, the board, the board tag, etc. We just need to display the board for each of these. Signed-off-by: James Growden <jgrowden@tenstorrent.com>
Move to use KMD 2.7.0 with the most up to date metal container.
This passed metal in this CI job, and it also passes stress locally on my p150a.