Ludovic Brenta wrote:
> The kfreebsd-i386 buildd, finzi.debian.org, had similar failures,
> this time the error message is:
>
> polyorb.utils.sockets: connect to 172.17.12.2 failed: [61] Connection
> refused
>
> (as opposed to 172.17.12.3 on fano.debian.org).
>
> Is it possible that these IP add
The kfreebsd-i386 buildd, finzi.debian.org, had similar failures,
this time the error message is:
polyorb.utils.sockets: connect to 172.17.12.2 failed: [61] Connection
refused
(as opposed to 172.17.12.3 on fano.debian.org).
Is it possible that these IP addresses really are those of the DNS serv
Ludovic Brenta schrieb:
> Some of the tests of 2.6.0~20090423-4 just failed on the kfreebsd-amd64
> buildd (they all passed in the previous build). Apparently all the test
> failures were due to:
>
> polyorb.utils.sockets: connect to 172.17.12.3 failed: [61] Connection
> refused
>
> The IP addre
Some of the tests of 2.6.0~20090423-4 just failed on the kfreebsd-amd64
buildd (they all passed in the previous build). Apparently all the test
failures were due to:
polyorb.utils.sockets: connect to 172.17.12.3 failed: [61] Connection
refused
The IP address of the host (fano.debian.org) appear
Lucas Nussbaum wrote:
> On 27/01/10 at 09:42 +0100, Ludovic Brenta wrote:
>>
>> Lucas Nussbaum wrote:
>>> What about testing with the network down to find which is the
>>> affected test, and disable that test?
>>
>> "the network down" is much too general. Remember: this is about
>> distributed app
On 27/01/10 at 09:42 +0100, Ludovic Brenta wrote:
>
> Lucas Nussbaum wrote:
> > What about testing with the network down to find which is the affected
> > test, and disable that test?
>
> "the network down" is much too general. Remember: this is about distributed
> applications; they obviously re
Lucas Nussbaum wrote:
> What about testing with the network down to find which is the affected
> test, and disable that test?
"the network down" is much too general. Remember: this is about distributed
applications; they obviously require "the network". What that means is
they must at least be a
On 26/01/10 at 21:51 +0100, Ludovic Brenta wrote:
> Lucas Nussbaum writes:
> > severity 562342 serious
> > thanks
> > On 26/01/10 at 20:36 +0100, Ludovic Brenta wrote:
> >> This is clearly a problem with the network configuration of the machine
> >> doing the tests. I will close the bug when I ful
Lucas Nussbaum writes:
> severity 562342 serious
> thanks
> On 26/01/10 at 20:36 +0100, Ludovic Brenta wrote:
>> This is clearly a problem with the network configuration of the machine
>> doing the tests. I will close the bug when I fully understand what part
>> of the configuration triggers the t
severity 562342 serious
thanks
On 26/01/10 at 20:36 +0100, Ludovic Brenta wrote:
> This is clearly a problem with the network configuration of the machine
> doing the tests. I will close the bug when I fully understand what part
> of the configuration triggers the test failures; in the mean time,
severity 562342 minor
thanks
This is clearly a problem with the network configuration of the machine
doing the tests. I will close the bug when I fully understand what part
of the configuration triggers the test failures; in the mean time,
lowering the severity to minor. Note that polyorb being
11 matches
Mail list logo
