-
Notifications
You must be signed in to change notification settings - Fork 25.3k
DateTimeToCharProcessorTests test {tochar-generated.csv:76 mi @ FMmiTH} failing #128585
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Just Gave absolute path
The issue is that CET timezone rules don't exist for dates in 25... BC. Modern timezone definitions only go back a few hundred years, but this test is trying to apply CET timezone rules to an ancient date, causing unpredictable behavior across different Java implementations.
💚 CLA has been signed |
Pinging @elastic/es-analytical-engine (Team:Analytics) |
Thanks for your contribution @Aariyan007 !
|
Hi! I wasn’t able to find |
You can find it here: https://github.com/elastic/elasticsearch/blob/main/muted-tests.yml#L144-L145 |
I’ve removed DateTimeToCharProcessorTests from muted-tests.yml as requested. Let me know if anything else needs to be updated. |
buildkite test this |
Fix: DateTimeToCharProcessorTests ancient date timezone issue
Problem: Test failing with ancient timestamp (2594 BC) using CET timezone - timezone rules don't exist that far back, causing inconsistent behavior across Java versions.
Solution: Changed CET to UTC on line 178 of tochar-generated.csv and updated expected output.
Result: Eliminates 13.4% test failure rate and fixes flaky behavior across all Java configurations.
Files changed:
x-pack/plugin/sql/src/test/resources/tochar-generated.csv