Looks like the restricted capability used for test needs to be bundle2 aware otherwise capability negotiation get really confused. This ticket mostly exists to keep track of things we still to take care of with bundle2 First few lines of test failure. --- /home/marmoute/mercurial-testing/tests/test-treediscovery.t +++ /home/marmoute/mercurial-testing/tests/test-treediscovery.t.err @@ -42,6 +42,8 @@ $ hg pull -R empty1 $remote pulling from http://localhost:$HGPORT/ no changes found + abort: cannot look up remote changes; remote repository does not support the 'getbundle' capability! + [255] $ hg push -R empty1 $remote pushing to http://localhost:$HGPORT/ no changes found @@ -101,6 +103,8 @@ pulling from http://localhost:$HGPORT/ searching for changes no changes found + abort: cannot look up remote changes; remote repository does not support the 'getbundle' capability! + [255] $ hg push $remote pushing to http://localhost:$HGPORT/ searching for changes
Fixed by http://selenic.com/repo/hg/rev/249c7e922d1a Pierre-Yves David <pierre-yves.david@fb.com> test-discovery: disable bundle2 for legacy test (issue4610) We need to disable the "bundle2" capability to ensure we stay on legacy capability. (please test the fix)
Bug was set to TESTING for 7 days, resolving