[HBASE-25385] TestCurrentHourProvider fails if the latest timezone changes are not present

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 2.4.1
• Fix Version/s: 3.0.0-alpha-1, 2.5.0, 2.4.2
• Assignee: Andrew Kyle Purtell
• Reporter: Christine Feng
• Created: 10/Dec/20 23:22
• Updated: 05/Mar/21 01:58
• Resolved: 04/Mar/21 02:15

Description

According to this link, 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.

Issue Links

• duplicates: HBASE-25618 Add detailed logs about which time zone is failing in TestCurrentHourProvider
• links to: GitHub Pull Request #3012

Sub-Tasks

• Reimplement TestCurrentHourProvider to not depend on unstable TZs: Resolved