Importing large mercurial repository: it's been 17 hours; how much longer should I wait? Edited

I used the Import existing code tool to import a giant Mercurial repo. It's been chugging along for 17 hours. I can visit the import status page and see the following output:

18:16:15 hg import for:
18:16:15 Cloning
18:16:16 applying clone bundle from
18:16:18 adding changesets
18:20:46 adding manifests
19:49:09 adding file changes

It's now 11:49:05 the next day and here we are. Is this normal for a repository of that size? Is it wedged? Did the import time out without telling me?

Visiting the repository page redirects to the import status page, so something thinks it's still importing.

0 answers

Suggest an answer

Log in or Join to answer
Community showcase
Piotr Plewa
Published Dec 27, 2017 in Bitbucket

Recipe: Deploying AWS Lambda functions with Bitbucket Pipelines

Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda&nbsp...

638 views 0 4
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot