Skip to content
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.

Sign up for GitHub

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

Jump to bottom

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 edit an alert #62494

Closed
kibanamachine opened this issue Apr 3, 2020 · 4 comments · Fixed by #62817
Closed

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 edit an alert #62494

kibanamachine opened this issue Apr 3, 2020 · 4 comments · Fixed by #62817
Assignees
@mikecote
Labels
failed-test A test failure on a tracked branch, potentially flaky-test Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@kibanamachine
Copy link
Contributor

kibanamachine commented Apr 3, 2020 •
edited
Loading

A test failed on a tracked branch

{ Error: expected 'Updated \'new alertChanged Alert Name\'' to sort of equal 'Updated \'Changed Alert Name\''
    at Assertion.assert (/dev/shm/workspace/kibana/packages/kbn-expect/expect.js:100:11)
    at Assertion.eql (/dev/shm/workspace/kibana/packages/kbn-expect/expect.js:244:8)
    at Context.it (test/functional_with_es_ssl/apps/triggers_actions_ui/alerts.ts:173:29)
    at process._tickCallback (internal/process/next_tick.js:68:7)
  actual: 'Updated \'new alertChanged Alert Name\'',
  expected: 'Updated \'Changed Alert Name\'',
  showDiff: true }

First failure: Jenkins Build
@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label Apr 3, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-test-triage (failed-test)

@spalger spalger added the Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) label Apr 3, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-alerting-services (Team:Alerting Services)

@spalger
Copy link
Contributor

spalger commented Apr 3, 2020

Similar pattern as #62472

image

Skipped by the same commits

master: 2b81552
7.x/7.8: 8501d11

@spalger spalger mentioned this issue Apr 3, 2020
Merged
@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@mikecote mikecote mentioned this issue Apr 7, 2020
Merged
@kobelb kobelb added the needs-team Issues missing a team label label Jan 31, 2022
@botelastic botelastic bot removed the needs-team Issues missing a team label label Jan 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mikecote mikecote

Labels
failed-test A test failure on a tracked branch, potentially flaky-test Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix alerting UI flaky tests mikecote/kibana
5 participants
@kobelb @spalger @mikecote @elasticmachine @kibanamachine