roachprod: fix update & get latest
TBD
Epic: none Fixes: #120750 Epic: CRDB-8035
Release note: None
Emulated "staleness" check which emits this warning in roachprod,
roachprod
WARN: roachprod binary is >= 2 weeks old (569h7m14.325s); latest sha: "abcdef"
WARN: Consider updating the binary: `roachprod update`
Separately, lots of lint failures. Consider using lintonbuild so you don't have to go back-and-forth with CI :)
Consider using
lintonbuildso you don't have to go back-and-forth with CI :)
I did for a while actually, until it got too slow :) Especially, when you're doing multiple builds (on different branches) back-to-back.
Everything is now green and ready to go. PTAL!
TFTR!
bors r=rickystewart
Build succeeded:
Encountered an error creating backports. Some common things that can go wrong:
- The backport branch might have already existed.
- There was a merge conflict.
- The backport branch contained merge commits.
You might need to create your backport manually using the backport tool.
error creating merge commit from 780b2982e88d9cdc3de98390285a1ec480db58bf to blathers/backport-release-23.2-124592: POST https://api.github.com/repos/cockroachdb/cockroach/merges: 409 Merge conflict []
you may need to manually resolve merge conflicts with the backport tool.
Backport to branch 23.2.x failed. See errors above.
error creating merge commit from 780b2982e88d9cdc3de98390285a1ec480db58bf to blathers/backport-release-24.1-124592: POST https://api.github.com/repos/cockroachdb/cockroach/merges: 409 Merge conflict []
you may need to manually resolve merge conflicts with the backport tool.
Backport to branch 24.1.x failed. See errors above.
:owl: Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf.
We can close #120750 now, yes? Or was there a reason this PR was only marked as Informs?
@renatolabs Check out the discussion here.