Closed Bug 493967 Opened 17 years ago Closed 17 years ago

l10n repacks go fubar on corrupted checkouts

Categories

(Release Engineering :: General, defect)

defect
Not set
major

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 475276

People

(Reporter: Pike, Unassigned)

References

()

Details

We're having pull issues, and apparently the hg source shell scripts go fubar in that condition. http://production-master.build.mozilla.org:8010/builders/WINNT%205.2%20mozilla-1.9.1%20l10n/builds/4738 is a build where the checkout just bails for "default" unknown in places, and doesn't come back anymore, it seems. We at least need to repair the broken slaves, and think about how to prevent them from breaking again.
As Axel mentions in: http://production-master.build.mozilla.org:8010/builders/WINNT%205.2%20mozilla-1.9.1%20l10n/builds/4738/steps/shell_9/logs/stdio we are getting: |abort: repository default not found! |abort: unknown revision 'default'! which comes from running this step: http://hg.mozilla.org/build/buildbotcustom/file/tip/process/factory.py#l1028 I noted that we are missing a haltOnFailure for the step. Would using the "Mercurial" step help us avoid it? http://hg.mozilla.org/build/buildbotcustom/file/tip/process/factory.py#l357 Do we know why we are hitting this problem?
This is likely a dupe of bug 475276. An incomplete clobber leaves us with a checkout dir that is most empty, but still open, so when our pull/clone step runs, it sees the dir already exists and tries to pull rather than clone.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → DUPLICATE
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.