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

Issue 663543 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Jan 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug

Blocked on:
issue 662214



Sign in to add a comment

Repo init error shouldn't exit PreCQLauncher

Project Member Reported by nxia@chromium.org, Nov 8 2016

Issue description

https://uberchromegw.corp.google.com/i/chromeos/builders/pre-cq-launcher/builds/8039/steps/PreCQLauncher/logs/stdio

23:44:17: INFO: Running cidb query on pid 23534, repr(query) starts with <sqlalchemy.sql.expression.Insert object at 0x7f881126e1d0>
23:44:19: INFO: Waiting for waiting for tree to open (213 minutes left)...
23:44:49: INFO: RunCommand: repo manifest in /b/cbuild/internal_master
23:44:49: INFO: RunCommand: repo init --repo-url https://chromium.googlesource.com/external/repo --manifest-url https://chrome-internal-review.googlesource.com/chromeos/manifest-internal --manifest-name official.xml --manifest-branch master in /b/cbuild/internal_master
fatal: remote error: internal server error
fatal: remote error: internal server error
fatal: cannot obtain manifest https://chrome-internal-review.googlesource.com/chromeos/manifest-internal
23:46:44: ERROR: return code: 1; command: repo init --repo-url https://chromium.googlesource.com/external/repo --manifest-url https://chrome-internal-review.googlesource.com/chromeos/manifest-internal --manifest-name official.xml --manifest-branch master
cwd=/b/cbuild/internal_master

@@@STEP_FAILURE@@@
23:46:44: ERROR: <class 'chromite.cbuildbot.repository.SrcCheckOutException'>: return code: 1; command: repo init --repo-url https://chromium.googlesource.com/external/repo --manifest-url https://chrome-internal-review.googlesource.com/chromeos/manifest-internal --manifest-name official.xml --manifest-branch master
cwd=/b/cbuild/internal_master
Traceback (most recent call last):
  File "/b/cbuild/internal_master/chromite/lib/failures_lib.py", line 172, in wrapped_functor
    return functor(*args, **kwargs)
  File "/b/cbuild/internal_master/chromite/cbuildbot/stages/sync_stages.py", line 1946, in PerformStage
    builder_run=self._run)
  File "/b/cbuild/internal_master/chromite/cbuildbot/validation_pool.py", line 1441, in AcquirePool
    repo.Sync()
  File "/b/cbuild/internal_master/chromite/cbuildbot/repository.py", line 517, in Sync
    raise SrcCheckOutException(err_msg)
SrcCheckOutException: return code: 1; command: repo init --repo-url https://chromium.googlesource.com/external/repo --manifest-url https://chrome-internal-review.googlesource.com/chromeos/manifest-internal --manifest-name official.xml --manifest-branch master
cwd=/b/cbuild/internal_master

23:46:44: INFO: Running cidb query on pid 23534, repr(query) starts with <sqlalchemy.sql.expression.Update object at 0x7f8810a02190>
23:46:48: INFO: cidb query succeeded after 1 retries

 

Comment 1 by nxia@chromium.org, Nov 8 2016

Owner: nxia@chromium.org
Project Member

Comment 2 by bugdroid1@chromium.org, Nov 10 2016

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/chromite/+/7e1aaf532e3745f2c3b09e42c48347e27b31426e

commit 7e1aaf532e3745f2c3b09e42c48347e27b31426e
Author: Ningning Xia <nxia@chromium.org>
Date: Tue Nov 08 23:11:38 2016

Log repo sync error and output.

We saw repo_init errors lately. Eable the repo error and output in the
error log.

BUG= chromium:663543 
TEST=run_tests

Change-Id: Id2ee4f06adb01801b90f827994c701d68767468c
Reviewed-on: https://chromium-review.googlesource.com/408667
Commit-Ready: Ningning Xia <nxia@chromium.org>
Tested-by: Ningning Xia <nxia@chromium.org>
Reviewed-by: Don Garrett <dgarrett@chromium.org>

[modify] https://crrev.com/7e1aaf532e3745f2c3b09e42c48347e27b31426e/cbuildbot/repository.py

Comment 3 by nxia@chromium.org, Jan 31 2017

Blockedon: 662214
 crbug.com/662214  fix repo init by retry.

If repo init fails after 2 retries, the pre-cq-lancher should just fail. 

Comment 4 by nxia@chromium.org, Jan 31 2017

Status: Fixed (was: Untriaged)

Sign in to add a comment