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/get_alert_instance_summary·ts - alerting api integration security and spaces enabled Alerts alerts getAlertInstanceSummary "after each" hook for "should handle getAlertInstanceSummary alert request appropriately" #111702

Open
kibanamachine opened this issue Sep 9, 2021 · 2 comments
Open

Failing test: X-Pack Alerting API Integration Tests.x-pack/test/alerting_api_integration/security_and_spaces/tests/alerting/get_alert_instance_summary·ts - alerting api integration security and spaces enabled Alerts alerts getAlertInstanceSummary "after each" hook for "should handle getAlertInstanceSummary alert request appropriately" #111702

kibanamachine opened this issue Sep 9, 2021 · 2 comments
Labels
failed-test A test failure on a tracked branch, potentially flaky-test Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@kibanamachine
Copy link
Contributor

A test failed on a tracked branch

Error: expected 204 "No Content", got 409 "Conflict"
    at Test._assertStatus (/dev/shm/workspace/parallel/21/kibana/node_modules/supertest/lib/test.js:268:12)
    at Test._assertFunction (/dev/shm/workspace/parallel/21/kibana/node_modules/supertest/lib/test.js:283:11)
    at Test.assert (/dev/shm/workspace/parallel/21/kibana/node_modules/supertest/lib/test.js:173:18)
    at assert (/dev/shm/workspace/parallel/21/kibana/node_modules/supertest/lib/test.js:131:12)
    at /dev/shm/workspace/parallel/21/kibana/node_modules/supertest/lib/test.js:128:5
    at Test.Request.callback (/dev/shm/workspace/parallel/21/kibana/node_modules/supertest/node_modules/superagent/lib/node/index.js:718:3)
    at /dev/shm/workspace/parallel/21/kibana/node_modules/supertest/node_modules/superagent/lib/node/index.js:906:18
    at IncomingMessage.<anonymous> (/dev/shm/workspace/parallel/21/kibana/node_modules/supertest/node_modules/superagent/lib/node/parsers/json.js:19:7)
    at endReadableNT (internal/streams/readable.js:1317:12)
    at processTicksAndRejections (internal/process/task_queues.js:82:21)

First failure: Jenkins Build
@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label Sep 9, 2021
@botelastic botelastic bot added the needs-team Issues missing a team label label Sep 9, 2021
@dmlemeshko dmlemeshko added the Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) label Sep 10, 2021
@elasticmachine
Copy link
Contributor

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

@botelastic botelastic bot removed the needs-team Issues missing a team label label Sep 10, 2021
@ymao1
Copy link
Contributor

ymao1 commented Sep 10, 2021

This test failure occurred 09/09 at 6:02AM EDT. I merged this PR to fix the 204/409 errors on 09/09 at 9:48AM EDT, so if we don't see any more flaky tests past that time, I think we can close this issue.

@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
No one assigned
Labels
failed-test A test failure on a tracked branch, potentially flaky-test Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@gmmorris @kobelb @dmlemeshko @ymao1 @elasticmachine @kibanamachine