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

Issue 710981 link

Starred by 8 users

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Jun 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: ----
Type: ----



Sign in to add a comment

Upload fails randomly

Project Member Reported by roc...@chromium.org, Apr 12 2017

Issue description

Output of git cl upload occasionally looks like this:

------

To https://chromium.googlesource.com/chromium/src.git
 ! [remote rejected]           43e79c9c16e038b3a717d2fe2e39e349b420ee72 -> refs/for/refs/heads/master%m=minor_cleanup__cancel_watcher_on_failed_notification,notify=NONE (error in Gerrit backend)
error: failed to push some refs to 'https://chromium.googlesource.com/chromium/src.git'

Error after CL description prompt -- saving description to /usr/local/google/home/rockot/.git_cl_description_backup

Failed to create a change. Please examine output above for the reason of the failure.
Hint: run command below to diangose common Git/Gerrit credential problems:
  git cl creds-check

------

creds-check never turns up anything interesting ("No problems detected in your .gitcookies", plus a list of valid hosts and users)

And a subsequent run of git cl upload usually succeeds.
 
Owner: aga...@chromium.org
Status: Assigned (was: Unconfirmed)
from "(error in Gerrit backend)" looks to be a Gerrit issue.

Comment 2 by aga...@chromium.org, Apr 13 2017

I've inquired on the gerrit team mailing list.

Comment 3 by aga...@chromium.org, Apr 17 2017

Cc: aga...@chromium.org
Owner: ----
Status: ExternalDependency (was: Assigned)
How often does this come up? Just once?

Do you have a timestamp so they can look in their logs?

Comment 4 by roc...@chromium.org, Apr 20 2017

I'll try to remember to update this bug next time it happens. I was hitting
it pretty frequently two weeks ago.

Comment 5 by roc...@chromium.org, Apr 24 2017

This just happened again at ~ 16:13 PDT.

Trying to upload a new patchset to
https://chromium-review.googlesource.com/c/477393/.

Output follows:


To https://chromium.googlesource.com/chromium/src.git
 ! [remote rejected]           7a67ae0bd081e6556c6e018e76a81d4a55954c01 ->
refs/for/refs/heads/master%m=,notify=NONE (error in Gerrit backend)
error: failed to push some refs to '
https://chromium.googlesource.com/chromium/src.git'

Error after CL description prompt -- saving description to
/usr/local/google/home/rockot/.git_cl_description_backup

Failed to create a change. Please examine output above for the reason of
the failure.
Hint: run command below to diangose common Git/Gerrit credential problems:
  git cl creds-check

Comment 6 by roc...@chromium.org, Apr 24 2017

Failed twice in a row. Each time it took about 2 full minutes of nothing
happening before actually failing.

Upon rerunning git cl upload a third time without taking any other other
actions, the upload succeeded.

Comment 7 by roc...@chromium.org, Apr 25 2017

Happened again today on the same CL, maybe about 15 minutes ago.
 Issue 715878  has been merged into this issue.
 Issue 719722  has been merged into this issue.
Cc: logan@google.com dborowitz@google.com
Owner: sop@google.com
Status: Assigned (was: ExternalDependency)
Hey gerrit folks, similar to  issue 710722 , we have a bunch of folks who have complained about straight up flaky failures upon push. They get a 500 (error in Gerrit backend) for no particular reason.

Can we get an investigation into long push times and see if we can figure out what's going on?
s/long push times/flaky push failures/
File a bug internally with specific projects and timestamps.
 Issue 726523  has been merged into this issue.
We have a recent reproduction with timestamps, so I just filed http://b/62106271
\o/ thanks!
Status: ExternalDependency (was: Assigned)
 Issue 728798  has been merged into this issue.
Cc: scottmg@chromium.org
 Issue 733842  has been merged into this issue.
Status: Fixed (was: ExternalDependency)
The internal tracking bug has been fixed. We can dig into this again if we continue to see reports.

Sign in to add a comment