Go version
N/A
Output of go env in your module/workspace:
What did you do?
Review contributed changes that need additional testing (such as running on a longtest builder or a particular architecture) before they can be safely merged.
What did you see happen?
There is a “CHOOSE TRYJOBS” button, but IIRC it doesn't affect auto-submit, and it definitely doesn't stick when a new patchset is uploaded.
It is possible to leave a comment requesting that the author add a Cq-Include-Trybots: line to the commit message, but for small externally-contributed changes that can add an extra round-trip.
What did you expect to see?
Some way that I (as a reviewer) can mark the CL as ok to auto-submit provided that a specific set of additional LUCI builders succeeds.
Go version
N/A
Output of
go envin your module/workspace:What did you do?
Review contributed changes that need additional testing (such as running on a
longtestbuilder or a particular architecture) before they can be safely merged.What did you see happen?
There is a “CHOOSE TRYJOBS” button, but IIRC it doesn't affect auto-submit, and it definitely doesn't stick when a new patchset is uploaded.
It is possible to leave a comment requesting that the author add a
Cq-Include-Trybots:line to the commit message, but for small externally-contributed changes that can add an extra round-trip.What did you expect to see?
Some way that I (as a reviewer) can mark the CL as ok to auto-submit provided that a specific set of additional LUCI builders succeeds.