Closed
Bug 1131591
Opened 9 years ago
Closed 9 years ago
Nexus 5 Builds busted
Categories
(Infrastructure & Operations Graveyard :: CIDuty, task)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1108957
People
(Reporter: cbook, Unassigned)
Details
seems the nexus 5 builds are busted on mozilla-inbound https://treeherder.mozilla.org/logviewer.html#?job_id=6461644&repo=mozilla-inbound 06:00 < pmoore> hmmmmm 06:01 < pmoore> that's a pretty ugly crash 06:02 < pmoore> ./repo forall -c "git show-ref -q --head HEAD || rm -rfv $PWD" causing a traceback (repo tool crashing) 06:02 < pmoore> maybe this is a recent mozharness change, let me take a look 06:06 < pmoore> doesn't seem to be 06:06 < pmoore> https://hg.mozilla.org/build/mozharness/rev/1527d06e46bd655eee7b446e7a4d02a60c192c6c#l1.381 06:07 < pmoore> i wonder if we've updated our repo version 06:08 < pmoore> https://code.google.com/p/git-repo/issues/detail?id=190
Comment hidden (Legacy TBPL/Treeherder Robot) |
Comment hidden (Legacy TBPL/Treeherder Robot) |
Comment 3•9 years ago
|
||
Looks like we are checking out repo from https://git.mozilla.org/?p=external/google/gerrit/git-repo.git;a=shortlog;h=refs/heads/stable See: http://hg.mozilla.org/build/mozharness/file/cc61099cd96a/scripts/b2g_build.py#l333 http://hg.mozilla.org/build/mozharness/file/cc61099cd96a/scripts/b2g_build.py#l139 It is possible that "stable" has been updated. A workaround might be to temporarily pin the revision to a known good commit, rather than the head of the stable branch: http://hg.mozilla.org/build/mozharness/file/cc61099cd96a/scripts/b2g_build.py#l140
Comment 4•9 years ago
|
||
Looks like we mirror from: https://gerrit.googlesource.com/git-repo/+/stable (see https://hg.mozilla.org/users/hwine_mozilla.com/repo-sync-configs/file/69f083a22c88/external-google-gerrit-git-repo/config#l6)
Comment 5•9 years ago
|
||
RyanVM has pointed out to me in IRC that the above error is a red herring, and appears in all the logs. The real error comes afterwards. Probably we should clean up the repo error too, but that is not the cause of this problem, it seems.
Reporter | ||
Comment 6•9 years ago
|
||
(In reply to Pete Moore [:pete][:pmoore] from comment #5) > RyanVM has pointed out to me in IRC that the above error is a red herring, > and appears in all the logs. The real error comes afterwards. > backed out Bug 1108957
Comment 7•9 years ago
|
||
cc-ing catlee based on https://hg.mozilla.org/build/mozharness/rev/cc61099cd96a
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
Updated•6 years ago
|
Product: Release Engineering → Infrastructure & Operations
Updated•4 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•