-
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/details·ts - Actions and Triggers app Alert Details Alert Instances renders the active alert instances #57426
Failing test: Chrome X-Pack UI Functional Tests.x-pack/test/functional_with_es_ssl/apps/triggers_actions_ui/details·ts - Actions and Triggers app Alert Details Alert Instances renders the active alert instances #57426
Comments
Pinging @elastic/kibana-test-triage (failed-test) |
Pinging @elastic/kibana-alerting-services (Team:Alerting Services) |
New failure: Jenkins Build |
New failure: Jenkins Build |
New failure: Jenkins Build |
New failure: Jenkins Build |
1 similar comment
New failure: Jenkins Build |
New failure: Jenkins Build |
New failure: Jenkins Build |
New failure: Jenkins Build |
New failure: Jenkins Build |
1 similar comment
New failure: Jenkins Build |
New failure: Jenkins Build |
Should be addressed now as backport has finally made it through CI |
New failure: Jenkins Build |
New failure: Jenkins Build |
New failure: Jenkins Build |
New failure: Jenkins Build |
New failure: Jenkins Build |
New failure: Jenkins Build |
New failure: Jenkins Build |
* master: Added `defaultActionMessage` to index threshold alert UI type definition (elastic#80936) [ILM] Migrate Delete phase and name field to Form Lib (elastic#82834) skip flaky suite (elastic#57426) [Alerting] adds an Run When field in the alert flyout to assign the action to an Action Group (elastic#82472) [APM] Expose APM event client as part of plugin contract (elastic#82724) [Logs UI] Fix errors during navigation (elastic#78319) Enable send to background in TSVB (elastic#82835) SavedObjects search_dsl: add match_phrase_prefix clauses when using prefix search (elastic#82693) [Ingest Manager] Unify install* under installPackage (elastic#82916)
…e-details-overlay * 'master' of github.com:elastic/kibana: (201 commits) Added `defaultActionMessage` to index threshold alert UI type definition (elastic#80936) [ILM] Migrate Delete phase and name field to Form Lib (elastic#82834) skip flaky suite (elastic#57426) [Alerting] adds an Run When field in the alert flyout to assign the action to an Action Group (elastic#82472) [APM] Expose APM event client as part of plugin contract (elastic#82724) [Logs UI] Fix errors during navigation (elastic#78319) Enable send to background in TSVB (elastic#82835) SavedObjects search_dsl: add match_phrase_prefix clauses when using prefix search (elastic#82693) [Ingest Manager] Unify install* under installPackage (elastic#82916) [Fleet] Make stream id unique in agent policy (elastic#82447) skip flaky suite (elastic#82915) skip flaky suite (elastic#75794) Copy `dateAsStringRt` to observability plugin (elastic#82839) [Maps] rename connected_components/map folder to mb_map (elastic#82897) [Security Solution] Fix EventsViewer DnD cypress tests (elastic#82619) [Security Solution] Adds logging and performance fan out API for threat/Indicator matching (elastic#82546) Implemented Alerting health status pusher by using task manager and status pooler for Kibana status plugins 'kibanahost/api/status' (elastic#79056) [APM] Adds new configuration 'xpack.apm.maxServiceEnvironments' (elastic#82090) Move single use function in line (elastic#82885) [ML] Add unsigned_long support to data frame analytics and anomaly detection (elastic#82636) ...
I ran this test that failed |
Hmm the failure reported was that it was off by a second on one of the array elements, way back here: #57426 (comment) Looks like the test is here: kibana/x-pack/test/functional_with_es_ssl/apps/triggers_actions_ui/details.ts Lines 393 to 400 in 208e86e
I'm guessing this may be a rounding difference on the millis from the Since rounding may end up affecting even the year (on New Year's Eve :-) ), if it is rounding, I think we'll need to do this test another way. Perhaps parse what the UI is returning, converting to a Date() object, to get the epoch millis value. Then do a compare of the times from the API with a few seconds of slop (eg, 10). I didn't look to see how the UI is actually calculating this value. Are they both the same? So we shouldn't be seeing the rounding error? Perhaps what's happening is there is some delay, and the alert got another chance to run, and it's a 1 sec interval so it caught the next one? If so, I think the change suggested above ^^^, taking into account some slop, should still be a safe fix. |
A test failed on a tracked branch
First failure: Jenkins Build
The text was updated successfully, but these errors were encountered: