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: X-Pack Alerting API Integration Tests.x-pack/test/alerting_api_integration/security_and_spaces/tests/alerting/alerts·ts - alerting api integration security and spaces enabled Alerting alerts space_1_all at space1 should unmute all instances when unmuting an alert #50079

Closed
kibanamachine opened this issue Nov 7, 2019 · 10 comments · Fixed by #50246
Closed

Failing test: X-Pack Alerting API Integration Tests.x-pack/test/alerting_api_integration/security_and_spaces/tests/alerting/alerts·ts - alerting api integration security and spaces enabled Alerting alerts space_1_all at space1 should unmute all instances when unmuting an alert #50079

kibanamachine opened this issue Nov 7, 2019 · 10 comments · Fixed by #50246
Assignees
@mikecote
Labels
failed-test A test failure on a tracked branch, potentially flaky-test Feature:Alerting skipped-test v7.7.0

Comments

@kibanamachine
Copy link
Contributor

kibanamachine commented Nov 7, 2019 •
edited
Loading

A test failed on a tracked branch

{ Error: expected 0 to sort of equal 1
    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.eql (test/alerting_api_integration/security_and_spaces/tests/alerting/alerts.ts:657:65)
    at process._tickCallback (internal/process/next_tick.js:68:7) actual: '0', expected: '1', showDiff: true }

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

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

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

spalger pushed a commit that referenced this issue Nov 8, 2019
skip flaky suite (#50079) (#50074) (#48709) (#50078)
78e9d93
spalger pushed a commit that referenced this issue Nov 8, 2019
skip flaky suite (#50079) (#50074) (#48709) (#50078)
1072c58 
(cherry picked from commit 78e9d93)
spalger pushed a commit that referenced this issue Nov 8, 2019
skip flaky suite (#50079) (#50074) (#48709) (#50078)
f661af1 
(cherry picked from commit 78e9d93)
@spalger
Copy link
Contributor

spalger commented Nov 8, 2019

Skipped

master: 78e9d93
7.x/7.6: 1072c58
7.5: f661af1

@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-stack-services (Team:Stack Services)

@mikecote mikecote mentioned this issue Nov 12, 2019
Merged
@kibanamachine kibanamachine reopened this Jan 7, 2020
@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@mikecote
Copy link
Contributor

Closing this as flakiness no longer seems to be an issue.

@mikecote mikecote self-assigned this Jan 30, 2020
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 Feature:Alerting skipped-test v7.7.0
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Increase alerting test stability and reduce flakiness mikecote/kibana
4 participants
@spalger @mikecote @elasticmachine @kibanamachine