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/cases/public/components/user_actions/property_actions - AlertPropertyActions remove alerts correctly #174670

Closed
kibanamachine opened this issue Jan 11, 2024 · 4 comments · Fixed by #174759
Labels
failed-test A test failure on a tracked branch, potentially flaky-test Feature:Cases Cases feature Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@kibanamachine
Copy link
Contributor

kibanamachine commented Jan 11, 2024

A test failed on a tracked branch

TestingLibraryElementError: Unable to find an element by: [data-test-subj="property-actions-user-action"]

Ignored nodes: comments, script, style
<body>
  <div />
</body>
    at Object.getElementError (/var/lib/buildkite-agent/builds/kb-n2-4-spot-873ed99d6a4cc289/elastic/kibana-on-merge/kibana/node_modules/@testing-library/dom/dist/config.js:40:19)
    at /var/lib/buildkite-agent/builds/kb-n2-4-spot-873ed99d6a4cc289/elastic/kibana-on-merge/kibana/node_modules/@testing-library/dom/dist/query-helpers.js:90:38
    at /var/lib/buildkite-agent/builds/kb-n2-4-spot-873ed99d6a4cc289/elastic/kibana-on-merge/kibana/node_modules/@testing-library/dom/dist/query-helpers.js:62:17
    at /var/lib/buildkite-agent/builds/kb-n2-4-spot-873ed99d6a4cc289/elastic/kibana-on-merge/kibana/node_modules/@testing-library/dom/dist/query-helpers.js:111:19
    at Object.getByTestId (/var/lib/buildkite-agent/builds/kb-n2-4-spot-873ed99d6a4cc289/elastic/kibana-on-merge/kibana/x-pack/plugins/cases/public/components/user_actions/property_actions/alert_property_actions.test.tsx:89:19)
    at Promise.then.completed (/var/lib/buildkite-agent/builds/kb-n2-4-spot-873ed99d6a4cc289/elastic/kibana-on-merge/kibana/node_modules/jest-circus/build/utils.js:300:28)
    at new Promise (<anonymous>)
    at callAsyncCircusFn (/var/lib/buildkite-agent/builds/kb-n2-4-spot-873ed99d6a4cc289/elastic/kibana-on-merge/kibana/node_modules/jest-circus/build/utils.js:233:10)
    at _callCircusTest (/var/lib/buildkite-agent/builds/kb-n2-4-spot-873ed99d6a4cc289/elastic/kibana-on-merge/kibana/node_modules/jest-circus/build/run.js:314:40)
    at _runTest (/var/lib/buildkite-agent/builds/kb-n2-4-spot-873ed99d6a4cc289/elastic/kibana-on-merge/kibana/node_modules/jest-circus/build/run.js:250:3)
    at _runTestsForDescribeBlock (/var/lib/buildkite-agent/builds/kb-n2-4-spot-873ed99d6a4cc289/elastic/kibana-on-merge/kibana/node_modules/jest-circus/build/run.js:125:9)
    at _runTestsForDescribeBlock (/var/lib/buildkite-agent/builds/kb-n2-4-spot-873ed99d6a4cc289/elastic/kibana-on-merge/kibana/node_modules/jest-circus/build/run.js:120:9)
    at run (/var/lib/buildkite-agent/builds/kb-n2-4-spot-873ed99d6a4cc289/elastic/kibana-on-merge/kibana/node_modules/jest-circus/build/run.js:70:3)
    at runAndTransformResultsToJestFormat (/var/lib/buildkite-agent/builds/kb-n2-4-spot-873ed99d6a4cc289/elastic/kibana-on-merge/kibana/node_modules/jest-circus/build/legacy-code-todo-rewrite/jestAdapterInit.js:122:21)
    at jestAdapter (/var/lib/buildkite-agent/builds/kb-n2-4-spot-873ed99d6a4cc289/elastic/kibana-on-merge/kibana/node_modules/jest-circus/build/legacy-code-todo-rewrite/jestAdapter.js:79:19)
    at runTestInternal (/var/lib/buildkite-agent/builds/kb-n2-4-spot-873ed99d6a4cc289/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-873ed99d6a4cc289/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 Jan 11, 2024
@botelastic botelastic bot added the needs-team Issues missing a team label label Jan 11, 2024
@kibanamachine kibanamachine added the Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) label Jan 11, 2024
@elasticmachine
Copy link
Contributor

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

@botelastic botelastic bot removed the needs-team Issues missing a team label label Jan 11, 2024
@cnasikas cnasikas added the Feature:Cases Cases feature label Jan 11, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/response-ops-cases (Feature:Cases)

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

mistic added a commit that referenced this issue Jan 11, 2024
@mistic
Copy link
Member

mistic commented Jan 11, 2024

Skipped.

main: 881c8e5

@cnasikas cnasikas linked a pull request Jan 12, 2024 that will close this issue
2 tasks
semd pushed a commit to semd/kibana that referenced this issue Jan 12, 2024
cnasikas added a commit that referenced this issue Jan 15, 2024
## Summary

Fixes: #174671,
#174670,
#174669,
#174668,
#174667

Successful builds:
https://buildkite.com/elastic/kibana-pull-request/builds?branch=cnasikas%3Afix_alert_property_actions_flaky

### Checklist

Delete any items that are not applicable to this PR.

- [x] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios

### For maintainers

- [x] This was checked for breaking API changes and was [labeled
appropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)

---------

Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
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:Cases Cases feature Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants