 |
 |
Norman, That was the build on the 18th, last nights build is still running. It looks like the clock on that PC is out too, I will fix that. Note, I keep a copy of the cvs repository on venus, which is updated every night before the builds start. This means that any commits after the build is started are ignored until the next day. It would be very confusing if commits where going on while the build was happening, like I said in the meeting, the nightly build checks out each module individually. We do not want commits happening while the nightly build is going on. Steve. -----Original Message----- From: Starlink development [mailto:[log in to unmask]] On Behalf Of Norman Gray Sent: 18 January 2005 20:29 To: [log in to unmask] Subject: Re: Starlink Nightly Build On System: DEBIAN-3.0r3_i386 On 2005 Jan 18 , at 19.03, Starlink Software wrote: > Module: dvi2bitmap > Status: failed > Build Log: > http://dev.starlink.ac.uk/build/DEBIAN-3.0r3_i386/logs/ > dvi2bitmap.1106019224.log But I fixed this! The log file is showing (the Makefile which comes from) revision 1.17 of Makefile.am, but I committed revision 1.18 -- see <http://cvsweb.starlink.ac.uk/cvsweb.cgi/applications/dvi2bitmap/ Makefile.am> -- at 11 this morning. Shouldn't the build have the most up-to-date version? Norman -- ---------------------------------------------------------------------- Norman Gray : Physics & Astronomy, Glasgow University, UK http://www.astro.gla.ac.uk/users/norman/ : www.starlink.ac.uk