Skip to content

[CI] DateUtilsTests testTimezoneIds failing #120630

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.

Sign up for GitHub

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

Jump to bottom
Open
elasticsearchmachine opened this issue Jan 22, 2025 · 1 comment
Open

[CI] DateUtilsTests testTimezoneIds failing #120630

elasticsearchmachine opened this issue Jan 22, 2025 · 1 comment
Assignees
@mosche
Labels
:Core/Infra/Core Core issues without another label low-risk An open issue or test failure that is a low risk to future releases Team:Core/Infra Meta label for core/infra team >test-failure Triaged test failures from CI

Comments

@elasticsearchmachine
Copy link
Collaborator

elasticsearchmachine commented Jan 22, 2025 •
edited
Loading

Build Scans:

Reproduction Line:

./gradlew ':server:test' --tests "org.elasticsearch.common.time.DateUtilsTests.testTimezoneIds" -Dtests.seed=981DA435DCB65EE -Dtests.locale=es-ES -Dtests.timezone=Pacific/Honolulu -Druntime.java=8

Applicable branches:
7.17

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.lang.AssertionError: WET
Expected: <0>
     but: was <3600000>

Issue Reasons:

  • [7.17] 3 consecutive failures in test testTimezoneIds
  • [7.17] 22 consecutive failures in step zulu8_java-matrix
  • [7.17] 22 consecutive failures in step corretto11_java-matrix
  • [7.17] 22 consecutive failures in step openjdk23_java-matrix
  • [7.17] 21 consecutive failures in step adoptopenjdk11_java-matrix
  • [7.17] 21 consecutive failures in step zulu11_java-matrix
  • [7.17] 108 failures in test testTimezoneIds (11.3% fail rate in 952 executions)
  • [7.17] 22 failures in step zulu8_java-matrix (100.0% fail rate in 22 executions)
  • [7.17] 22 failures in step corretto11_java-matrix (100.0% fail rate in 22 executions)
  • [7.17] 22 failures in step openjdk23_java-matrix (100.0% fail rate in 22 executions)
  • [7.17] 21 failures in step adoptopenjdk11_java-matrix (100.0% fail rate in 21 executions)
  • [7.17] 21 failures in step zulu11_java-matrix (100.0% fail rate in 21 executions)
  • [7.17] 22 failures in pipeline elasticsearch-periodic (100.0% fail rate in 22 executions)

Note:
This issue was created using new test triage automation. Please report issues or feedback to es-delivery.
@elasticsearchmachine elasticsearchmachine added :Core/Infra/Core Core issues without another label >test-failure Triaged test failures from CI Team:Core/Infra Meta label for core/infra team needs:risk Requires assignment of a risk label (low, medium, blocker) labels Jan 22, 2025
@elasticsearchmachine
Copy link
Collaborator Author

Pinging @elastic/es-core-infra (Team:Core/Infra)

@thecoop thecoop self-assigned this Jan 22, 2025
@thecoop thecoop added low-risk An open issue or test failure that is a low risk to future releases and removed needs:risk Requires assignment of a risk label (low, medium, blocker) labels Jan 22, 2025
@thecoop thecoop mentioned this issue Jan 22, 2025
Merged
@arpadkiraly arpadkiraly assigned mosche and unassigned thecoop Apr 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mosche mosche

Labels
:Core/Infra/Core Core issues without another label low-risk An open issue or test failure that is a low risk to future releases Team:Core/Infra Meta label for core/infra team >test-failure Triaged test failures from CI
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@mosche @thecoop @elasticsearchmachine