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.

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

[CI] CoreWithMultipleProjectsClientYamlTestSuiteIT test {yaml=data_stream/150_tsdb/created the data stream} failing #124575

Open
elasticsearchmachine opened this issue Mar 11, 2025 · 2 comments
Open

[CI] CoreWithMultipleProjectsClientYamlTestSuiteIT test {yaml=data_stream/150_tsdb/created the data stream} failing #124575

elasticsearchmachine opened this issue Mar 11, 2025 · 2 comments
Labels
:Delivery/Build Build or test infrastructure needs:risk Requires assignment of a risk label (low, medium, blocker) Team:Delivery Meta label for Delivery team >test-failure Triaged test failures from CI

Comments

@elasticsearchmachine
Copy link
Collaborator

Build Scans:

Reproduction Line:

./gradlew ":x-pack:qa:multi-project:core-rest-tests-with-multiple-projects:yamlRestTest" --tests "org.elasticsearch.multiproject.test.CoreWithMultipleProjectsClientYamlTestSuiteIT.test {yaml=data_stream/150_tsdb/created the data stream}" -Dtests.seed=3667756CA22BBFD3 -Dtests.locale=sq-AL -Dtests.timezone=Africa/Bangui -Druntime.java=23

Applicable branches:
main

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.lang.AssertionError: Failure at [data_stream/150_tsdb:111]: 
Expected: "2021-04-29T00:00:00.000Z"
     but: was "2025-03-11T16:08:51.000Z"

Issue Reasons:

  • [main] 5 failures in test test {yaml=data_stream/150_tsdb/created the data stream} (0.8% fail rate in 617 executions)
  • [main] 4 failures in step part-2 (2.1% fail rate in 192 executions)
  • [main] 4 failures in pipeline elasticsearch-pull-request (2.1% fail rate in 192 executions)

Note:
This issue was created using new test triage automation. Please report issues or feedback to es-delivery.
@elasticsearchmachine elasticsearchmachine added :Delivery/Build Build or test infrastructure >test-failure Triaged test failures from CI labels Mar 11, 2025
@elasticsearchmachine
Copy link
Collaborator Author

This has been muted on branch main

Mute Reasons:

  • [main] 5 failures in test test {yaml=data_stream/150_tsdb/created the data stream} (0.8% fail rate in 617 executions)
  • [main] 4 failures in step part-2 (2.1% fail rate in 192 executions)
  • [main] 4 failures in pipeline elasticsearch-pull-request (2.1% fail rate in 192 executions)

Build Scans:

elasticsearchmachine added a commit that referenced this issue Mar 11, 2025
@elasticsearchmachine
Mute org.elasticsearch.multiproject.test.CoreWithMultipleProjectsClie…
2187c25 
…ntYamlTestSuiteIT test {yaml=data_stream/150_tsdb/created the data stream} #124575
@elasticsearchmachine elasticsearchmachine added Team:Delivery Meta label for Delivery team needs:risk Requires assignment of a risk label (low, medium, blocker) labels Mar 11, 2025
@elasticsearchmachine
Copy link
Collaborator Author

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
:Delivery/Build Build or test infrastructure needs:risk Requires assignment of a risk label (low, medium, blocker) Team:Delivery Meta label for Delivery team >test-failure Triaged test failures from CI
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@elasticsearchmachine