Solaris fixes for a few tests
Giorgos Keramidas
keramida at ceid.upatras.gr
Fri Oct 20 17:09:38 UTC 2006
On 2006-10-20 09:09, Danek Duvall <danek.duvall at sun.com> wrote:
>On Fri, Oct 20, 2006 at 03:06:25AM -0300, Alexis S. L. Carvalho wrote:
>>> ,--------------------------------------------------------------------------
>>> | system: Solaris
>>> | version: Solaris 10 1/06 s10x_u1wos_19a X86 (amd64)
>>> +--------------------------------------------------------------------------
>>> | .........
>>> | ERROR: test-bad-pull output changed
>>> | --- Expected output
>>> | +++ Test output
>>> | @@ -1,4 +1,4 @@
>>> | -abort: error: Connection refused
>>> | +abort: error: Network is unreachable
>>
>> Eek - does Solaris really print that when there's no process listening
>> on a port (e.g. does something like "telnet localhost 38142" also print
>> that? What about "telnet 127.0.0.1 38142"? Assuming there's nobody
>> listening on that port...) Is there any chance you have some firewall
>> settings that could cause this?
>
> The cause of this (at least when I get it) is that you have both 127.0.0.1
> and ::1 as localhost in /etc/inet/ipnodes, but you don't have an ipv6
> interface up and running. Either ignore the error or bring up your ipv6
> loopback interface.
Quite right. I don't use IPv6 on the test system, so I commented out
the localhost <=> ::1 line in `/etc/inet/ipnodes'.
Then this test passes successfully:
$ python run-tests.py test-bad-pull
.
# Ran 1 tests, 0 skipped, 0 failed.
$
Thank you :)
More information about the Mercurial-devel
mailing list