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: Chrome X-Pack UI Functional Tests with ES SSL - Cases - group 2.x-pack/test/functional_with_es_ssl/apps/cases/group2/attachment_framework·ts - Cases Attachment framework Attachment hooks Modal filters with multiple selection #178690

Open
kibanamachine opened this issue Mar 14, 2024 · 12 comments · Fixed by #181230
Open

Failing test: Chrome X-Pack UI Functional Tests with ES SSL - Cases - group 2.x-pack/test/functional_with_es_ssl/apps/cases/group2/attachment_framework·ts - Cases Attachment framework Attachment hooks Modal filters with multiple selection #178690

kibanamachine opened this issue Mar 14, 2024 · 12 comments · Fixed by #181230
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 Mar 14, 2024 •
edited
Loading

A test failed on a tracked branch

Error: expected testSubject(cases-table-row-9fbcafd7-1116-4eb0-a224-f35d9ec4930b) to exist
    at TestSubjects.existOrFail (test_subjects.ts:71:13)
    at Context.<anonymous> (attachment_framework.ts:332:13)
    at Object.apply (wrap_function.js:73:16)

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

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

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

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

mistic added a commit that referenced this issue Mar 14, 2024
@mistic
skip flaky suite (#178690)
d95ae3e
@mistic
Copy link
Member

mistic commented Mar 14, 2024

Skipped.

main: d95ae3e

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@cnasikas cnasikas added the Feature:Cases Cases feature label Mar 15, 2024
@elasticmachine
Copy link
Contributor

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

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - 8.13

@kibanamachine
Copy link
Contributor Author

Skipped

8.13: fd0a060

kibanamachine added a commit that referenced this issue Mar 28, 2024
@kibanamachine
skip failing test suite (#178690)
fd0a060
@cnasikas cnasikas linked a pull request Apr 19, 2024 that will close this issue
[Cases] Fix flaky functional tests #181230
Merged
3 tasks
@cnasikas cnasikas mentioned this issue Apr 19, 2024
Merged
3 tasks
@cnasikas cnasikas self-assigned this Apr 21, 2024
cnasikas added a commit that referenced this issue Apr 22, 2024
@cnasikas @kibanamachine
[Cases] Fix flaky functional tests (#181230)
8a99299 
## Summary

I ran the flaky test runner multiple times. I did not find any good
reason why some of the tests were flaky in the first place.

Flaky test runner:
https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/5720,
https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/5721,
https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/5727

Fixes: #179016,
#178991,
#176716,
#178690

### 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
- [x] [Flaky Test
Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was
used on any tests changed

### 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 <[email protected]>
kibanamachine pushed a commit to kibanamachine/kibana that referenced this issue Apr 22, 2024
@cnasikas
[Cases] Fix flaky functional tests (elastic#181230)
687c7ef 
## Summary

I ran the flaky test runner multiple times. I did not find any good
reason why some of the tests were flaky in the first place.

Flaky test runner:
https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/5720,
https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/5721,
https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/5727

Fixes: elastic#179016,
elastic#178991,
elastic#176716,
elastic#178690

### 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
- [x] [Flaky Test
Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was
used on any tests changed

### 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 <[email protected]>
(cherry picked from commit 8a99299)
@kibanamachine kibanamachine reopened this Jun 18, 2024
@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

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 functional tests cnasikas/kibana
4 participants
@mistic @cnasikas @elasticmachine @kibanamachine