I landed a change in bzr.dev 3840 that stops bzr from trying to push the
entire history into stacked branches. I believe this is the root cause,
but I can't be completely sure. If you are experiencing this problem,
please see whether bzr.dev 3840 solves it for you.
** Changed in: bzr
I'm running bzr nightly ppa.
Is this the smart server that needs updating?
--
1.9rc1 can't push to Launchpad
https://bugs.launchpad.net/bugs/293679
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I just had this again. I left it pushing for a *long* time and it
stabilised at ~700M resident memory before I got bored and killed it.
This is with the 1.9 release.
See attached log, bzipped, it's massive! Sorry ...
** Attachment added: bzr.log.bz2
This is happening more and more often now that everybody's submitting
stacked branches to Launchpad
** Changed in: bzr
Importance: High = Critical
Status: New = Triaged
--
1.9rc1 can't push to Launchpad
https://bugs.launchpad.net/bugs/293679
You received this bug notification because
So let's at least upgrade to 1.9final which is in the ppa. It does
have some fixes past rc1, though not necessarily one that fixes this.
--
Martin http://launchpad.net/~mbp/
--
1.9rc1 can't push to Launchpad
https://bugs.launchpad.net/bugs/293679
You received this bug notification because you
I had a similar problem just now pushing a (stacked) branch that I had
already pushed several times successfully last week, so I was just
pushing up a couple of revisions. But first I had the following bit of
fun:
$ bzr push
Using saved push location: bzr+ssh://[EMAIL
Julian Edwards wrote:
[...]
However, I did get a new error when pushing up a change to an existing
branch,
I don't know if this is related:
UnknownErrorFromSmartServer: Server sent an unexpected error: ('error',
'ProtocolError for xmlrpc.lp.internal:8097/branchfilesystem: -1 ')
That one
Ok, so being very slow is probably just bug 294479. (If you're keen,
you could try the patch there, or more simply just edit
bzrlib/repofmt/pack_repo.py so that self._cache_limit = 1024*1024
rather than 0. It should make the pushing much faster.)
I still have no idea what's causing the memory
Well I can't re-create this now either :/
The only difference is that I am using 1.9rc1-1 now as that is what I upgraded
to just now to test this out. However, I know I was not the only one with the
issue yesterday, so it might be some particular data that triggers the bug
rather than all
I also encountered this problem.
I have the pdb backtrace output. I also ran this with -Dhpss and can
give the log. Backtrace below, log attached.
[EMAIL PROTECTED]:~/canonical/lp-branches/bug288064$ bzr push -Dhpss
Using saved push location: lp:~garyposter/launchpad/bug288064
/ [==
Andrew, I tried the manual change (self._cache_limit = 0 -
self._cache_limit = 1024*1024) and it still didn't get past step 0 of
4 in 14 minutes, after which I killed it.
--
1.9rc1 can't push to Launchpad
https://bugs.launchpad.net/bugs/293679
You received this bug notification because you are a
BTW, I'll carry on using 1.9rc1-1 and let you know as soon as the problem
happens again, if it does.
--
1.9rc1 can't push to Launchpad
https://bugs.launchpad.net/bugs/293679
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Hmm, I can't reproduce your problem. I have found another problem, but
it doesn't seem to be this severe, and it is unchanged between 1.8 and
1.9rc1.
Unfortunately that traceback isn't very helpful either, because it's
showing an error during the abort, rather than where it was when it was
** Also affects: bzr
Importance: Undecided
Status: New
** Changed in: bzr (Ubuntu)
Status: New = Invalid
--
1.9rc1 can't push to Launchpad
https://bugs.launchpad.net/bugs/293679
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
You are pushing via bzr+ssh, I assume?
Did you get a backtrace in ~/.bzr.log when you killed it? If not, can
you try again and use SIGQUIT (hit Ctrl-\) to interrupt it when the
memory consumption gets high and then type bt at the pdb prompt to get
a backtrace.
** Changed in: bzr
Importance:
On Tuesday 04 November 2008 22:43:48 Andrew Bennetts wrote:
You are pushing via bzr+ssh, I assume?
Yep, sorry I should have mentioned that.
Did you get a backtrace in ~/.bzr.log when you killed it?
Yes:
Using saved push location: lp:~julian-edwards/launchpad/api_copy_packages
16 matches
Mail list logo
