New issue
Advanced search Search tips

Issue 804394 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 811188
Owner:
Closed: Jun 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug-Regression



Sign in to add a comment

CL is committed, but gerrit complained about uprev failure

Project Member Reported by ahass...@chromium.org, Jan 22 2018

Issue description

I have a problem with a CL, (crrev.com/c/834876). It seems the CQ picked it up "only once" and failed to commit it because of uprev failure, but at the same time it has been committed and I can see the commit log in the tree. It looks different than root cause of b/68258327. Can someone take a look?


 
Components: -Infra>Codereview>Gerrit Infra>Client>ChromeOS

Comment 2 by jkop@chromium.org, Jan 31 2018

Cc: -akes...@chromium.org -jkop@chromium.org shuqianz@chromium.org
Labels: -Pri-1 Pri-2
From the link you provided, it was committed without error. Doesn't seem like a serious issue.
Sorry, it was a wrong CL, This is the correct CL: crrev.com/c/825956

If you look at the tree is merge is commited (https://chromium.git.corp.google.com/chromiumos/overlays/board-overlays/+/9e4602d151c4fb9251f9d624f4b876d52a921038), but gerrit reports that CQ failed to apply it.
If you don't think this is serious anymore I can close this and abandon the change.

Comment 5 by xixuan@chromium.org, Mar 14 2018

Cc: -shuqianz@chromium.org
Owner: nxia@chromium.org
Status: Assigned (was: Untriaged)
Based on the tree's history, this CL is submitted at Sat Jan 20 04:35:44 2018, which should be a UTC time, and it's PST Jan 19, 20:35:44. At that time the CQ (https://luci-milo.appspot.com/buildbot/chromeos/master-paladin/17529) hasn't started.

Assign to @nxia, any other service in our system to commit a CL?

Comment 6 by nxia@chromium.org, May 31 2018

Components: -Infra>Client>ChromeOS Infra>Client>ChromeOS>CI
Owner: ----
Status: Available (was: Assigned)
Owner: athilenius@chromium.org
Status: Untriaged (was: Available)
Alec, please look at the logs for the CQ run that submitted crrev.com/c/825956 and see if you can come up with a timeline of events related to this. That's good enough for a triage right now.
16:10:51 - Commit_queue +1
18:43:08 - CQ Picked up change
20:54:45 - Source synced
20:54:55 - CQSync - Queried changes: ... CL:825956 ...
20:54:55 - CQSync - Checking for change ahassani:825956:24578e4c
20:57:39 - CQSync - Attempting to create transaction for ahassani:825956:24578e4c
20:57:40 - CQSync - Transaction for ahassani:825956:24578e4c is ahassani:825956:24578e4c.
... Many merges
20:57:58 - CQSync - Attempting to apply change ahassani:825956:24578e4c:"moblab: Removed dependency to delta_generator"
20:57:58 - CQSync - Rewinding transaction: failed changes: ahassani:825956:24578e4c:"moblab: Removed dependency to delta_generator".
20:57:58 - CQSync - EbuildConflict: CL:825956 deletes an ebuild that is not present anymore. For this reason, we refuse to submit your change.
20:57:58 - CQSync - Failed applying transaction for ahassani:825956:24578e4c:"moblab: Removed dependency to delta_generator": CL:825956 deletes an ebuild that is not present anymore. For this reason, we refuse to submit your change.
20:58:05 - CQSync - Change ahassani:825956:24578e4c:"moblab: Removed dependency to delta_generator" did not apply cleanly.
21:58:06 - Verified -1 by Commit Bot
Mergedinto: 811188
Status: Duplicate (was: Untriaged)
20:54:55 is after the CL submitted time. Did the CQ run before it submit it? Yep:

https://luci-milo.appspot.com/buildbot/chromeos/master-paladin/17528:

20:36:27: INFO: RunCommand: git push https://chromium-review.googlesource.com/chromiumos/overlays/board-overlays HEAD:master in /b/c/cbuild/repository/src/overlays
20:37:01: WARNING: Change 825956 was pushed without errors, but gerrit is reporting it with status "NEW" (expected "MERGED").
20:37:01: ERROR: Gerrit likely was unable to merge change 825956.

This is yet another Gerrit flake.

Sign in to add a comment