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/cases/public/containers/user_profiles - useGetCurrentUserProfile shows a toast error message when an error occurs in the response #183144

Closed
kibanamachine opened this issue May 10, 2024 · 4 comments · Fixed by #183721
Closed

Failing test: Jest Tests.x-pack/plugins/cases/public/containers/user_profiles - useGetCurrentUserProfile shows a toast error message when an error occurs in the response #183144

kibanamachine opened this issue May 10, 2024 · 4 comments · Fixed by #183721
Assignees
@cnasikas
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 May 10, 2024 •
edited

A test failed on a tracked branch

Error: Timed out in waitFor after 1000ms.
    at waitFor (/var/lib/buildkite-agent/builds/kb-n2-4-spot-eb0d3642e6e606a4/elastic/kibana-on-merge/kibana/node_modules/@testing-library/react-hooks/lib/core/asyncUtils.js:64:13)
    at Object.<anonymous> (/var/lib/buildkite-agent/builds/kb-n2-4-spot-eb0d3642e6e606a4/elastic/kibana-on-merge/kibana/x-pack/plugins/cases/public/containers/user_profiles/use_get_current_user_profile.test.ts:63:5)

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

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

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

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

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

mistic added a commit that referenced this issue May 15, 2024
@mistic
skip flaky suite (#183144)
f7098f3
@mistic
Copy link
Member

mistic commented May 15, 2024

Skipped.

main: f7098f3

@cnasikas cnasikas self-assigned this May 17, 2024
@cnasikas cnasikas mentioned this issue May 17, 2024
Merged
2 tasks
cnasikas added a commit that referenced this issue May 17, 2024
@cnasikas
[Cases] Fix flaky hooks (#183721)
0e112e3 
## Summary

Fixes: #183144,
#182845

### 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)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@cnasikas cnasikas

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
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[Cases] Fix flaky hooks cnasikas/kibana
4 participants
@mistic @cnasikas @elasticmachine @kibanamachine