On 11/18/06, Bill Barker [EMAIL PROTECTED] wrote:
Phil Steitz [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
On 11/18/06, Bill Barker [EMAIL PROTECTED] wrote:
I found the problem with Gump, and I'm betting that it is the same
problem
with [nightly build]. The /etc/hosts file on
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
Phil Steitz [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
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]
I found the problem with Gump, and I'm betting that it is the same problem
with [nightly build]. The /etc/hosts file on vmgump still had the old IP
address for vmgump. I changed it to the new address, and now
INA.getLocalHost() returns the right address.
Bill Barker [EMAIL PROTECTED] wrote
On 11/18/06, Bill Barker [EMAIL PROTECTED] wrote:
I found the problem with Gump, and I'm betting that it is the same problem
with [nightly build]. The /etc/hosts file on vmgump still had the old IP
address for vmgump. I changed it to the new address, and now
INA.getLocalHost() returns the
Phil Steitz [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
On 11/18/06, Bill Barker [EMAIL PROTECTED] wrote:
I found the problem with Gump, and I'm betting that it is the same
problem
with [nightly build]. The /etc/hosts file on vmgump still had the old IP
address for vmgump.
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 -, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Failed build logs:
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 [EMAIL PROTECTED] wrote:
I've sudo'd
Failed build logs:
http://people.apache.org/~psteitz/commons-nightlies/20061115/codec.log
http://people.apache.org/~psteitz/commons-nightlies/20061115/net.log
http://people.apache.org/~psteitz/commons-nightlies/20061115/proxy.log
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
10 matches
Mail list logo