dev-vcs/mercurial-3.8.4 fails the tests test-clonebundles.t test-paths.t due to feature 'network-sandbox'. The error messages are ------------------- test-clonebundles.t test-clonebundles.t ... # Test test-clonebundles.t # Running sh "/var/tmp/portage/dev-vcs/mercurial-3.7.3/temp/test/child78/test-clonebundles.t.sh" --- /var/tmp/portage/dev-vcs/mercurial-3.7.3/work/mercurial-3.7.3/tests/test-clonebundles.t +++ /var/tmp/portage/dev-vcs/mercurial-3.7.3/work/mercurial-3.7.3/tests/test-clonebundles.t.err @@ -52,7 +52,7 @@ $ echo 'http://does.not.exist/bundle.hg' > server/.hg/clonebundles.manifest $ hg clone http://localhost:$HGPORT 404-url applying clone bundle from http://does.not.exist/bundle.hg - error fetching bundle: (.* not known|getaddrinfo failed) (re) + error fetching bundle: Temporary failure in name resolution abort: error applying bundle (if this error persists, consider contacting the server operator or disable clone bundles via "--config ui.clonebundles=false") [255] ERROR: test-clonebundles.t output changed !# Killing daemon process 24997 # Killing daemon process 25010 ------------------- and (the not so obvious one) ------------------- test-paths.t test-paths.t ... # Test test-paths.t # Running sh "/var/tmp/portage/dev-vcs/mercurial-3.8.4/temp/test/child265/test-paths.t.sh" --- /var/tmp/portage/dev-vcs/mercurial-3.8.4/work/mercurial-3.8.4/tests/test-paths.t +++ /var/tmp/portage/dev-vcs/mercurial-3.8.4/work/mercurial-3.8.4/tests/test-paths.t.err @@ -100,10 +100,8 @@ zeroconf wraps ui.configitems(), which shouldn't crash at least: $ hg paths --config extensions.zeroconf= - dupe = $TESTTMP/b#tip (glob) - dupe:pushurl = https://example.com/dupe - expand = $TESTTMP/a/$SOMETHING/bar (glob) - insecure = http://foo:***@example.com/ + abort: No such device + [255] $ cd .. ERROR: test-paths.t output changed ! Keeping testtmp dir: /var/tmp/portage/dev-vcs/mercurial-3.8.4/temp/test/child265/test-paths.t Keeping threadtmp dir: /var/tmp/portage/dev-vcs/mercurial-3.8.4/temp/test/child265 # Ret was: 0 (test-paths.t) ------------------- Emerging mercurial with feature 'network-sandbox' disables lets the tests pass. Suggestion: Disable those two tests or patch the tests to also match this alternative outcome. Note: For easier testing you can edit the existing mercurial-X.ebuild and add the tests names test-clonebundles.t test-paths.t to the end of the run-tests.py command: pytest <something> test-clonebundles.t test-paths.t
dev-vcs/mercurial-4.2 passed its tests for me.
Tested again with 4.2 and 4.1.3. For 4.2 and 4.1.3: The test test-clonebundles.t still fails the same away although the regex pattern was slightly adjusted to error fetching bundle: (.* not known|getaddrinfo failed|No address associated with hostname) (re) The test test-paths.t is fixed in 4.2 but still fails in 4.1.3 with the same error as before.
Fixed by https://phab.mercurial-scm.org/D6870
