-
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: X-Pack Alerting API Integration Tests.x-pack/test/alerting_api_integration/security_and_spaces/tests/alerting/rbac_legacy·ts - alerting api integration security and spaces enabled Alerts legacy alerts alerts space_1_all_alerts_none_actions at space1 should schedule actions on legacy alerts #87010
Comments
Pinging @elastic/kibana-alerting-services (Team:Alerting Services) |
Looks like this has only failed in one unrelated PR and here in the last 30 days, making this not particularly flaky, so waiting and watching for now. |
We had another failure with https://kibana-ci.elastic.co/job/elastic+kibana+master/10822/, skips: |
…meline-component * 'master' of github.com:elastic/kibana: (955 commits) remove SameSite:None workaround (elastic#86994) URL encoding for URL drilldown (elastic#86902) [Security Solution] Fix few styling issues (elastic#87045) [APM] Custom links can still be created with a read only user. (elastic#87089) prevent double update (elastic#86794) Upgrade @hapi/hoek to revert hack introduced in hapi v20 upgrade (elastic#87113) [APM] Every time the new Header Icon is clicked it fetches data (elastic#87093) [APM] Add range query to service map trace walk (elastic#86631) [Discover] Deangularize navbar in context app (elastic#86353) skip "should schedule actions on legacy alerts" elastic#87010 🍾 update notice text for 2021 [logstash] remove "upgrade" functionality now that .logstash is a system index (elastic#87056) Enable prototype pollution protection in TSVB (elastic#85952) [Security Solution] add a consistent spelling of ES in Policy Response (elastic#87073) [SECURITY_SOLUTION][ENDPOINT] Delete Endpoint Policy List code (elastic#87063) Adds more URLs to the docs links service (elastic#86972) Add missing backticks in reporting-settings.asciidoc (elastic#77979) [test/functional_cors] 9000 is sometimes in use, make getPort random (elastic#87050) [Security Solution] Fix Timeline filter EuiSuperSelect styling (elastic#87033) [Lens] Fix duplicate suggestions on single-bucket charts (elastic#86996) ... # Conflicts: # x-pack/plugins/index_lifecycle_management/public/application/sections/edit_policy/components/index.ts
https://kibana-ci.elastic.co/job/elastic+kibana+master/10752/
https://kibana-ci.elastic.co/job/elastic+kibana+master/10822/
|
New failure: Jenkins Build |
|
I'm wondering if there is some odd chance that this has caught an error in our code - we've had a couple of reports of "legacy" alerts not running in the field, when we expected them to, but never determined what was causing that. The specific failure in this test is showing the same problem. Might be useful to spend a couple of minutes looking through the legacy RBAC stuff ... but I assume this is probably just a flaky test of some kind. |
I recently fixed another legacy rbac test failure #92549 where the root cause was a race condition in how the functional test runner loads and migrates from the esArchiver. This could be another flake caused by something similar. |
Looks like the previous failures in this test were a different issue (fixed by Mike), so I'd put money down on flaky test rather than functionality.... |
It's been a few weeks since the last flaky failure. I will go ahead and close this. |
New failure: Jenkins Build |
New failure: Jenkins Build |
|
Flakiness hasn't returned in a few weeks, closing for now. |
A test failed on a tracked branch
First failure: Jenkins Build
The text was updated successfully, but these errors were encountered: