[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Strange error resolving non-existent hostname
Recently, a mercurial test has started failing for me (7.99.21/amd64):
@@ -80,7 +80,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 (glob)
+ error fetching bundle: No address associated with hostname
abort: error applying bundle
(if this error persists, consider contacting the server operator or disable clone bundles via "--config experimental.clonebundles=false")
ERROR: test-clonebundles.t output changed
In other words, the test tries resolving does.not.exist and expects
any error message ending with 'not known' but gets the one for
EAI_NODATA, in contrast to all other operating systems (according to
the mercurial author).
Can someone else please try this, to make sure it's not my DNS setup?
cd /usr/pkgsrc/devel/py-mercurial && make test
Any ideas what could be the reason for this?
Main Index |
Thread Index |