In the past, such CQ spam like that has often led to a sub-optimal experience for every other developer, since the CQ gets bogged down under the spike in load. So until smart per-user rate limiting is implemented in the CQ (
crbug.com/1335519), we'd appreciate not dry-running such CLs at the same time. Other options that infra would much prefer:
- Wait for off-hours to dry-run everything, ie: not during AMER's working day. Note that folks in EMEA's or APAC's working day might still be affected depending on when things are triggered.
- Don't dry-run every CL at the same time, ie: do it gradually in a sequence.
- Don't dry-run at all; simply set the auto-submit label and let reviewers gradually CQ+2 the CLs as they're reviewed.
LMK if that doesn't make sense. And thanks for reaching out ahead of time.