[
https://issues.apache.org/jira/browse/HBASE-25385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17293288#comment-17293288
]
Andrew Kyle Purtell commented on HBASE-25385:
---------------------------------------------
I was able to reproduce this on a vanilla Amazon Linux EC2 instance.
We should rewrite this to be TZ independent or remove it. TZ is a notoriously
difficult aspect of operations. We are begging for hassle by depending on it.
> TestCurrentHourProvider fails if the latest timezone changes are not present
> ----------------------------------------------------------------------------
>
> Key: HBASE-25385
> URL: https://issues.apache.org/jira/browse/HBASE-25385
> Project: HBase
> Issue Type: Bug
> Reporter: Christine Feng
> Priority: Minor
>
> According to [this
> link|https://www.oracle.com/java/technologies/tzdata-versions.html], a few
> timezones underwent changes in October of this year. For environments that do
> not have these latest updates, TestCurrentHourProvider will fail since
> information for certain time zones is out of date.
> Example: On an environment running jdk8, this test fails for timezones
> America/Dawson, America/Whitehorse, Canada/Yukon, and Antarctica/Casey (all
> of which were affected by the latest changes described at the above link).
> It seems that if timezone information on a particular environment is not up
> to date with the latest changes, this shouldn't indicate a failure of
> CurrentHourProvider, especially since this test specifically tests the
> functionality of CurrentHourProvider and using EnvironmentEdgeManager to mock
> time.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
