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/watcher/example-watches/example-watch-clusterstatus/line_137} failing #115809

Closed
elasticsearchmachine opened this issue Oct 28, 2024 · 4 comments · Fixed by #117354
Assignees
Labels
:Data Management/Watcher 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 ":docs:yamlRestTest" --tests "org.elasticsearch.smoketest.DocsClientYamlTestSuiteIT.test {yaml=reference/watcher/example-watches/example-watch-clusterstatus/line_137}" -Dtests.seed=451EC8FFC95CB241 -Dtests.locale=pa -Dtests.timezone=America/Yellowknife -Druntime.java=22

Applicable branches:
main

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

org.elasticsearch.client.WarningFailureException: method [DELETE], host [http://[::1]:39035], URI [*,-.ds-ilm-history-*,-.ds-.slm-history-*,-.ds-.watcher-history-*?expand_wildcards=open%2Cclosed%2Chidden], status line [HTTP/1.1 200 OK]
Warnings: [this request accesses system indices: [.triggered_watches], but in a future major version, direct access to system indices will be prevented by default]
{"acknowledged":true}

Issue Reasons:

  • [main] 2 failures in test test {yaml=reference/watcher/example-watches/example-watch-clusterstatus/line_137} (0.3% fail rate in 632 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 Oct 28, 2024
@elasticsearchmachine
Copy link
Collaborator Author

This has been muted on branch main

Mute Reasons:

  • [main] 2 failures in test test {yaml=reference/watcher/example-watches/example-watch-clusterstatus/line_137} (0.3% fail rate in 632 executions)

Build Scans:

elasticsearchmachine added a commit that referenced this issue Oct 28, 2024
…=reference/watcher/example-watches/example-watch-clusterstatus/line_137} #115809
@elasticsearchmachine elasticsearchmachine added Team:Delivery Meta label for Delivery team needs:risk Requires assignment of a risk label (low, medium, blocker) labels Oct 28, 2024
@elasticsearchmachine
Copy link
Collaborator Author

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

@mark-vieira mark-vieira added :Data Management/Watcher and removed :Delivery/Build Build or test infrastructure labels Oct 29, 2024
@elasticsearchmachine elasticsearchmachine added the Team:Data Management Meta label for data/management team label Oct 29, 2024
@elasticsearchmachine
Copy link
Collaborator Author

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

@elasticsearchmachine elasticsearchmachine removed the Team:Delivery Meta label for Delivery team label Oct 29, 2024
@dakrone dakrone 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 Oct 29, 2024
ioanatia pushed a commit to ioanatia/elasticsearch that referenced this issue Nov 4, 2024
…=reference/watcher/example-watches/example-watch-clusterstatus/line_137} elastic#115809
jfreden pushed a commit to jfreden/elasticsearch that referenced this issue Nov 4, 2024
…=reference/watcher/example-watches/example-watch-clusterstatus/line_137} elastic#115809
@lukewhiting
Copy link
Contributor

Looks like this is a re-occurrence of this known issue RE watches actually executing during test runs: #99517

I'll have a dig today and see if there's any solutions that can be put in place

@lukewhiting lukewhiting reopened this Nov 18, 2024
lukewhiting added a commit that referenced this issue Dec 4, 2024
…atches/example-watch-clusterstatus/line_137} failing - (#115809) (#117354)

* Ignore system index access errors in YAML test index cleanup method

* Remove test mute

* Swap the logic back as it was right the first time

* Resolve conflict with latest merge

* Move warning handler into it's own method to reduce nesting
lukewhiting added a commit to lukewhiting/elasticsearch that referenced this issue Dec 4, 2024
…atches/example-watch-clusterstatus/line_137} failing - (elastic#115809) (elastic#117354)

* Ignore system index access errors in YAML test index cleanup method

* Remove test mute

* Swap the logic back as it was right the first time

* Resolve conflict with latest merge

* Move warning handler into it's own method to reduce nesting

(cherry picked from commit cda2fe6)
lukewhiting added a commit to lukewhiting/elasticsearch that referenced this issue Dec 4, 2024
…atches/example-watch-clusterstatus/line_137} failing - (elastic#115809) (elastic#117354)

* Ignore system index access errors in YAML test index cleanup method

* Remove test mute

* Swap the logic back as it was right the first time

* Resolve conflict with latest merge

* Move warning handler into it's own method to reduce nesting

(cherry picked from commit cda2fe6)
elasticsearchmachine pushed a commit that referenced this issue Dec 4, 2024
…atches/example-watch-clusterstatus/line_137} failing - (#115809) (#117354) (#117972)

* Ignore system index access errors in YAML test index cleanup method

* Remove test mute

* Swap the logic back as it was right the first time

* Resolve conflict with latest merge

* Move warning handler into it's own method to reduce nesting

(cherry picked from commit cda2fe6)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment