On Sun, 23 Jan 2005, Starlink Software wrote:
> Module: starjava
> Status: failed
> Build URL: http://dev.starlink.ac.uk/build/RHEL-WS3-3_i386/logs/starjava.1106440596.log
The failures in the VOTable test targets are due to some connections to
an external URL failing. This is either because there's some problem
with java making HTTP connections through the firewall or possibly
because the site in question was down at the time of the test.
Apart from the test target itself, it looks to me like the starjava
build has gone through OK.
I have modified the test in question so that the VOTable tests do not
make any external network connections, so these ought to run OK next time.
However, there are some tests which do need external connections,
for instance in the VO package, so if the test machine does have
problems with external network access the tests may still fail next time.
Some such problems can be solved with suitable proxy settings (Peter is
the expert on this). Steve/Peter, are these in place on the test machine?
And/or we could institute a policy that a normal test only does things
which can work without requiring network connections, or maybe a
system property along the lines of java.awt.headless which test programs
ought to check before attempting something networky. Opinions?
Mark
--
Mark Taylor Starlink Programmer Physics, Bristol University, UK
[log in to unmask] +44-117-928-8776 http://www.star.bris.ac.uk/~mbt/
|