On 22/04/2013 19:32, Xueming Shen wrote:
Hi,
This is a "test regression" caused by the JSR310 latest push into TL
repository, in which
the timezone name handling is slightly different for those "special"
timezone name such
as UTC, GMT and UT. The offending test case has not been updated
accordingly (the test
case had the old workaround to map the UTC/GMT/UT back to JSR310
specific "Z" for the
golden data, which is no longer needed in the latest JSR310
spec/implementation), so
it fails on env/conf that has the TZ configured to UTC/GMT/UT, which
is likely on some
server machines, like our JPRT solaris machines. The proposed change
has been reviewed
and pushed into JSR310 repo already, guess it might be preferred to
push this test case
only/simple fix into the TL to remove the test/nightly test failure.
http://cr.openjdk.java.net/~sherman/8012638/webrev
This looks okay to me. The test should probably list 8003680 before bugs
for subsequent changes.
-Alan.
