Skip to content
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

[CI] DataStreamsClientYamlTestSuiteIT test {p0=data_stream/200_rollover_failure_store/Rolling over a failure store on a data stream without the failure store enabled should work} failing #110051

Closed
elasticsearchmachine opened this issue Jun 21, 2024 · 2 comments · Fixed by #110058
Assignees
Labels
:Data Management/Data streams Data streams and their lifecycles 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

Build Scans:

Reproduction Line:

./gradlew ':modules:data-streams:yamlRestTest' --tests "org.elasticsearch.datastreams.DataStreamsClientYamlTestSuiteIT.test {p0=data_stream/200_rollover_failure_store/Rolling over a failure store on a data stream without the failure store enabled should work}" -Dtests.seed=C90957F275DB1936 -Dtests.locale=ar-OM -Dtests.timezone=America/Santiago -Druntime.java=22

Applicable branches:
main

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.lang.AssertionError: Failure at [data_stream/200_rollover_failure_store:417]: got unexpected warning header [
	299 Elasticsearch-8.15.0-97a7b83efe8d1814edd83616b1475359770dfa31 "index template [my-other-template] has index patterns [other-data-*] matching patterns from existing older templates [global] with patterns (global => [*]); this template [my-other-template] will take precedence during new index creation"
]

Mute Reasons:

  • [main] 6 failures in test test {p0=data_stream/200_rollover_failure_store/Rolling over a failure store on a data stream without the failure store enabled should work} (1.9% fail rate)
  • [main] 1.9% failure rate in test test {p0=data_stream/200_rollover_failure_store/Rolling over a failure store on a data stream without the failure store enabled should work} (1.9% fail rate)
  • [main] 1.5% failure rate in step part-1 (1.5% fail rate)
  • [main] 1.5% failure rate in pipeline elasticsearch-pull-request (1.5% fail rate)

Note:
This issue was created using new, in-development muting automation. Please mind any issues.

@elasticsearchmachine elasticsearchmachine added :Data Management/Data streams Data streams and their lifecycles >test-failure Triaged test failures from CI labels Jun 21, 2024
@elasticsearchmachine
Copy link
Collaborator Author

This has been muted on branch main

Mute Reasons:

  • [main] 6 failures in test test {p0=data_stream/200_rollover_failure_store/Rolling over a failure store on a data stream without the failure store enabled should work} (1.9% fail rate)
  • [main] 1.9% failure rate in test test {p0=data_stream/200_rollover_failure_store/Rolling over a failure store on a data stream without the failure store enabled should work} (1.9% fail rate)
  • [main] 1.5% failure rate in step part-1 (1.5% fail rate)
  • [main] 1.5% failure rate in pipeline elasticsearch-pull-request (1.5% fail rate)

Build Scans:

elasticsearchmachine added a commit that referenced this issue Jun 21, 2024
…est {p0=data_stream/200_rollover_failure_store/Rolling over a failure store on a data stream without the failure store enabled should work} #110051
@elasticsearchmachine elasticsearchmachine added Team:Data Management Meta label for data/management team needs:risk Requires assignment of a risk label (low, medium, blocker) labels Jun 21, 2024
@elasticsearchmachine
Copy link
Collaborator Author

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

@nielsbauman nielsbauman self-assigned this Jun 21, 2024
@nielsbauman nielsbauman 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 Jun 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Data Management/Data streams Data streams and their lifecycles 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

Successfully merging a pull request may close this issue.

2 participants