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/spaces_only/tests/alerting/delete·ts - alerting api integration spaces only Alerting delete should handle delete alert request appropriately #110827

Closed
kibanamachine opened this issue Sep 1, 2021 · 3 comments · Fixed by #111366
Closed

Failing test: X-Pack Alerting API Integration Tests.x-pack/test/alerting_api_integration/spaces_only/tests/alerting/delete·ts - alerting api integration spaces only Alerting delete should handle delete alert request appropriately #110827

kibanamachine opened this issue Sep 1, 2021 · 3 comments · Fixed by #111366
Labels
failed-test A test failure on a tracked branch, potentially flaky-test Feature:Alerting/RulesFramework Issues related to the Alerting Rules Framework impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. loe:small Small Level of Effort 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/15/kibana/node_modules/supertest/lib/test.js:268:12)
    at Test._assertFunction (/dev/shm/workspace/parallel/15/kibana/node_modules/supertest/lib/test.js:283:11)
    at Test.assert (/dev/shm/workspace/parallel/15/kibana/node_modules/supertest/lib/test.js:173:18)
    at assert (/dev/shm/workspace/parallel/15/kibana/node_modules/supertest/lib/test.js:131:12)
    at /dev/shm/workspace/parallel/15/kibana/node_modules/supertest/lib/test.js:128:5
    at Test.Request.callback (/dev/shm/workspace/parallel/15/kibana/node_modules/supertest/node_modules/superagent/lib/node/index.js:718:3)
    at /dev/shm/workspace/parallel/15/kibana/node_modules/supertest/node_modules/superagent/lib/node/index.js:906:18
    at IncomingMessage.<anonymous> (/dev/shm/workspace/parallel/15/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 1, 2021
@botelastic botelastic bot added the needs-team Issues missing a team label label Sep 1, 2021
@mistic mistic added the Team:Security Team focused on: Auth, Users, Roles, Spaces, Audit Logging, and more! label Sep 1, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-security (Team:Security)

@botelastic botelastic bot removed the needs-team Issues missing a team label label Sep 1, 2021
@azasypkin azasypkin added Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) and removed Team:Security Team focused on: Auth, Users, Roles, Spaces, Audit Logging, and more! labels Sep 1, 2021
@elasticmachine
Copy link
Contributor

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

@spalger
Copy link
Contributor

spalger commented Sep 1, 2021 •
edited
Loading

Only two failures in the last 30 days, one in a PR, monitoring for now.

@gmmorris gmmorris added the Feature:Alerting/RulesFramework Issues related to the Alerting Rules Framework label Sep 2, 2021
@ymao1 ymao1 mentioned this issue Sep 7, 2021
Merged
@mikecote mikecote mentioned this issue Sep 7, 2021
Closed
@exalate-issue-sync exalate-issue-sync bot added impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. loe:small Small Level of Effort labels Sep 29, 2021
@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/RulesFramework Issues related to the Alerting Rules Framework impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. loe:small Small Level of Effort 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.

[Alerting] Fixing flaky tests ymao1/kibana
7 participants
@gmmorris @kobelb @spalger @azasypkin @mistic @elasticmachine @kibanamachine