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

Issue 756373 link

Starred by 3 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Sep 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

[WPT import] Import failing to create Gerrit review (unpacker error)

Project Member Reported by foolip@chromium.org, Aug 17 2017

Issue description

https://build.chromium.org/p/chromium.infra.cron/builders/wpt-importer/builds/480

In the attached log, we see `git cl upload -f --gerrit` failing like this:

output: Last 500 characters of output:
       c10a9a60060af6d562c35d924aedc3c3f462e693 -> refs/for/refs/heads/master%wip,m=Initial_upload (n/a (unpacker error))
error: failed to push some refs to 'https://chromium.googlesource.com/a/chromium/src.git'
Error after CL description prompt -- saving description to /home/chrome-bot/.git_cl_description_backup
Failed to create a change. Please examine output above for the reason of the failure.
Hint: run command below to diagnose common Git/Gerrit credential problems:
  git cl creds-check
step returned non-zero exit code: 1

It didn't happen again in https://build.chromium.org/p/chromium.infra.cron/builders/wpt-importer/builds/481, so leaving in P3 unless this failure cause comes up again.
 
wpt-importer-480.txt
12.4 KB View Download
Cc: raphael....@intel.com
Labels: -Pri-3 Pri-2
Status: Available (was: Untriaged)
https://luci-milo.appspot.com/buildbot/chromium.infra.cron/wpt-importer/502 wasn't exactly an "unpack error", but something else was wrong with git:

CQ appears to have passed; trying to commit.
Traceback (most recent call last):
  File "/mnt/data/b/rr/tmp1aClXN/w/src/third_party/WebKit/Tools/Scripts/wpt-import", line 18, in <module>
    host.exit(importer.main())
  File "/mnt/data/b/rr/tmp1aClXN/w/src/third_party/WebKit/Tools/Scripts/webkitpy/w3c/test_importer.py", line 130, in main
    if not self.run_commit_queue_for_cl():
  File "/mnt/data/b/rr/tmp1aClXN/w/src/third_party/WebKit/Tools/Scripts/webkitpy/w3c/test_importer.py", line 182, in run_commit_queue_for_cl
    self.git_cl.run(['upload', '-f', '--send-mail'])  # Turn off WIP mode.
  File "/mnt/data/b/rr/tmp1aClXN/w/src/third_party/WebKit/Tools/Scripts/webkitpy/common/net/git_cl.py", line 51, in run
    return self._host.executive.run_command(command, cwd=self._cwd)
  File "/mnt/data/b/rr/tmp1aClXN/w/src/third_party/WebKit/Tools/Scripts/webkitpy/common/system/executive.py", line 326, in run_command
    (error_handler or self.default_error_handler)(script_error)
  File "/mnt/data/b/rr/tmp1aClXN/w/src/third_party/WebKit/Tools/Scripts/webkitpy/common/system/executive.py", line 234, in default_error_handler
    raise error
webkitpy.common.system.executive.ScriptError: Failed to run "['git', 'cl', 'upload', '-f', '--send-mail']" exit_code: 1
output: Last 500 characters of output:
external/wpt/README.md      | 44 +++++++++++---------
 .../external/wpt/html/dom/original-harness.js      |  3 +-
 3 files changed, 43 insertions(+), 51 deletions(-)
fatal: remote error: Git repository not found
Oh, I've just noticed  issue 757722  about the error above.
I just saw this error on my local machine during "git cl upload".

Opened an internal bug to the Gerrit/Git team: https://b.corp.google.com/issues/64979510

Don't worry if you can't access. I will post follow-ups here.
Update: the team has located the logs of the corresponding server-side exception and is investigating.
In case it helps, it happened again a few hours ago: https://luci-milo.appspot.com/buildbot/chromium.infra.cron/wpt-importer/581
Yup, reported. Thanks, Raphael.

(And also thanks to Quinten, we now have timestamps in the log, which helps a lot in case like this!)
Status: WontFix (was: Available)
Update from the internal bug:

Although the root cause is still unclear, the team has rolled out a fix for another issue that might reduce the frequency of the faulty code path by several magnitudes. In practice, we might no longer see this error again.

Closing the bug as WONTFIX until we see another case.

Sign in to add a comment