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: Jest Tests.x-pack/plugins/triggers_actions_ui/public/application/sections/alerts_table - AlertsTableState field browser should insert a new field as column when its not a default one #150790

Closed
kibanamachine opened this issue Feb 9, 2023 · 5 comments · Fixed by #162805
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 Feb 9, 2023

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-1fc47bc38e5c55bf/elastic/kibana-on-merge/kibana/x-pack/plugins/triggers_actions_ui/public/application/sections/alerts_table/alerts_table_state.test.tsx:345:5)
    at _dispatchDescribe (/var/lib/buildkite-agent/builds/kb-n2-4-spot-1fc47bc38e5c55bf/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-1fc47bc38e5c55bf/elastic/kibana-on-merge/kibana/node_modules/jest-circus/build/index.js:55:5)
    at describe (/var/lib/buildkite-agent/builds/kb-n2-4-spot-1fc47bc38e5c55bf/elastic/kibana-on-merge/kibana/x-pack/plugins/triggers_actions_ui/public/application/sections/alerts_table/alerts_table_state.test.tsx:271:3)
    at _dispatchDescribe (/var/lib/buildkite-agent/builds/kb-n2-4-spot-1fc47bc38e5c55bf/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-1fc47bc38e5c55bf/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-1fc47bc38e5c55bf/elastic/kibana-on-merge/kibana/x-pack/plugins/triggers_actions_ui/public/application/sections/alerts_table/alerts_table_state.test.tsx:159:1)
    at Runtime._execModule (/var/lib/buildkite-agent/builds/kb-n2-4-spot-1fc47bc38e5c55bf/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-1fc47bc38e5c55bf/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-1fc47bc38e5c55bf/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-1fc47bc38e5c55bf/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-1fc47bc38e5c55bf/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-1fc47bc38e5c55bf/elastic/kibana-on-merge/kibana/node_modules/jest-runner/build/runTest.js:444:34)

First failure: CI Build - 8.7

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

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

@botelastic botelastic bot removed the needs-team Issues missing a team label label Feb 9, 2023
@JiaweiWu JiaweiWu moved this from Awaiting Triage to Up for grabs in AppEx: ResponseOps - Rules & Alerts Management Feb 14, 2023
@JiaweiWu JiaweiWu added the Feature:Alerting/RulesManagement Issues related to the Rules Management UX label Feb 14, 2023
@XavierM XavierM closed this as completed Feb 21, 2023
@kibanamachine kibanamachine reopened this Jun 30, 2023
@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@mistic
Copy link
Member

mistic commented Jul 3, 2023

Skipped.

main: 04f8885

jcger added a commit that referenced this issue Aug 2, 2023
## Summary

closes #150790
The approach is the same as always when rendering the alerts table in
test, we mock jsdom getComputedStyle function as it has bad performance
and we don't really need that calculations
@kibanamachine kibanamachine reopened this Aug 14, 2023
@kibanamachine
Copy link
Contributor Author

New failure: CI Build - 8.9

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.

6 participants