Skip to content

[CI] DateProcessorTests testJavaPatternDefaultYear failing #119391

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

Closed
elasticsearchmachine opened this issue Dec 31, 2024 · 4 comments
Closed

[CI] DateProcessorTests testJavaPatternDefaultYear failing #119391

elasticsearchmachine opened this issue Dec 31, 2024 · 4 comments
Assignees
Labels
:Data Management/Ingest Node Execution or management of Ingest Pipelines including GeoIP low-risk An open issue or test failure that is a low risk to future releases Team:Data Management Meta label for data/management team >test-failure Triaged test failures from CI

Comments

@elasticsearchmachine
Copy link
Collaborator

elasticsearchmachine commented Dec 31, 2024

Build Scans:

Reproduction Line:

./gradlew ":modules:ingest-common:test" --tests "org.elasticsearch.ingest.common.DateProcessorTests.testJavaPatternDefaultYear" -Dtests.seed=BC4829F6371A460A -Dtests.locale=ga-GB -Dtests.timezone=America/North_Dakota/Center -Druntime.java=23

Applicable branches:
8.x

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.lang.AssertionError: 
Expected: "2024-06-12T00:00:00.000+02:00"
     but: was "2025-06-12T00:00:00.000+02:00"

Issue Reasons:

  • [8.x] 2 consecutive failures in step encryption-at-rest
  • [8.x] 2 consecutive failures in step opensuse-leap-15_platform-support-unix
  • [8.x] 2 consecutive failures in step part-1
  • [8.x] 2 consecutive failures in pipeline elasticsearch-pull-request
  • [8.x] 23 failures in test testJavaPatternDefaultYear (25.6% fail rate in 90 executions)
  • [8.x] 2 failures in step encryption-at-rest (66.7% fail rate in 3 executions)
  • [8.x] 2 failures in step opensuse-leap-15_platform-support-unix (66.7% fail rate in 3 executions)
  • [8.x] 2 failures in step part-1 (40.0% fail rate in 5 executions)
  • [8.x] 3 failures in pipeline elasticsearch-periodic (100.0% fail rate in 3 executions)
  • [8.x] 3 failures in pipeline elasticsearch-periodic-platform-support (100.0% fail rate in 3 executions)
  • [8.x] 2 failures in pipeline elasticsearch-pull-request (40.0% fail rate in 5 executions)

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

@elasticsearchmachine elasticsearchmachine added :Data Management/Ingest Node Execution or management of Ingest Pipelines including GeoIP >test-failure Triaged test failures from CI Team:Data Management Meta label for data/management team needs:risk Requires assignment of a risk label (low, medium, blocker) labels Dec 31, 2024
@elasticsearchmachine
Copy link
Collaborator Author

Pinging @elastic/es-data-management (Team:Data Management)

@elasticsearchmachine
Copy link
Collaborator Author

This has been muted on branch 8.16

Mute Reasons:

  • [8.16] 2 failures in test testJavaPatternDefaultYear (1.9% fail rate in 105 executions)
  • [8.16] 2 failures in step part1 (40.0% fail rate in 5 executions)
  • [8.16] 2 failures in pipeline elasticsearch-intake (40.0% fail rate in 5 executions)

Build Scans:

@dakrone dakrone 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 2, 2025
@samxbr
Copy link
Contributor

samxbr commented Apr 23, 2025

Should have been closed by #122577, not sure why it was not closed.

@samxbr samxbr closed this as completed Apr 23, 2025
@nielsbauman
Copy link
Contributor

Github only closes issues from PRs when they target the default branch (i.e. main).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Data Management/Ingest Node Execution or management of Ingest Pipelines including GeoIP low-risk An open issue or test failure that is a low risk to future releases Team:Data Management Meta label for data/management team >test-failure Triaged test failures from CI
Projects
None yet
Development

No branches or pull requests

4 participants