Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 610102 - dev-vcs/mercurial fails tests test-clonebundles.t and test-paths.t due to feature 'network-sandbox'
Summary: dev-vcs/mercurial fails tests test-clonebundles.t and test-paths.t due to fea...
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Cédric Krier
Depends on:
Reported: 2017-02-20 17:27 UTC by Maram
Modified: 2021-07-17 15:54 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Note You need to log in before you can comment on or make changes to this bug.
Description Maram 2017-02-20 17:27:22 UTC
dev-vcs/mercurial-3.8.4 fails the tests


due to feature 'network-sandbox'.

The error messages are

test-clonebundles.t ... # Test test-clonebundles.t
# Running sh "/var/tmp/portage/dev-vcs/mercurial-3.7.3/temp/test/child78/" 

--- /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")

ERROR: test-clonebundles.t output changed
!# Killing daemon process 24997
# Killing daemon process 25010

and (the not so obvious one)

test-paths.t ... # Test test-paths.t 
# Running sh "/var/tmp/portage/dev-vcs/mercurial-3.8.4/temp/test/child265/" 

--- /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 =
-  expand = $TESTTMP/a/$SOMETHING/bar (glob)
-  insecure = http://foo:***
+  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.

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 command:

    pytest <something>  test-clonebundles.t test-paths.t
Comment 1 Aaron W. Swenson gentoo-dev 2017-06-02 09:28:30 UTC
dev-vcs/mercurial-4.2 passed its tests for me.
Comment 2 Maram 2017-06-03 14:27:38 UTC
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.
Comment 3 Cédric Krier gentoo-dev 2021-07-17 15:54:49 UTC
Fixed by