[WPT import] wpt-importer job is red when import succeeded |
||||||||
Issue description
Currently what happens when import succeeds is this:
File ".../webkitpy/w3c/test_importer.py", line 368, in do_auto_update
self.git_cl.run(['set-close'])
webkitpy.common.system.executive.ScriptError: Failed to run "['git', 'cl', 'set-close']" exit_code: 1
output: Last 500 characters of output:
._GetGerritHost(), self.GetIssue(), msg='')
File "/mnt/data/b/depot_tools/gerrit_util.py", line 569, in AbandonChange
return ReadHttpJsonResponse(conn, ignore_404=False)
File "/mnt/data/b/depot_tools/gerrit_util.py", line 377, in ReadHttpJsonResponse
conn, expect_status=expect_status, ignore_404=ignore_404)
File "/mnt/data/b/depot_tools/gerrit_util.py", line 370, in ReadHttpResponse
raise GerritError(response.status, reason)
gerrit_util.GerritError: Conflict: change is merged
In this case, the import script should check whether the change is merged, and if so, exit with status 0.
,
Apr 19 2017
Expecting this to be fixed now, will be able to tell on the next successful wpt import.
,
May 21 2017
Still an issue. Example build: https://build.chromium.org/p/chromium.infra.cron/builders/wpt-importer/builds/103 https://luci-logdog.appspot.com/v/?s=chromium%2Fbb%2Fchromium.infra.cron%2Fwpt-importer%2F103%2F%2B%2Frecipes%2Fsteps%2Fupdate_wpt%2F0%2Fstdout webkitpy.common.system.executive.ScriptError: Failed to run "['git', 'cl', 'set-close']" exit_code: 1 output: Last 500 characters of output: gerrit_util.AbandonChange(self._GetGerritHost(), self.GetIssue(), msg='') File "/mnt/data/b/depot_tools/gerrit_util.py", line 567, in AbandonChange return ReadHttpJsonResponse(conn) File "/mnt/data/b/depot_tools/gerrit_util.py", line 377, in ReadHttpJsonResponse fh = ReadHttpResponse(conn, accept_statuses) File "/mnt/data/b/depot_tools/gerrit_util.py", line 371, in ReadHttpResponse raise GerritError(response.status, reason) gerrit_util.GerritError: Conflict: change is merged step returned non-zero exit code: 1
,
Jun 18 2017
,
Jul 3 2017
,
Jul 3 2017
,
Jul 26 2017
,
Sep 7 2017
Is this still an issue? I don't recall seeing it at least during last month.
,
Sep 7 2017
Let's close for now and reopen if we see it again :-) |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by bugdroid1@chromium.org
, Apr 19 2017