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/snapshot-restore/apis/get-snapshot-api/line_751} failing #121345

Open
elasticsearchmachine opened this issue Jan 30, 2025 · 3 comments · May be fixed by #124684
Assignees
Labels
low-risk An open issue or test failure that is a low risk to future releases :Security/Security Security issues without another label Team:Security Meta label for security team >test-failure Triaged test failures from CI

Comments

@elasticsearchmachine
Copy link
Collaborator

Build Scans:

Reproduction Line:

./gradlew ":docs:yamlRestTest" --tests "org.elasticsearch.smoketest.DocsClientYamlTestSuiteIT.test {yaml=reference/snapshot-restore/apis/get-snapshot-api/line_751}" -Dtests.seed=421819A6F0A1867B -Dtests.locale=mas -Dtests.timezone=Etc/Universal -Druntime.java=23

Applicable branches:
main

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.lang.AssertionError: Failure at [reference/snapshot-restore/apis/get-snapshot-api:431]: Expected a map containing
       snapshots: a list containing
                 0: a map containing
            failures: an empty list
include_global_state: <true>
            end_time: "2025-01-30T21:19:08.430Z"
  duration_in_millis: <0>
          version_id: <9009000>
          repository: "my_repository"
                uuid: "nBD4NjQFSVuUx3InCZRtDQ"
             version: "9.0.0"
          start_time: "2025-01-30T21:19:08.430Z"
              shards: a map containing
                 total: expected <0> but was <1>
                failed: <0>
            successful: expected <0> but was <1>
             indices: an empty list
                     0: <unexpected> but was ".security-7"
      feature_states: an empty list
                     0: <unexpected> but was <{feature_name=security, indices=[.security-7]}>
start_time_in_millis: <1738271948430L>
        data_streams: an empty list
       
[truncated]

Issue Reasons:

  • [main] 2 failures in test test {yaml=reference/snapshot-restore/apis/get-snapshot-api/line_751} (0.3% fail rate in 611 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
Copy link
Collaborator Author

This has been muted on branch main

Mute Reasons:

  • [main] 2 failures in test test {yaml=reference/snapshot-restore/apis/get-snapshot-api/line_751} (0.3% fail rate in 611 executions)

Build Scans:

elasticsearchmachine added a commit that referenced this issue Jan 30, 2025
…=reference/snapshot-restore/apis/get-snapshot-api/line_751} #121345
@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)

smalyshev pushed a commit to smalyshev/elasticsearch that referenced this issue Jan 30, 2025
…=reference/snapshot-restore/apis/get-snapshot-api/line_751} elastic#121345
saikatsarkar056 pushed a commit to saikatsarkar056/elasticsearch that referenced this issue Jan 31, 2025
…=reference/snapshot-restore/apis/get-snapshot-api/line_751} elastic#121345
bpintea pushed a commit to bpintea/elasticsearch that referenced this issue Jan 31, 2025
…=reference/snapshot-restore/apis/get-snapshot-api/line_751} elastic#121345
@slobodanadamovic slobodanadamovic self-assigned this Feb 3, 2025
@slobodanadamovic slobodanadamovic added :Security/Security Security issues without another label Team:Security Meta label for security team low-risk An open issue or test failure that is a low risk to future releases and removed :Delivery/Build Build or test infrastructure Team:Delivery Meta label for Delivery team needs:risk Requires assignment of a risk label (low, medium, blocker) labels Feb 3, 2025
@elasticsearchmachine
Copy link
Collaborator Author

Pinging @elastic/es-security (Team:Security)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
low-risk An open issue or test failure that is a low risk to future releases :Security/Security Security issues without another label Team:Security Meta label for security team >test-failure Triaged test failures from CI
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants