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.

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/alert_create_flyout·ts - Actions and Triggers app create alert should create an alert with actions in multiple groups #89397

Open
kibanamachine opened this issue Jan 27, 2021 · 9 comments · Fixed by #123878
Assignees
Labels
failed-test A test failure on a tracked branch, potentially flaky-test Feature:Alerting/RulesManagement Issues related to the Rules Management UX Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@kibanamachine
Copy link
Contributor

kibanamachine commented Jan 27, 2021

A test failed on a tracked branch

Error: expected [] to sort of equal [ { name: 'eecce0ac8785446584745ce38e57e6ef',
    tagsText: '',
    alertType: 'Always Firing',
    interval: '1m' } ]
    at Assertion.assert (/dev/shm/workspace/parallel/17/kibana/packages/kbn-expect/expect.js:100:11)
    at Assertion.eql (/dev/shm/workspace/parallel/17/kibana/packages/kbn-expect/expect.js:244:8)
    at Context.<anonymous> (test/functional_with_es_ssl/apps/triggers_actions_ui/alert_create_flyout.ts:161:41)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
    at Object.apply (/dev/shm/workspace/parallel/17/kibana/packages/kbn-test/src/functional_test_runner/lib/mocha/wrap_function.js:73:16) {
  actual: '[]',
  expected: '[\n' +
    '  {\n' +
    '    "alertType": "Always Firing"\n' +
    '    "interval": "1m"\n' +
    '    "name": "eecce0ac8785446584745ce38e57e6ef"\n' +
    '    "tagsText": ""\n' +
    '  }\n' +
    ']',
  showDiff: true
}

First failure: Jenkins Build

@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label Jan 27, 2021
@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@mistic mistic added the Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) label Nov 5, 2021
@elasticmachine
Copy link
Contributor

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

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - 8.0

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - 8.0

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@brianseeders
Copy link
Contributor

brianseeders commented Nov 6, 2021

Skipped

main: 3fc3f36
8.0: e6f391c
7.16: c884f81

brianseeders added a commit that referenced this issue Nov 6, 2021
brianseeders added a commit that referenced this issue Nov 6, 2021
@gmmorris gmmorris added the Feature:Alerting/RulesManagement Issues related to the Rules Management UX label Nov 8, 2021
@kibanamachine
Copy link
Contributor Author

New failure: CI Build - 7.16

tylersmalley pushed a commit that referenced this issue Nov 10, 2021
@kibanamachine
Copy link
Contributor Author

New failure: CI Build - 7.16

Repository owner moved this from In Progress to Done in AppEx: ResponseOps - Rules & Alerts Management Jan 28, 2022
@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
@kibanamachine kibanamachine reopened this Jul 5, 2022
@kibanamachine
Copy link
Contributor Author

New failure: CI Build - 8.3

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:Alerting/RulesManagement Issues related to the Rules Management UX Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
No open projects
Development

Successfully merging a pull request may close this issue.

7 participants