-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
[Fleet] Reenable flaky test and add longer timeout #194843
Conversation
Pinging @elastic/fleet (Team:Fleet) |
💛 Build succeeded, but was flaky
Failed CI StepsTest Failures
Metrics [docs]
To update your PR or re-run it, just comment with: cc @criamico |
Closes elastic#192999 ## Summary [Fleet] Reenable skipped flaky test. The [beforeEach](elastic#192999) conditions in this test keep failing because they take longer than the 5s timeout allowed for each test. Here I'm adding an 8s timeout to attempt fixing it. ### Checklist - [ ] [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
Closes elastic#192999 ## Summary [Fleet] Reenable skipped flaky test. The [beforeEach](elastic#192999) conditions in this test keep failing because they take longer than the 5s timeout allowed for each test. Here I'm adding an 8s timeout to attempt fixing it. ### Checklist - [ ] [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
Friendly reminder: Looks like this PR hasn’t been backported yet. |
Friendly reminder: Looks like this PR hasn’t been backported yet. |
Closes #192999
Summary
[Fleet] Reenable skipped flaky test. The beforeEach conditions in this test keep failing because they take longer than the 5s timeout allowed for each test.
Here I'm adding an 8s timeout to attempt fixing it.
Checklist