I don't really know why we picked 1 day, but what would be your suggestion?

My guess is that 1 day makes cross timezone reviews more bearable.
Submit patch, send to try bots, wait for review overnight, land in the morning if lgtm'd and trybots pass.

So, we (CQ) don't intend to do anything about this in the short to medium term. Since this "bug report" is WAI given current constraints, I mark this as feature request.

It could and should be revisited if:


Option A: we have more capacity OR some new service can "sense" empty resources and re-trigger CQ dry runs on Cls with old (say >12hr) green tryjobs. In short, re-running morning MTV tryjobs the following night. This might actually even save some capacity during MTV peaks.

Option B: we have much faster cycle times, so we can change the 1 day limit to lower number.

tandrii, is this configurable on the chromium side? I was under the impression that this was an intrinsic part of the CQ.

No, it's not, but there is already a feature request to make it so: see issue 753103.

That said, are you actually disagreeing with what I wrote in #3 above?

Nope, no disagreement there.

Then, I think this bug is to be kept outside of CQ daemon component, as there is nothing that CQ daemon needs to do, at least until Option A above becomes feasible. It is clearly a valid bug, so needs to be kept open.

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Neither options in c#3 are yet true, so throwing back into the queue.