[Bug 6136] New: hg pull hg-committed seems to get stuck in an infinite loop
mercurial-bugs at mercurial-scm.org
mercurial-bugs at mercurial-scm.org
Sat May 11 02:29:00 UTC 2019
https://bz.mercurial-scm.org/show_bug.cgi?id=6136
Bug ID: 6136
Summary: hg pull hg-committed seems to get stuck in an infinite
loop
Product: Mercurial
Version: default branch
Hardware: PC
OS: Windows
Status: UNCONFIRMED
Severity: bug
Priority: normal
Component: evolution
Assignee: bugzilla at mercurial-scm.org
Reporter: matt_harbison at yahoo.com
CC: mercurial-devel at mercurial-scm.org,
pierre-yves.david at ens-lyon.org
Pull was taking an insane amount of time (> 5 minutes) with hg-838f3a094b4f and
evolve-b78707559f1f. So I killed it, was able to pull with 4.9.1, and then got
it stuck again with 838df3 (even without anything incoming).
I see it cycling through new https connections in ProcessExplorer, and mimimal
CPU being used.
C:\Users\Matt\hg>hg pull --debug
pulling from https://www.mercurial-scm.org/repo/hg-committed
using https://www.mercurial-scm.org/repo/hg-committed
sending capabilities command
query 1; heads
sending batch command
searching for changes
all remote heads known locally
no changes found
sampling from both directions
query 1; still undecided: 42270, sample size is: 200
sending evoext_obshash1 command
sampling from both directions
query 2; still undecided: 6267, sample size is: 200
sending evoext_obshash1 command
sampling from both directions
query 3; still undecided: 1835, sample size is: 200
sending evoext_obshash1 command
sampling from both directions
query 4; still undecided: 1835, sample size is: 200
sending evoext_obshash1 command
sampling from both directions
...
It's at query 46 after 500s, and not making any progress off of 1835. I assume
this is evolve, but don't want to disable it and try again in case there's any
local residual state that's tripping it up.
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the Mercurial-devel
mailing list