Separate diffuse runner used to build containers#273
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThree jobs in ChangesDocker Workflow Runner Update
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related PRs
Suggested reviewers
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
Docker publish jobs in
diff-use/sampleworkswere stuck waiting for a runner.The issue started in commit
9f17fc4(Run docker workflow on Astera builder), which changed the Docker workflow fromubuntu-latesttoastera-sh-builder.astera-sh-builderexisted, but it was registered to theAstera-orgGitHub org. Thesampleworksrepo is underdiff-use, so GitHub could not match the job to that runner.Fix
Add a new diff-use CPU runner scale set named
diffuse-sh-builderin the existingarc-runnersnamespace.Update the
sampleworksDocker workflow to use: