-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Failing test: Jest Tests.x-pack/plugins/cases/public/components/case_view/components - EditTags cancels on cancel #175621
Labels
failed-test
A test failure on a tracked branch, potentially flaky-test
Feature:Cases
Cases feature
Team:ResponseOps
Label for the ResponseOps team (formerly the Cases and Alerting teams)
Comments
kibanamachine
added
the
failed-test
A test failure on a tracked branch, potentially flaky-test
label
Jan 25, 2024
kibanamachine
added
the
Team:ResponseOps
Label for the ResponseOps team (formerly the Cases and Alerting teams)
label
Jan 25, 2024
Pinging @elastic/response-ops (Team:ResponseOps) |
New failure: CI Build - main |
New failure: CI Build - main |
Skipped. main: bb3abc7 |
cnasikas
added
Feature:Cases
Cases feature
and removed
blocker
skipped-test
v8.13.0
labels
Jan 28, 2024
Pinging @elastic/response-ops-cases (Feature:Cases) |
CoenWarmer
pushed a commit
to CoenWarmer/kibana
that referenced
this issue
Feb 15, 2024
## Summary The tests started to be flaky recently: https://ops.kibana.dev/s/ci/app/dashboards#/view/cb7380fb-67fe-5c41-873d-003d1a407dad?_g=(filters:!(),refreshInterval:(pause:!t,value:0),time:(from:now-4w,to:now)) elastic#175618 elastic#175619 elastic#175621 elastic#175622 elastic#175623 elastic#175655
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
failed-test
A test failure on a tracked branch, potentially flaky-test
Feature:Cases
Cases feature
Team:ResponseOps
Label for the ResponseOps team (formerly the Cases and Alerting teams)
A test failed on a tracked branch
First failure: CI Build - main
The text was updated successfully, but these errors were encountered: