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.packages/analytics/client/src/analytics_client - AnalyticsClient E2E Discards all the events at the shipper level (globally disabled) #131369

Closed
kibanamachine opened this issue May 3, 2022 · 2 comments · Fixed by #131494
Closed

Failing test: Jest Tests.packages/analytics/client/src/analytics_client - AnalyticsClient E2E Discards all the events at the shipper level (globally disabled) #131369

kibanamachine opened this issue May 3, 2022 · 2 comments · Fixed by #131494
Assignees
@afharo
Labels
failed-test A test failure on a tracked branch, potentially flaky-test impact:critical This issue should be addressed immediately due to a critical level of impact on the product. Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc

Comments

@kibanamachine
Copy link
Contributor

A test failed on a tracked branch

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

Expected number of calls: 2
Received number of calls: 0
    at Object.<anonymous> (/var/lib/buildkite-agent/builds/kb-n2-4-spot-64f93d39630da1a1/elastic/kibana-on-merge/kibana/packages/analytics/client/src/analytics_client/analytics_client.test.ts:1124:33)
    at runNextTicks (node:internal/process/task_queues:61:5)
    at processTimers (node:internal/timers:499:9)
    at _callCircusTest (/var/lib/buildkite-agent/builds/kb-n2-4-spot-64f93d39630da1a1/elastic/kibana-on-merge/kibana/node_modules/jest-circus/build/run.js:212:5)
    at _runTest (/var/lib/buildkite-agent/builds/kb-n2-4-spot-64f93d39630da1a1/elastic/kibana-on-merge/kibana/node_modules/jest-circus/build/run.js:149:3)
    at _runTestsForDescribeBlock (/var/lib/buildkite-agent/builds/kb-n2-4-spot-64f93d39630da1a1/elastic/kibana-on-merge/kibana/node_modules/jest-circus/build/run.js:63:9)
    at _runTestsForDescribeBlock (/var/lib/buildkite-agent/builds/kb-n2-4-spot-64f93d39630da1a1/elastic/kibana-on-merge/kibana/node_modules/jest-circus/build/run.js:57:9)
    at _runTestsForDescribeBlock (/var/lib/buildkite-agent/builds/kb-n2-4-spot-64f93d39630da1a1/elastic/kibana-on-merge/kibana/node_modules/jest-circus/build/run.js:57:9)
    at run (/var/lib/buildkite-agent/builds/kb-n2-4-spot-64f93d39630da1a1/elastic/kibana-on-merge/kibana/node_modules/jest-circus/build/run.js:25:3)
    at runAndTransformResultsToJestFormat (/var/lib/buildkite-agent/builds/kb-n2-4-spot-64f93d39630da1a1/elastic/kibana-on-merge/kibana/node_modules/jest-circus/build/legacy-code-todo-rewrite/jestAdapterInit.js:176:21)

First failure: CI Build - main
@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label May 3, 2022
@botelastic botelastic bot added the needs-team Issues missing a team label label May 3, 2022
@kibanamachine kibanamachine added the Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc label May 3, 2022
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-core (Team:Core)

@botelastic botelastic bot removed the needs-team Issues missing a team label label May 3, 2022
suchcodemuchwow pushed a commit that referenced this issue May 3, 2022
skip flaky suite (#131369)
c1d4415
@suchcodemuchwow
Copy link
Contributor

Skipped because jest tests should not be failing. It uses real timers when it should be using fake timers. cc @afharo

main/8.3: c1d4415

academo pushed a commit to academo/kibana that referenced this issue May 4, 2022
skip flaky suite (elastic#131369)
cf421a8
@afharo afharo self-assigned this May 4, 2022
@afharo afharo mentioned this issue May 4, 2022
Merged
1 task
@exalate-issue-sync exalate-issue-sync bot added the impact:critical This issue should be addressed immediately due to a critical level of impact on the product. label May 4, 2022
@exalate-issue-sync exalate-issue-sync bot reopened this May 4, 2022
kertal pushed a commit to kertal/kibana that referenced this issue May 24, 2022
@kertal
skip flaky suite (elastic#131369)
7ebea07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@afharo afharo

Labels
failed-test A test failure on a tracked branch, potentially flaky-test impact:critical This issue should be addressed immediately due to a critical level of impact on the product. Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[EBT] Fix flaky test afharo/kibana
4 participants
@afharo @suchcodemuchwow @elasticmachine @kibanamachine