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/rest-api/common-options/line_125} failing #121338

Open
elasticsearchmachine opened this issue Jan 30, 2025 · 3 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 Jan 30, 2025

Build Scans:

Reproduction Line:

./gradlew ":docs:yamlRestTest" --tests "org.elasticsearch.smoketest.DocsClientYamlTestSuiteIT.test {yaml=reference/rest-api/common-options/line_125}" -Dtests.seed=E3BBFA5DB18C0E4A -Dtests.locale=tk-Latn-TM -Dtests.timezone=America/Rankin_Inlet -Druntime.java=23

Applicable branches:
8.18

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.lang.AssertionError: Failure at [reference/rest-api/common-options:123]: Expected a map containing
routing_table: a map containing
        indices: a map containing
  my-index-000001: a map containing
             shards: a map containing
                    0: a list containing
                      0: a map containing
                    state: "STARTED"
                      1: a map containing
                    state: "UNASSIGNED"
      .security-7: <unexpected> but was <{shards={0=[{state=STARTED}]}}>

Issue Reasons:

  • [8.18] 2 failures in test test {yaml=reference/rest-api/common-options/line_125} (1.5% fail rate in 135 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 Jan 30, 2025
elasticsearchmachine added a commit that referenced this issue Jan 30, 2025
@elasticsearchmachine
Copy link
Collaborator Author

This has been muted on branch main

Mute Reasons:

  • [main] 3 failures in test test {yaml=reference/rest-api/common-options/line_125} (0.3% fail rate in 928 executions)
  • [main] 2 failures in step part-1 (0.5% fail rate in 415 executions)
  • [main] 2 failures in pipeline elasticsearch-pull-request (0.4% fail rate in 448 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 Jan 30, 2025
@elasticsearchmachine
Copy link
Collaborator Author

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

@slobodanadamovic slobodanadamovic self-assigned this Jan 30, 2025
smalyshev pushed a commit to smalyshev/elasticsearch that referenced this issue Jan 30, 2025
saikatsarkar056 pushed a commit to saikatsarkar056/elasticsearch that referenced this issue Jan 31, 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 Jan 31, 2025
@elasticsearchmachine
Copy link
Collaborator Author

This has been muted on branch 8.18

Mute Reasons:

  • [8.18] 2 failures in test test {yaml=reference/rest-api/common-options/line_125} (1.5% fail rate in 135 executions)

Build Scans:

elasticsearchmachine added a commit that referenced this issue Mar 3, 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