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.src/plugins/charts/public/services/active_cursor - useActiveCursor should trigger cursor pointer update (chart type: datatable - time based, event type: time) #130177

Closed
kibanamachine opened this issue Apr 13, 2022 · 3 comments · Fixed by #130358 or #130531
Closed

Failing test: Jest Tests.src/plugins/charts/public/services/active_cursor - useActiveCursor should trigger cursor pointer update (chart type: datatable - time based, event type: time) #130177

kibanamachine opened this issue Apr 13, 2022 · 3 comments · Fixed by #130358 or #130531
Assignees
@alexwizp
Labels
failed-test A test failure on a tracked branch, potentially flaky-test impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. Team:Visualizations Visualization editors, elastic-charts and infrastructure

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: 1
    at Object.<anonymous> (/var/lib/buildkite-agent/builds/kb-n2-4-spot-841a108bde9b7f1e/elastic/kibana-on-merge/kibana/src/plugins/charts/public/services/active_cursor/use_active_cursor.test.ts:132:42)
    at _callCircusTest (/var/lib/buildkite-agent/builds/kb-n2-4-spot-841a108bde9b7f1e/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-841a108bde9b7f1e/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-841a108bde9b7f1e/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-841a108bde9b7f1e/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-841a108bde9b7f1e/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-841a108bde9b7f1e/elastic/kibana-on-merge/kibana/node_modules/jest-circus/build/legacy-code-todo-rewrite/jestAdapterInit.js:176:21)
    at jestAdapter (/var/lib/buildkite-agent/builds/kb-n2-4-spot-841a108bde9b7f1e/elastic/kibana-on-merge/kibana/node_modules/jest-circus/build/legacy-code-todo-rewrite/jestAdapter.js:109:19)
    at runTestInternal (/var/lib/buildkite-agent/builds/kb-n2-4-spot-841a108bde9b7f1e/elastic/kibana-on-merge/kibana/node_modules/jest-runner/build/runTest.js:380:16)
    at runTest (/var/lib/buildkite-agent/builds/kb-n2-4-spot-841a108bde9b7f1e/elastic/kibana-on-merge/kibana/node_modules/jest-runner/build/runTest.js:472:34)

First failure: CI Build - main
@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label Apr 13, 2022
@botelastic botelastic bot added the needs-team Issues missing a team label label Apr 13, 2022
@kibanamachine kibanamachine added the Team:Visualizations Visualization editors, elastic-charts and infrastructure label Apr 13, 2022
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-vis-editors @elastic/kibana-vis-editors-external (Team:VisEditors)

@botelastic botelastic bot removed the needs-team Issues missing a team label label Apr 13, 2022
spalger pushed a commit that referenced this issue Apr 13, 2022
skip flaky suite (#130177)
de25fb0
@spalger
Copy link
Contributor

spalger commented Apr 13, 2022

Jest tests really shouldn't be flaky, and this has failed 5 PRs this week:

image

Skipped:
8.3/main: de25fb0

@alexwizp alexwizp self-assigned this Apr 14, 2022
@alexwizp
Copy link
Contributor

Looks like it's related to #129087

@alexwizp alexwizp mentioned this issue Apr 15, 2022
Merged
@exalate-issue-sync exalate-issue-sync bot reopened this Apr 18, 2022
@exalate-issue-sync exalate-issue-sync bot added the impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. label Apr 18, 2022
@alexwizp alexwizp reopened this Apr 18, 2022
@alexwizp alexwizp mentioned this issue Apr 19, 2022
Merged
@exalate-issue-sync exalate-issue-sync bot reopened this Apr 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@alexwizp alexwizp

Labels
failed-test A test failure on a tracked branch, potentially flaky-test impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. Team:Visualizations Visualization editors, elastic-charts and infrastructure
Projects
None yet
Milestone
No milestone
4 participants
@spalger @elasticmachine @alexwizp @kibanamachine