Closed Bug 758975 Opened 13 years ago Closed 12 years ago

Mozharness MercurialVCS should have a retry

Categories

(Release Engineering :: General, defect, P3)

Product:
Release Engineering
Component:
General
Platform:
ARM
Android
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 793642

People

(Reporter: philor, Unassigned)

References

Details

(Whiteboard: [mozharness]) 

http://ftp.mozilla.org/pub/mozilla.org/mobile/nightly/2012/05/2012-05-27-03-05-15-mozilla-central-android-xul/mozilla-central-android-xul-nightly-bm30-build1-build6.txt.gz

Built fine, uploaded en-US fine, cloned cs fine, died with "abort: connection ended unexpectedly" while cloning da.

Because of bug 732526, I can't do the reasonable thing and retrigger it, but I have a red "N" sitting on my push about which I have to do something, thus: a bug.

Not actually a broad solution to the problem, since for any amount of time you choose, hg.m.o is quite willing to intermittently fail for one minute longer than that, but, shouldn't mozharness have an equivalent of MercurialCloneCommand(RetryingShellCommand) that will keep pounding away at hg.m.o until it succeeds or all hope is lost?
Priority: -- → P3
Summary: Android XUL nightly died in repacks from hg clone failure → Mozharness MercurialVCS should have a retry
Whiteboard: [mozharness]
Blocks: 770960
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
Product: mozilla.org → Release Engineering
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.