Ignore Antarctica/Vostok timezone differences #104610
Merged
+1
−2
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
thecoop
added
>test
|
Pinging @elastic/es-core-infra (Team:Core/Infra) |
|
Rather than ignoring it, should we be updating Joda? 2.12.6 appears to contain the relevant timezone update: |
|
Lets try that - #104720 |
|
Upgrading joda doesn't fix this test - there's still some jdks where the timezone data differs. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
2023d has changed Antartica/Vostok, this means the JDK and joda timezones are out of sync.
This fixes #104544