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: Jest Tests.x-pack/plugins/triggers_actions_ui/public/application/sections/rules_list/components - Rules list Bulk Delete should Bulk Delete #152521

Open
kibanamachine opened this issue Mar 1, 2023 · 4 comments
Open

Failing test: Jest Tests.x-pack/plugins/triggers_actions_ui/public/application/sections/rules_list/components - Rules list Bulk Delete should Bulk Delete #152521

kibanamachine opened this issue Mar 1, 2023 · 4 comments
Assignees
@guskovaue
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 Mar 1, 2023 •
edited
Loading

A test failed on a tracked branch

Error: thrown: "Exceeded timeout of 5000 ms for a test.
Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."
    at it (/var/lib/buildkite-agent/builds/kb-n2-4-spot-bc15970930868861/elastic/kibana-on-merge/kibana/x-pack/plugins/triggers_actions_ui/public/application/sections/rules_list/components/rules_list_bulk_delete.test.tsx:169:3)
    at _dispatchDescribe (/var/lib/buildkite-agent/builds/kb-n2-4-spot-bc15970930868861/elastic/kibana-on-merge/kibana/node_modules/jest-circus/build/index.js:91:26)
    at describe (/var/lib/buildkite-agent/builds/kb-n2-4-spot-bc15970930868861/elastic/kibana-on-merge/kibana/node_modules/jest-circus/build/index.js:55:5)
    at Object.describe (/var/lib/buildkite-agent/builds/kb-n2-4-spot-bc15970930868861/elastic/kibana-on-merge/kibana/x-pack/plugins/triggers_actions_ui/public/application/sections/rules_list/components/rules_list_bulk_delete.test.tsx:130:1)
    at Runtime._execModule (/var/lib/buildkite-agent/builds/kb-n2-4-spot-bc15970930868861/elastic/kibana-on-merge/kibana/node_modules/jest-runtime/build/index.js:1377:24)
    at Runtime._loadModule (/var/lib/buildkite-agent/builds/kb-n2-4-spot-bc15970930868861/elastic/kibana-on-merge/kibana/node_modules/jest-runtime/build/index.js:989:12)
    at Runtime.requireModule (/var/lib/buildkite-agent/builds/kb-n2-4-spot-bc15970930868861/elastic/kibana-on-merge/kibana/node_modules/jest-runtime/build/index.js:849:12)
    at jestAdapter (/var/lib/buildkite-agent/builds/kb-n2-4-spot-bc15970930868861/elastic/kibana-on-merge/kibana/node_modules/jest-circus/build/legacy-code-todo-rewrite/jestAdapter.js:77:13)
    at runTestInternal (/var/lib/buildkite-agent/builds/kb-n2-4-spot-bc15970930868861/elastic/kibana-on-merge/kibana/node_modules/jest-runner/build/runTest.js:367:16)
    at runTest (/var/lib/buildkite-agent/builds/kb-n2-4-spot-bc15970930868861/elastic/kibana-on-merge/kibana/node_modules/jest-runner/build/runTest.js:444:34)

First failure: CI Build - main
@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label Mar 1, 2023
@botelastic botelastic bot added the needs-team Issues missing a team label label Mar 1, 2023
@kibanamachine kibanamachine added the Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) label Mar 1, 2023
@elasticmachine
Copy link
Contributor

Pinging @elastic/response-ops (Team:ResponseOps)

@botelastic botelastic bot removed the needs-team Issues missing a team label label Mar 1, 2023
@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

jbudz added a commit that referenced this issue Mar 6, 2023
@jbudz
skip flaky suite (#152521)
04ca1dd
@jbudz
Copy link
Member

jbudz commented Mar 6, 2023

Skipped

main: 04ca1dd

bmorelli25 pushed a commit to bmorelli25/kibana that referenced this issue Mar 10, 2023
@jbudz @bmorelli25
skip flaky suite (elastic#152521)
5685803
@XavierM XavierM assigned XavierM and guskovaue and unassigned XavierM Mar 28, 2023
@XavierM
Copy link
Contributor

XavierM commented Mar 28, 2023

@guskovaue I think that you fix that by creating functional testing without using jest tests. We might need to do the same here.

@XavierM XavierM moved this from Awaiting Triage to Todo in AppEx: ResponseOps - Rules & Alerts Management Mar 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@guskovaue guskovaue

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
No open projects
AppEx: ResponseOps - Rules & Alerts Management
Status: Todo
Milestone
No milestone
Development

No branches or pull requests
5 participants
@XavierM @jbudz @elasticmachine @guskovaue @kibanamachine