Problems cloning mozilla-unified repo

RESOLVED WORKSFORME

Status

RESOLVED WORKSFORME
2 years ago
2 years ago

People

(Reporter: aleth, Unassigned)

Tracking

Details

(Reporter)

Description

2 years ago
STR (Mercurial 3.8.3, OS X 10.11.5):

hg clone https://hg.mozilla.org/mozilla-unified mozilla
applying clone bundle from https://hg.cdn.mozilla.net/mozilla-unified/a45e92e6ebe31a63abda96d3d0728f39b9c308ca.gzip-v2.hg
adding changesets
adding manifests
adding file changes                                     
transaction abort!
rollback completed
abort: stream ended unexpectedly (got 0 bytes, expected 4)

This was reproducible, so I tried unbundling manually:
wget https://hg.cdn.mozilla.net/mozilla-unified/a45e92e6ebe31a63abda96d3d0728f39b9c308ca.gzip-v2.hg
hg unbundle a45e92e6ebe31a63abda96d3d0728f39b9c308ca.gzip-v2.hg mozilla

This did not produce errors, but seems to take forever (now >1h) compared to a straightforward mozilla-central clone or unbundle.
(Reporter)

Comment 1

2 years ago
Retrying 
hg clone https://hg.mozilla.org/mozilla-unified mozilla
today WFM.

Comment 2

2 years ago
This smells like connectivity issues :/

It is a known issue with Mercurial (and Git) that connection drops during clone result in a poor user experience by deleting all local, already-obtained data. I know the Mercurial project has talked about "checkpointing" clones so most cloned data will be retained. However, nobody has stepped up to implement that feature yet :(
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.