-
Notifications
You must be signed in to change notification settings - Fork 25k
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
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
added
:Delivery/Build
Build or test infrastructure
>test-failure
Triaged test failures from CI
labels
Oct 28, 2024
This has been muted on branch main Mute Reasons:
Build Scans: |
elasticsearchmachine
added a commit
that referenced
this issue
Oct 28, 2024
…=reference/watcher/example-watches/example-watch-clusterstatus/line_137} #115809
elasticsearchmachine
added
Team:Delivery
Meta label for Delivery team
needs:risk
Requires assignment of a risk label (low, medium, blocker)
labels
Oct 28, 2024
Pinging @elastic/es-delivery (Team:Delivery) |
mark-vieira
added
:Data Management/Watcher
and removed
:Delivery/Build
Build or test infrastructure
labels
Oct 29, 2024
elasticsearchmachine
added
the
Team:Data Management
Meta label for data/management team
label
Oct 29, 2024
Pinging @elastic/es-data-management (Team:Data Management) |
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
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
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
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
Build Scans:
Reproduction Line:
Applicable branches:
main
Reproduces locally?:
N/A
Failure History:
See dashboard
Failure Message:
Issue Reasons:
Note:
This issue was created using new test triage automation. Please report issues or feedback to es-delivery.
The text was updated successfully, but these errors were encountered: