-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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/event_log/server/es - retries createIlmPolicyIfNotExists with 1 retry #156061
Labels
failed-test
A test failure on a tracked branch, potentially flaky-test
Team:ResponseOps
Label for the ResponseOps team (formerly the Cases and Alerting teams)
Comments
kibanamachine
added
the
failed-test
A test failure on a tracked branch, potentially flaky-test
label
Apr 27, 2023
kibanamachine
added
the
Team:ResponseOps
Label for the ResponseOps team (formerly the Cases and Alerting teams)
label
Apr 27, 2023
Pinging @elastic/response-ops (Team:ResponseOps) |
github-project-automation
bot
moved this to Awaiting Triage
in AppEx: ResponseOps - Execution & Connectors
Apr 27, 2023
New failure: CI Build - main |
New failure: CI Build - main |
ymao1
moved this from Awaiting Triage
to Todo
in AppEx: ResponseOps - Execution & Connectors
May 18, 2023
ersin-erdal
moved this from Todo
to In Progress
in AppEx: ResponseOps - Execution & Connectors
May 26, 2023
New failure: CI Build - main |
Skipped. main: b529887 |
ersin-erdal
moved this from In Progress
to In Review
in AppEx: ResponseOps - Execution & Connectors
May 31, 2023
github-project-automation
bot
moved this from In Review
to Done
in AppEx: ResponseOps - Execution & Connectors
Jun 1, 2023
ersin-erdal
added a commit
that referenced
this issue
Jun 1, 2023
…elapsed time in tests (#158721) Resolves: #156061 Since all the failed CI results show actual elapsed time as `19` rather than `20` (expected), the issue seems like an inaccurate time calculation caused by `Date.now()` method. Replacing `Date.now()` with the more precise `performance.now()` method may solve the problem.
New failure: CI Build - main |
New failure: CI Build - main |
Skipped. main: 3f55d18 |
github-project-automation
bot
moved this to Awaiting Triage
in AppEx: ResponseOps - Execution & Connectors
Jun 15, 2023
mikecote
moved this from Awaiting Triage
to Todo
in AppEx: ResponseOps - Execution & Connectors
Jun 21, 2023
doakalexi
moved this from Todo
to In Progress
in AppEx: ResponseOps - Execution & Connectors
Jul 26, 2023
doakalexi
moved this from In Progress
to In Review
in AppEx: ResponseOps - Execution & Connectors
Jul 26, 2023
doakalexi
moved this from In Review
to Done
in AppEx: ResponseOps - Execution & Connectors
Jul 31, 2023
ThomThomson
pushed a commit
to ThomThomson/kibana
that referenced
this issue
Aug 1, 2023
…elastic#162558) elastic#156061 ## Summary Fixes flaky test by adding ceil(). When it fails the time elapsed is close to the `MOCK_RETRY_DELAY` of 20 (like 19.7), so rounding up helps with the flakiness
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
Team:ResponseOps
Label for the ResponseOps team (formerly the Cases and Alerting teams)
A test failed on a tracked branch
First failure: CI Build - main
The text was updated successfully, but these errors were encountered: