-
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: Chrome X-Pack UI Functional Tests.x-pack/test/functional_with_es_ssl/apps/triggers_actions_ui/alerts·ts - Actions and Triggers app alerts should delete all selection #77401
Failing test: Chrome X-Pack UI Functional Tests.x-pack/test/functional_with_es_ssl/apps/triggers_actions_ui/alerts·ts - Actions and Triggers app alerts should delete all selection #77401
Comments
Pinging @elastic/kibana-test-triage (failed-test) |
Pinging @elastic/kibana-alerting-services (Team:Alerting Services) |
New failure: Jenkins Build |
@gmmorris It looks like this might be caused by an unnecessary timeout being set here:
|
My hunch is revealing my bias against people customizing the default timeouts without explanation, but based on the failure pattern in the last 2 weeks seems to indicate this was caused by something else: 6 failures across master and PRs, there doesn't seem to be a clear indicator which PR might have caused an issue causing deletion to be a little slower on CI, but removing the timeout will probably fix it. Skipping in master and 7.x as a precaution |
Sorry Spence, didn't mean to ignore you... missed the notification... |
This test just failed on a snapshot build, and it has failed 11 PRs in the last 7 days since it was unskipped. Sorry @YulNaumenko but I'm skipping again |
New failure: Jenkins Build |
New failure: Jenkins Build |
|
According to the log, that is weird that we have such a big number of alerts to delete - should be only 2 if all the tests have implemented clean up logic.. |
That suggests we've introduced some new tests that create alerts that haven't been removed by the objectRemover 🤔 |
New failure: Jenkins Build |
A test failed on a tracked branch
First failure: Jenkins Build
The text was updated successfully, but these errors were encountered: