EVALUATION
Testcase was taken from wrong testsuite causing this failure.
15-02-2007
EVALUATION
Oops. It depends on the 6393531 fix, not time zone patches on Windows 2003.
14-02-2007
EVALUATION
If this Windows 2003 has the time zone patches installed, the 1.4.2_14 b03 test/java/util/TimeZone/WinZones must be used. The attached WinTZVM.jtr.142u14b03 shows that an old version of the test data was used as pointed out in the first Evaluation entry by ###@###.###. Please note that WinTZVM.sh is a test driver, and its actual test data is WinZones in the same directory.
14-02-2007
EVALUATION
Looked at the testcase (2/13/07 10:30 pst) in different testsuites (integration ws and /net/jdk one) and did not found any diff.
$ bringover
Parent workspace: /net/nightsvr/export4/integration/1.4.2_14/j2se
Child workspace: /net/shiva/test/MyTestArea/JDK1.4.2/workspace_142
cd /net/shiva/test/MyTestArea/JDK1.4.2/workspace_142/test; /net/nightsvr/export1
/nightly/1.4.0.tools/sparc/SUNWspro/SC6.1/bin/def.dir.flp &
cd /net/nightsvr/export4/integration/1.4.2_14/j2se/test; /net/nightsvr/export1/n
ightly/1.4.0.tools/sparc/SUNWspro/SC6.1/bin/def.dir.flp
Examined files: 10659
No changes to bring over
$pwd
/home/asaha/MyTestArea/JDK1.4.2/workspace_142
$ diff /net/nightsvr/export4/integration/1.4.2_14/j2se/test/java/util/TimeZone/WinTZVM.sh test/java/util/TimeZone/WinTZVM.sh
$ diff /net/jdk/export/jpse04/Regression/1.4.2/test/java/util/TimeZone/WinTZVM.sh test/java/util/TimeZone/WinTZVM.sh
Bug fix # 6393531, in 142_14 b02 did not change this testcase.
13-02-2007
EVALUATION
After working with Eugene on this bug, I've discovered that the java/util/TimeZone/WinZones test file used is old. 6393531 was integrated into 1.4.2_14 b02 and an accompanying testcase change was made. Please contact Abhijit to get the latest testcases.