Gerrit flake: CQ to merges to Git but doesn't update Gerrit status on submission
Reported by
vpalatin@chromium.org,
Feb 12 2018
|
|||||
Issue descriptionI have tried to submit 2 EC CLs (public and private) with a CQ-DEPEND on each other: (public) https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/880955 (private) https://chrome-internal-review.googlesource.com/c/chromeos/platform/ec-private/+/552559 Gerrit still thinks both are not submitted while there are both in their respective git repository: https://chromium.googlesource.com/chromiumos/platform/ec/+/01cee655ab1eb2cf5271a1d578074a3252430ea0 https://chrome-internal.googlesource.com/chromeos/platform/ec-private/+/c6ae2cfb51d243d411270ff51d839db2c1996321 (I'm going to abandon them) The public CL failed with: The Commit Queue failed to apply your change in https://luci-milo.appspot.com/buildbot/chromeos/master-paladin/17709 . CL:880955 had no changes after rebasing to ToT. The private CL failed with: The Commit Queue failed to apply your change in https://luci-milo.appspot.com/buildbot/chromeos/master-paladin/17709 . CL:*552559 depends on CL:880955, which had no changes after rebasing to ToT. Then the CL exonerator came : "This CL has been marked innocent in the CL annotator; re-marking as CQ+1." CL failed again ...
,
May 15 2018
Maybe this is https://bugs.chromium.org/p/chromium/issues/detail?id=792781 ?
,
May 29 2018
This isn't the issue I linked in Comment 2. Instead, this is Gerrit flakes recurring. Going to leave this open as the new bug for any such reports (though I don't think we've had any more since February).
,
Jun 5 2018
,
Jun 5 2018
Most recent dupe is from January so I think we still aren't seeing a pattern of new reports since February.
,
Jun 6 2018
Issue 849981 has been merged into this issue.
,
Jun 6 2018
It happened again last night. Escalating to Gerrit team (yet again).
,
Jun 6 2018
,
Jun 13 2018
Per the Gerrit team, we can use the Fix Change REST API to try to automatically repair changes that we detect failed in this way. This is a workaround while Gerrit continues to investigate fixing the root cause on b/63796025 .
,
Jun 13 2018
,
Aug 10
We've been offered an API to clean up an entire git repository on a periodic basis and also permission to call this daily. Our current action item is to call this daily. This API was landed here: https://buganizer.corp.google.com/issues/63796025 .
,
Jan 3
,
Jan 4
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by ayatane@chromium.org
, May 15 2018