Anyone able to sort out windows1 slave for our build; it started failing
a day or two ago.
Looking at the stack trace (below), suggests that maybe there's a
problem with cleaning up its local workspace. But that's only a guess.
Thx
Dan
Original Message
Subject:Bui
A few days ago we started getting the error below on our windows job
(isis-framework-windows);
To me it looks like a problem with the configuration of the slave (did
it recently get a new disk)?
If anyone could look at this, I'd appreciate it.
Cheers
Dan
~~~
ERROR: Ignore Proble
We've been seeing intermittent fails too; looking at the console output
it would seem that ubuntu1 fails for us, ubuntu2 succeeds:
succeed on ubuntu2:
https://builds.apache.org/hudson/view/G-L/view/Isis/job/isis-trunk-ubuntu/140/consoleFull
fail on ubuntu1:
https://builds.apache.org/hudson/view
Hi Niklas,
Any idea, then, why these jobs failed? Or failing that, any suggestions
as to how I might be able to diagnose the issue myself?
Thanks
Dan
On 01/02/2011 08:17, Niklas Gustavsson wrote:
On Tue, Feb 1, 2011 at 7:30 AM, Dan Haywood wrote:
The problem seems to be the "install&q
We've been getting some problems over recent days with our build
Build 71 [1] went through ok, but the two commits since then triggering
builds 72 [2] and 73 [3] have failed.
The problem seems to be the "install" phase, ie copying JARs into
~/.m2/repository, which makes me wonder about disk s
