Repository navigation
ci: run go and buf jobs on github-hosted runners - #363
Conversation
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository: akash-network/chain-sdk/.coderabbit.yaml Review profile: CHILL Plan: Essentials Run ID: 📒 Files selected for processing (3)
Included review availability: This review used your included allowance. 0 included reviews remain after this review. Your included PR review attempts over the past 7 days set your current allowance at 1 review per hour. WalkthroughCI workflow jobs changed from self-hosted runners to ChangesCI Workflow Settings
Priority: ⬇️ Low Estimated code review effort: 2 (Simple) | ~10 minutes Change: Other Suggested reviewers: Merge Risk: ⚪ Minimal · up to The Go and Buf-related CI jobs now use GitHub-hosted Ubuntu runners. The reviewed workflows set up their required tools, and no concrete incompatibility was found; the change appears ready to merge. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
A rabbit checks the runners in a row Comment |
9e151b6 to
f6801cb
Compare
These jobs fail intermittently on the self-hosted runners for reasons outside the code, mostly rejected buf.build downloads and interrupted builds. - run test, coverage, go lint, proto lint and the breakage check on ubuntu-latest - point setup-go at go/go.sum (go/sdl/go.sum for sdl-parity) so its cache restores
f6801cb to
8153368
Compare
📝 Description
Moves the Go and buf jobs to GitHub-hosted runners, where they stop failing for reasons outside the code. Also points setup-go at
go/go.sumso its module cache restores.🔧 Purpose of the Change
📌 Related Issues
✅ Checklist
📎 Notes for Reviewers
ts,labeler,releaseandrelease-tsstay on the self-hosted runners.