On 3/04/2003 13:43 Sam Ruby wrote:
I will correct this - though the machine is located in Kansas, we prefer to have the clock on GMT+1 time, but the sysadmins apparently forgot to set the timezone consequently.
Everything is virtual these days. ;-)
Ha! :-)
FYI: I've put in a workaround until this problem is corrected. This consisted of a a simple touch command, specifying a point 8 hours in the future, so gump runs should have the correct date. This covers the nightly build, but if people issue any "build gump" related commands between the hours of midnight and approximately 8am (depending on daylight savings time), then the results will be incorrect.
No idea neither. What java -versions are in use on the other machines?
cocoondev: 1.4.1_01 nagoya: 1.4.0 lsd: 1.4.0_01 rubix: 1.4.0_01
Note: nagoya is solaris, the rest are linux on intel.
Yup. Could you provide me with the exact JDK build level of lsd and rubix? There's plenty of them on cocoondev.org, so maybe switching those might help:
drwxr-xr-x 9 root root 4096 Jun 27 2001 j2sdk1.3.1 drwxr-xr-x 8 root root 4096 Jan 30 2002 j2sdk1.4.0 drwxr-xr-x 8 root root 4096 Jul 24 2002 j2sdk1.4.0_02 drwxr-xr-x 9 root root 4096 Oct 8 16:58 j2sdk1.4.1 drwxr-xr-x 9 root root 4096 Nov 20 08:55 j2sdk1.4.1_01 drwxr-xr-x 9 root root 4096 Mar 10 01:24 j2sdk1.4.1_02
</Steven>
I've just upgraded rubix to java full version "1.4.1_02-b06". This matches what is installed in /usr/j2sdk1.4.1_02 on cocoondev. We'll see how tonight's builds go...
- Sam Ruby
