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: Plugin Functional Tests.test/plugin_functional/test_suites/telemetry/telemetry·ts - telemetry Telemetry service detects that telemetry cannot be sent in screenshot mode #107034

Closed
kibanamachine opened this issue Jul 28, 2021 · 13 comments · Fixed by #143353
Closed

Failing test: Plugin Functional Tests.test/plugin_functional/test_suites/telemetry/telemetry·ts - telemetry Telemetry service detects that telemetry cannot be sent in screenshot mode #107034

kibanamachine opened this issue Jul 28, 2021 · 13 comments · Fixed by #143353
Labels
failed-test A test failure on a tracked branch, potentially flaky-test impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. loe:small Small Level of Effort Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc

Comments

@kibanamachine
Copy link
Contributor

kibanamachine commented Jul 28, 2021 •
edited
Loading

A test failed on a tracked branch

Error: retry.tryForTime timeout: Error: retry.try timeout: TimeoutError: Waiting for element to be located By(css selector, [data-test-subj="kibanaChrome"])
Wait timed out after 61219ms
    at /dev/shm/workspace/parallel/14/kibana/node_modules/selenium-webdriver/lib/webdriver.js:842:17
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:95:5)
    at onFailure (test/common/services/retry/retry_for_success.ts:17:9)
    at retryForSuccess (test/common/services/retry/retry_for_success.ts:57:13)
    at RetryService.try (test/common/services/retry/retry.ts:31:12)
    at /dev/shm/workspace/parallel/14/kibana/test/functional/page_objects/common_page.ts:233:21
    at runAttempt (test/common/services/retry/retry_for_success.ts:27:15)
    at retryForSuccess (test/common/services/retry/retry_for_success.ts:66:21)
    at RetryService.tryForTime (test/common/services/retry/retry.ts:22:12)
    at CommonPageObject.navigateToApp (test/functional/page_objects/common_page.ts:232:5)
    at Context.<anonymous> (test/plugin_functional/test_suites/telemetry/telemetry.ts:36:7)
    at Object.apply (node_modules/@kbn/test/target_node/functional_test_runner/lib/mocha/wrap_function.js:87:16)
    at onFailure (test/common/services/retry/retry_for_success.ts:17:9)
    at retryForSuccess (test/common/services/retry/retry_for_success.ts:57:13)
    at RetryService.tryForTime (test/common/services/retry/retry.ts:22:12)
    at CommonPageObject.navigateToApp (test/functional/page_objects/common_page.ts:232:5)
    at Context.<anonymous> (test/plugin_functional/test_suites/telemetry/telemetry.ts:36:7)
    at Object.apply (node_modules/@kbn/test/target_node/functional_test_runner/lib/mocha/wrap_function.js:87:16)

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

New failure: Jenkins Build

@botelastic botelastic bot added the needs-team Issues missing a team label label Jul 28, 2021
@vadimkibana vadimkibana added Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc and removed needs-team Issues missing a team label labels Sep 3, 2021
@elasticmachine
Copy link
Contributor

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

@kibanamachine
Copy link
Contributor Author

New failure: CI Build

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - master

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - 8.0

@exalate-issue-sync exalate-issue-sync bot added impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. loe:small Small Level of Effort labels Nov 4, 2021
@afharo
Copy link
Member

afharo commented Jun 27, 2022

Closing because it hasn't happened in a long while and we cannot see the build logs from those old failures.

@afharo afharo closed this as completed Jun 27, 2022
@kibanamachine
Copy link
Contributor Author

New failure: CI Build - 7.17

@kibanamachine kibanamachine reopened this Sep 28, 2022
@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

mistic added a commit that referenced this issue Sep 28, 2022
@mistic
skip flaky suite (#107034)
2d44c35
mistic added a commit that referenced this issue Sep 28, 2022
@mistic
skip flaky suite (#107034)
d9fc073
@mistic
Copy link
Member

mistic commented Sep 28, 2022

Skipped.

main: 2d44c35
7.17: d9fc073

@kibanamachine
Copy link
Contributor Author

New failure: CI Build - main

@afharo afharo mentioned this issue Oct 14, 2022
Merged
1 task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
failed-test A test failure on a tracked branch, potentially flaky-test impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. loe:small Small Level of Effort 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.

[Flaky tests] Unskip Telemetry Snapshot mode tests afharo/kibana
5 participants
@mistic @afharo @elasticmachine @kibanamachine @vadimkibana