progress bar for "finding fileprop revids" is misleading

Bug #448744 reported by Kevin Smith
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Bazaar Subversion Plugin
Triaged
Low
Unassigned

Bug Description

I had an empty bzr repo and tried this:

kevins@vanessa:~/work/miradi/eclipse/miradi$ bzr pull svn+ssh://subversion.benetech.org/opt/svn/repositories/benetech.org/Miradi/trunk -r1
[##########\ ] 255KB 0KB/s | finding fileprop revids 7911/14949

The KB keeps going up and up, but the numbers at the far right keep recycling. The following were all copied, in order, while I was composing this bug report:
[############\ ] 280KB 0KB/s | finding fileprop revids 9973/14949
[##################- ] 285KB 0KB/s | finding fileprop revids 13989/14949
[############/ ] 290KB 0KB/s | finding fileprop revids 9852/14949
[##################/ ] 307KB 0KB/s | finding fileprop revids 14072/14949
[##- ] 336KB 0KB/s | finding fileprop revids 2108/14949
[##########| ] 498KB 0KB/s | finding fileprop revids 8465/14949

(the reason it always shows 0KB/s here is because I can only copy text off the console when it is briefly stalled). This is a repository which I have successfully pulled from in other ways in the last couple days.

Running bzr 2.0.0 and bzr-svn 1.0.0

Revision history for this message
Jelmer Vernooij (jelmer) wrote :

The progress indicator might just the bit that is confusing here - I doubt it's actually going into an endless loop. Do you have a lot of merges in that repository, pushed by Bazaar?

Revision history for this message
Jelmer Vernooij (jelmer) wrote :

Can you try just letting it run for a while, and seeing whether it's just slow rather than looping?

Revision history for this message
Kevin Smith (ubuntu-qualitycode) wrote :

Ugh. I have no idea what changed, but I can't reproduce this any more. It did it several times yesterday, in different directories, during different work sessions. I let it run for a few minutes before quitting. Today, I tried twice and it didn't happen.

Revision history for this message
Kevin Smith (ubuntu-qualitycode) wrote :

I forgot to answer your other question: That repo probably has 20-50 revisions that were merged in from offline bzr work. All of them were pretty late (around revno 15000). There were definitely no merges before revno 1 that I was attempting to pull.

Jelmer Vernooij (jelmer)
Changed in bzr-svn:
status: New → Incomplete
Revision history for this message
Jelmer Vernooij (jelmer) wrote :

This is just slow, and the progress indicator isn't very helpful (since it's redisplayed for each revision). It's not an endless loop though.

Changed in bzr-svn:
status: Incomplete → Triaged
importance: Undecided → Low
Jelmer Vernooij (jelmer)
summary: - Pull goes into an endless loop of "finding fileprop revids"
+ progress bar for "finding fileprop revids" is misleading
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.