diff options
author | Neil Fuller <nfuller@google.com> | 2014-09-12 15:01:52 +0100 |
---|---|---|
committer | Neil Fuller <nfuller@google.com> | 2014-09-12 15:17:17 +0100 |
commit | d42af6ed0fec3cfca52912b0d8b3b459e72be4b4 (patch) | |
tree | ebc94896a7766070daf211fee317aeacdf8f1ddf /annotations/generate_annotated_java_files.py | |
parent | 8806710d7a5cd6a168f2463de21498c58f70948a (diff) |
Fix ZoneInfo.useDaylightTime()
Currently implemented is "are there any offset transitions
in the future?".
This is wrong: Transitions may occur in the future because
of DST, but can also occur for other reasons (e.g. if the
raw offset for a zone changes).
We should be implementing: Is the currently active transition,
or any transition in the future, one that has
isDst == true.
This was causing a test failure in
libcore.java.util.TimeZoneTest#testDisplayNames
for Asia/Novokuznetsk and Europe/Simferopol for
tzdata2014g. This is because they have a transition entry
for October 26, 2014 (i.e. in the future).
For each, the existance of the transition entry is not
due to an offset change at all:
For Asia/Novokuznetsk it is because the abbreviation
for the zone changes on that date (information we don't
curently use).
For Europe/Simferopol it is because the offset from
UTC changes on that date (but there is no actual DST
transtion).
Bug: 17377276
Change-Id: Ie81bae91baf38e99516bafed39028842af03c07a
Diffstat (limited to 'annotations/generate_annotated_java_files.py')
0 files changed, 0 insertions, 0 deletions