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: X-Pack Jest Tests.x-pack/plugins/task_manager/server/lib - Bulk Operation Buffer createBuffer() batch updates are executed at most by the next Event Loop tick by default #72700

Closed
kibanamachine opened this issue Jul 21, 2020 · 5 comments · Fixed by #72815
Closed

Failing test: X-Pack Jest Tests.x-pack/plugins/task_manager/server/lib - Bulk Operation Buffer createBuffer() batch updates are executed at most by the next Event Loop tick by default #72700

kibanamachine opened this issue Jul 21, 2020 · 5 comments · Fixed by #72815
Assignees
@gmmorris
Labels
failed-test A test failure on a tracked branch, potentially flaky-test Feature:Task Manager Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@kibanamachine
Copy link
Contributor

kibanamachine commented Jul 21, 2020 •
edited
Loading

A test failed on a tracked branch

Error: expect(jest.fn()).toHaveBeenCalledTimes(expected)

Expected number of calls: 1
Received number of calls: 0
    at setTimeout (/dev/shm/workspace/kibana/x-pack/plugins/task_manager/server/lib/bulk_operation_buffer.test.ts:90:30)
    at Timeout.callback [as _onTimeout] (/dev/shm/workspace/kibana/node_modules/jsdom/lib/jsdom/browser/Window.js:661:19)
    at ontimeout (timers.js:436:11)
    at tryOnTimeout (timers.js:300:5)
    at listOnTimeout (timers.js:263:5)
    at Timer.processTimers (timers.js:223:10)

First failure: Jenkins Build
@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label Jul 21, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-test-triage (failed-test)

@tylersmalley tylersmalley added Feature:Task Manager Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) labels Jul 21, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-alerting-services (Team:Alerting Services)

@tylersmalley tylersmalley mentioned this issue Jul 21, 2020
Merged
2 tasks
@tylersmalley
Copy link
Contributor

Reverted the 7.x backport of #71470 (comment) which I believe caused this.

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@tylersmalley
Copy link
Contributor

Skipped in master: 33a9604

@gmmorris gmmorris mentioned this issue Jul 22, 2020
Merged
2 tasks
@kobelb kobelb added the needs-team Issues missing a team label label Jan 31, 2022
@botelastic botelastic bot removed the needs-team Issues missing a team label label Jan 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gmmorris gmmorris

Labels
failed-test A test failure on a tracked branch, potentially flaky-test Feature:Task Manager 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.

[Task Manager] Addresses flaky test introduced by buffered store gmmorris/kibana
5 participants
@tylersmalley @gmmorris @kobelb @elasticmachine @kibanamachine