[CI] JdbcSqlSpecIT test {datetime.testCurrentTimestampYear} failing

[elasticsearchmachine]

Build Scans:

• elasticsearch-periodic #5648 / java11_java-matrix
• elasticsearch-periodic #5648 / java11_java-matrix
• elasticsearch-periodic-platform-support #5637 / sles-12_platform-support-unix
• elasticsearch-periodic-platform-support #5637 / sles-12_platform-support-unix
• elasticsearch-periodic-platform-support #5632 / windows-2022_checkpart2_platform-support-windows
• elasticsearch-periodic-platform-support #5632 / windows-2022_checkpart2_platform-support-windows
• elasticsearch-periodic #5643 / adoptopenjdk8_java-matrix
• elasticsearch-periodic #5643 / adoptopenjdk8_java-matrix
• elasticsearch-periodic #5643 / adoptopenjdk11_java-matrix
• elasticsearch-periodic #5643 / adoptopenjdk11_java-matrix

Reproduction Line:

./gradlew ':x-pack:plugin:sql:qa:server:security:without-ssl:javaRestTest' --tests "org.elasticsearch.xpack.sql.qa.security.JdbcSqlSpecIT" -Dtests.method="test {datetime.testCurrentTimestampYear}" -Dtests.seed=1D072A7F82272BFE -Dtests.locale=ar-SD -Dtests.timezone=US/Mountain -Druntime.java=11

Applicable branches:
7.17

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.lang.AssertionError: Different result for column [result], entry [1] expected:<2024> but was:<2025>

Issue Reasons:

• [7.17] 2 consecutive failures in test test {datetime.testCurrentTimestampYear}
• [7.17] 2 consecutive failures in step sles-12_platform-support-unix
• [7.17] 2 consecutive failures in step adoptopenjdk11_java-matrix
• [7.17] 33 failures in test test {datetime.testCurrentTimestampYear} (15.6% fail rate in 212 executions)
• [7.17] 2 failures in step sles-12_platform-support-unix (50.0% fail rate in 4 executions)
• [7.17] 2 failures in step adoptopenjdk11_java-matrix (66.7% fail rate in 3 executions)
• [7.17] 3 failures in pipeline elasticsearch-periodic (75.0% fail rate in 4 executions)
• [7.17] 2 failures in pipeline elasticsearch-periodic-platform-support (50.0% fail rate in 4 executions)

Note:
This issue was created using new test triage automation. Please report issues or feedback to es-delivery.

[elasticsearchmachine]

Pinging @elastic/es-delivery (Team:Delivery)

[elasticsearchmachine]

Pinging @elastic/es-analytical-engine (Team:Analytics)

[fang-xing-esql]

This looks like a reoccurrence of an old issue , and the fix to the tests was not backported to 7.x, it is a pretty old PR from 5 years ago. @bpintea do you still recall the context of that PR, I wonder what is the best way to deal with it? Should we backport it to 7.17 or just mark this test as ignored/removed on 7.17?