[Springframework-developer] Compile Farm testing

[Darren D. <da...@da...>]

The test suite is now being built and run on as many CF machines as I can=
 get
it to work on.  Six machines currently have a JDK on them, but one of the=
 JDK
1.3.1 boxes always crashes the java process during the tests target with =
no
error message and I suspended the schedule for this machine.

Of the other five, four are working well.  Unfortunately, the fifth is th=
e
only other JDK 1.3.1 box and this is failing several tests that should be
passing (they pass on my machine using Sun 1.3.1 JDK at any rate).  The
machine is the 64-bit Opteron - if anyone else has a 64-bit chip anywhere=
, I'd
be interested to know how the test suite runs on any JDK.

Each of the five machines is running 3 builds per day with a CVS update f=
rom
the anonymous CVS servers (the only ones I can use from the compile farm)
prior to each round of builds.  If (and only if) a build fails an email i=
s
sent with the last few lines of output.  I intend to change the email tar=
get
today from my address to the dev list address assuming no objections.  On=
ce an
email has been sent to notify a failed build, no further mail will be sen=
t by
that machine until a manual reset is made for it, although the machine wi=
ll
continue to participate in scheduled updates and builds.

I've had a go at getting autobuilds to work on some of the machines too w=
hich
was the original goal, but this is fraught with additional problems.=20
Principally, the CF machines are so over worked that in some cases it is
taking in excess of 40 minutes just to do a complete build and test suite=
 run.
 Simply attempting to extract a tomcat binary can itself take something l=
ike
15-20 minutes when disk usage is particularly high.  Hopefully I'll get i=
t
running on at least one of the machines soon.

Regards,
--=20
Darren Davison
Public Key: #DD356B0D