Need help with failing mercurial imports
I have recently requested two new imports from mercurial repos. Both are marked as failing, with a variety of different error messages:
https:/
and
https:/
Could someone please have a look at those and tell me what's going on?
Question information
- Language:
- English Edit question
- Status:
- Expired
- Assignee:
- No assignee Edit question
- Last query:
- 2010-07-26
- Last reply:
- 2010-08-10
| Tim Penhey (thumper) said : | #1 |
It looks to me as if the processes are being killed. Several failed with MemoryErrors, others with SIG_KILL (9) and SIG_TERM (15). There are some that appear to be connection failures, but I'm guessing that these might be masking one of the other issues here.
Have you tried the import locally to see if it succeeds within a reasonable time or memory?
If it doesn't we should file some bugs on the bzr-hg plugin.
| Peter Bex (peter-bex) said : | #2 |
I tried to fetch the repository, but at some point "fetching manifests 500/4219) it was already using 1.6G of memory!
I found this bugreport in the bzr-hg bugtracker: https:/
Is this fix already rolled out on Launchpad?
| Peter Bex (peter-bex) said : | #3 |
Come to think of it, I cloned trunk bzr-hg, so I guess it must either be a regression, the bug is only fixed in some other branch or it's another bug. Most likely another bug...
| Launchpad Janitor (janitor) said : | #4 |
This question was expired because it remained in the 'Open' state without activity for the last 15 days.
| Jelmer Vernooij (jelmer) said : | #5 |
In the second case the server appears to be dropping the connection for some reason.
