New issue
Advanced search Search tips

Issue 924018 link

Starred by 1 user

Issue metadata

Status: Closed
Owner:
Closed: Today
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

wizpig-paladin failed at CommitQueueSync stage

Project Member Reported by paulhsia@chromium.org, Yesterday (24 hours ago)

Issue description

After restarting CQ,

wizpig-paladin keep failing at CommitQueueSync with following message:

[1;31m20:21:44: ERROR: <class 'chromite.lib.cros_build_lib.RunCommandError'>: return code: 255; command: repo forall -c git fetch --all
cmd=['repo', 'forall', '-c', 'git', 'fetch', '--all'], cwd=/b/swarming/w/ir/cache/cbuild/repository
Traceback (most recent call last):
  File "/b/swarming/w/ir/cache/cbuild/repository/chromite/lib/failures_lib.py", line 230, in wrapped_functor
    return functor(*args, **kwargs)
  File "/b/swarming/w/ir/cache/cbuild/repository/chromite/cbuildbot/stages/sync_stages.py", line 794, in PerformStage
    self.ManifestCheckout(new_manifest)
  File "/b/swarming/w/ir/cache/cbuild/repository/chromite/cbuildbot/stages/sync_stages.py", line 1109, in ManifestCheckout
    super(CommitQueueSyncStage, self).ManifestCheckout(next_manifest)
  File "/b/swarming/w/ir/cache/cbuild/repository/chromite/cbuildbot/stages/sync_stages.py", line 438, in ManifestCheckout
    self.repo.FetchAll()
  File "/b/swarming/w/ir/cache/cbuild/repository/chromite/cbuildbot/repository.py", line 637, in FetchAll
    cros_build_lib.RunCommand(cmd, cwd=self.directory)
  File "/b/swarming/w/ir/cache/cbuild/repository/chromite/lib/cros_build_lib.py", line 650, in RunCommand
    raise RunCommandError(msg, cmd_result)
RunCommandError: return code: 255; command: repo forall -c git fetch --all
cmd=['repo', 'forall', '-c', 'git', 'fetch', '--all'], cwd=/b/swarming/w/ir/cache/cbuild/repository

20:21:44: INFO: Translating result <class 'chromite.lib.cros_build_lib.RunCommandError'>: return code: 255; command: repo forall -c git fetch --all
cmd=['repo', 'forall', '-c', 'git', 'fetch', '--all'], cwd=/b/swarming/w/ir/cache/cbuild/repository
Traceback (most recent call last):
  File "/b/swarming/w/ir/cache/cbuild/repository/chromite/lib/failures_lib.py", line 230, in wrapped_functor
    return functor(*args, **kwargs)
  File "/b/swarming/w/ir/cache/cbuild/repository/chromite/cbuildbot/stages/sync_stages.py", line 794, in PerformStage
    self.ManifestCheckout(new_manifest)
  File "/b/swarming/w/ir/cache/cbuild/repository/chromite/cbuildbot/stages/sync_stages.py", line 1109, in ManifestCheckout
    super(CommitQueueSyncStage, self).ManifestCheckout(next_manifest)
  File "/b/swarming/w/ir/cache/cbuild/repository/chromite/cbuildbot/stages/sync_stages.py", line 438, in ManifestCheckout
    self.repo.FetchAll()
  File "/b/swarming/w/ir/cache/cbuild/repository/chromite/cbuildbot/repository.py", line 637, in FetchAll
    cros_build_lib.RunCommand(cmd, cwd=self.directory)
  File "/b/swarming/w/ir/cache/cbuild/repository/chromite/lib/cros_build_lib.py", line 650, in RunCommand
    raise RunCommandError(msg, cmd_result)
RunCommandError: return code: 255; command: repo forall -c git fetch --all
cmd=['repo', 'forall', '-c', 'git', 'fetch', '--all'], cwd=/b/swarming/w/ir/cache/cbuild/repository
 to fail.

+wtlee
How about we label it as EXPERIMENTAL first?

 

Comment 1 by wtlee@chromium.org, Today (23 hours ago)

Owner: mikenichols@chromium.org

Comment 2 by wtlee@chromium.org, Today (23 hours ago)

Yes, we should make it EXPERIMENTAL currently. 

Hi Mike, could you take a look for this issue? Thanks.

Comment 3 by wtlee@chromium.org, Today (23 hours ago)

Cc: -wtlee@chromium.org athilenius@chromium.org

Comment 4 by wtlee@chromium.org, Today (23 hours ago)

Cc: wtlee@chromium.org

Comment 5 by dburger@google.com, Today (15 hours ago)

Perhaps interesting from those logs:

error: cannot open .git/FETCH_HEAD: Permission denied

Comment 6 by athilenius@chromium.org, Today (12 hours ago)

Owner: athilenius@chromium.org

Comment 7 by wtlee@chromium.org, Today (58 minutes ago)

It seems it is passed in latest build. Might be resolved.

Comment 8 by wtlee@chromium.org, Today (49 minutes ago)

Status: Closed (was: Untriaged)

Sign in to add a comment