New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 708786 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Apr 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

CQ incorrectly over-reports number of submitted CLs when "tree is closed"

Project Member Reported by pprabhu@chromium.org, Apr 5 2017

Issue description

If the tree is closed before a successful CQ run has submitted CLs, it waits till the tree opens to submit those (already verified) CLs.

In case the tree remains closed for too long, CQ master aborts.

But, it reports as all those CLs having been submitted.

eg: https://chromiumos-build-annotator.googleplex.com/build_annotations/edit_annotations/master-paladin/1430645/?num_builds=10

claims 27 CLs were submitted.
But it didn't really submit them.
e.g.: https://chromium-review.googlesource.com/c/462164/ was submitted the next day
(so they _are_ retried).

We should fix the reporting.
 

Comment 2 by nxia@chromium.org, Apr 7 2017

Status: WontFix (was: Available)

master-paladin/1430844/ actually claimed 0 CLs were submitted.

https://chromiumos-build-annotator.googleplex.com/build_annotations/edit_annotations/master-paladin/1430844/

paladin/1430645/ claimed 27 CLs were submitted, which is also right. 

https://chromiumos-build-annotator.googleplex.com/build_annotations/edit_annotations/master-paladin/1430645/


i think it's a won't fix?

Sign in to add a comment