[
https://issues.apache.org/jira/browse/HBASE-25385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17295512#comment-17295512
]
Hudson commented on HBASE-25385:
--------------------------------
Results for branch branch-2
[build #192 on
builds.a.o|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/192/]:
(/) *{color:green}+1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/192/General_20Nightly_20Build_20Report/]
(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/192/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/192/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/192/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> 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
> Affects Versions: 2.4.1
> Reporter: Christine Feng
> Assignee: Andrew Kyle Purtell
> Priority: Blocker
> Fix For: 3.0.0-alpha-1, 2.5.0, 2.4.2
>
>
> 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)
