commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Barker" <wbar...@wilshire.com>
Subject Re: [nightly build] codec net proxy failed.
Date Sat, 18 Nov 2006 21:47:06 GMT

"Phil Steitz" <phil.steitz@gmail.com> wrote in message 
news:8a81b4af0611181129h5f8a6d56rabbc502998952b35@mail.gmail.com...
> Hi James,
>
> Sorry for the response latency.  Nothing should have changed in the
> setup. In the logs (linked below) we are seeing
>
> Connection refused to host: 209.237.227.200; nested exception is:
>    [junit] java.net.ConnectException: Connection timed out
>
> Is that host available and accepting connections?

I'm betting that that host is vmbuild :).  Gump has the same error, except 
the address differs in the last number (and is the address of vmgump).  So 
I'm guessing that the machines aren't allowing connections on their external 
address.
>
> -Phil
>
> On 11/15/06, James Carman <james@carmanconsulting.com> wrote:
>> I haven't changed anything with proxy's RMI-based test cases.  Has
>> something in the environment changed that would not allow the test
>> cases to run successfully (they need to create an RMI registry, lookup
>> an RMI registry, etc.)?
>>
>>
>> On 11/15/06, Henri Yandell <flamefew@gmail.com> wrote:
>> > I've sudo'd over to your user (hope you don't mind), fixed things up
>> > (put the new nightly_wrapper.sh in place) and changed the crontab from
>> > 0:17 to 2:58 so it'll run again.
>> >
>> > I also ran svn cleanup on the trunks-proper as things were a bit
>> > messed up for cli/jelly. need to improve the script to do its best to
>> > fix things and get rid of tmp build files before kicking things off
>> > (added as a todo in the script).
>> >
>> > It seems to be ticking along, so hopefully an email will show telling
>> > us our failures etc.
>> >
>> > Hen
>> >
>> > On 11/15/06, Henri Yandell <flamefew@gmail.com> wrote:
>> > > Found the errors (the source $conf line is failing). And that I'm an
>> > > idiot who left an 'exit;' in too, though that's a relief in this case
>> > > as it stops things from running. Time for some scripting...
>> > >
>> > > On 11/15/06, Henri Yandell <flamefew@gmail.com> wrote:
>> > > > I suspect I broke the nightly build :)
>> > > >
>> > > > Did you get errors Phil?
>> > > >
>> > > > [we need to add a commons user on vmbuild and give various of us on
>> > > > there sudo to that]
>> > > >
>> > > > On 13 Nov 2006 12:01:02 -0000, psteitz@apache.org 
>> > > > <psteitz@apache.org> wrote:
>> > > > > Failed build logs:
>> > > > > http://people.apache.org/~psteitz/commons-nightlies/20061113/codec.log
>> > > > > http://people.apache.org/~psteitz/commons-nightlies/20061113/net.log
>> > > > > http://people.apache.org/~psteitz/commons-nightlies/20061113/proxy.log
>> > > > >
>> > > > > ---------------------------------------------------------------------
>> > > > > To unsubscribe, e-mail: 
>> > > > > commons-dev-unsubscribe@jakarta.apache.org
>> > > > > For additional commands, e-mail: 
>> > > > > commons-dev-help@jakarta.apache.org
>> > > > >
>> > > > >
>> > > >
>> > >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
>> > For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>>
>> 




---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message