Peter, Mark,
Just to verify the proxy settings are correct, I did:
setenv http_proxy http://wwwcache.rl.ac.uk:8080
wget
http://www.astro.gla.ac.uk/users/norman/star/dvi2bitmap/releases/dvi2bitmap-
0.12-2.tar.gz
--15:06:24--
http://www.astro.gla.ac.uk/users/norman/star/dvi2bitmap/releases/dvi2bitmap-
0.12-2.tar.gz
=> `dvi2bitmap-0.12-2.tar.gz'
Resolving wwwcache.rl.ac.uk... done.
Connecting to wwwcache.rl.ac.uk[130.246.135.176]:8080... connected.
Proxy request sent, awaiting response... 200 OK
Length: 937,462 [application/x-tar]
100%[====================================>] 937,462 1.64M/s ETA
00:00
15:06:24 (1.64 MB/s) - `dvi2bitmap-0.12-2.tar.gz' saved [937462/937462]
So wget works with the proxy set on the build system.
Steve,
-----Original Message-----
From: Starlink development [mailto:[log in to unmask]] On Behalf Of
Rankin, SE (Stephen)
Sent: 24 January 2005 15:00
To: [log in to unmask]
Subject: Re: Starlink Nightly Build On System:RHEL-WS3-3_i386
Peter, Mark,
My .stardev.properties looks like,
star.dir=/home/vmwareshare/rhel30linux_i386/build/build-root/starjava
star.archive.dir=/home/vmwareshare/rhel30linux_i386/build/packages/tars
stardev=/home/vmwareshare/rhel30linux_i386/build/build-root
perl=/usr/bin/perl
http.proxyHost=wwwcache.rl.ac.uk
http.proxyPort=8080
Steve.
-----Original Message-----
From: Starlink development [mailto:[log in to unmask]] On Behalf Of
Peter W. Draper
Sent: 24 January 2005 13:41
To: [log in to unmask]
Subject: Re: Starlink Nightly Build On System:RHEL-WS3-3_i386
On Mon, 24 Jan 2005, Mark Taylor wrote:
> 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?
Mark,
not as far as I know. Steve lines the lines:
# Proxy settings.
http.proxyHost=wwwcache.rl.ac.uk
http.proxyPort=8080
to the .stardev.properties file you use and that should get the proxy
working.
> 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?
Yes, let's do that. I've added a note to AntDevelopmentSystem requiring it
for the test target.
Cheers,
Peter.
|