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] DocsClientYamlTestSuiteIT test {yaml=reference/alias/line_260} failing #122343

Open
elasticsearchmachine opened this issue Feb 12, 2025 · 2 comments · May be fixed by #124684
Open

[CI] DocsClientYamlTestSuiteIT test {yaml=reference/alias/line_260} failing #122343

elasticsearchmachine opened this issue Feb 12, 2025 · 2 comments · May be fixed by #124684
Assignees
Labels
:Delivery/Build Build or test infrastructure low-risk An open issue or test failure that is a low risk to future releases Team:Delivery Meta label for Delivery team >test-failure Triaged test failures from CI

Comments

@elasticsearchmachine
Copy link
Collaborator

elasticsearchmachine commented Feb 12, 2025

Build Scans:

Reproduction Line:

./gradlew ":docs:yamlRestTest" --tests "org.elasticsearch.smoketest.DocsClientYamlTestSuiteIT.test {yaml=reference/alias/line_260}" -Dtests.seed=90BC31A30A172D0B -Dtests.locale=fr-RE -Dtests.timezone=Asia/Riyadh -Druntime.java=24

Applicable branches:
8.18

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.lang.AssertionError: Failure at [reference/alias:282]: got unexpected warning header [
	299 Elasticsearch-8.18.0-2a82161670df2dd2fcb53175a7c63ea7e885078d "this request accesses system indices: [.security-7], but in a future major version, direct access to system indices will be prevented by default"
]

Issue Reasons:

  • [8.18] 2 failures in test test {yaml=reference/alias/line_260} (1.2% fail rate in 167 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 Feb 12, 2025
@elasticsearchmachine
Copy link
Collaborator Author

This has been muted on branch main

Mute Reasons:

  • [main] 2 failures in test test {yaml=reference/alias/line_260} (0.4% fail rate in 498 executions)

Build Scans:

@elasticsearchmachine elasticsearchmachine added Team:Delivery Meta label for Delivery team needs:risk Requires assignment of a risk label (low, medium, blocker) labels Feb 12, 2025
@elasticsearchmachine
Copy link
Collaborator Author

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

@slobodanadamovic slobodanadamovic self-assigned this Feb 12, 2025
@slobodanadamovic slobodanadamovic 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 Feb 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Delivery/Build Build or test infrastructure low-risk An open issue or test failure that is a low risk to future releases Team:Delivery Meta label for Delivery team >test-failure Triaged test failures from CI
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants