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.

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: Chrome UI Functional Tests.test/functional/apps/context/_context_navigation·ts - context app discover - context - back navigation should go back after loading #188396

Closed
kibanamachine opened this issue Jul 16, 2024 · 6 comments · Fixed by #188811
Assignees
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:DataDiscovery Discover, search (e.g. data plugin and KQL), data views, saved searches. For ES|QL, use Team:ES|QL.

Comments

@kibanamachine
Copy link
Contributor

kibanamachine commented Jul 16, 2024

A test failed on a tracked branch

Error: timed out waiting for user navigating to context and returning to discover -- last error: Error: timed out waiting for doc viewer to open -- last error: ElementNotInteractableError: element not interactable
  (Session info: chrome=126.0.6478.126)
    at Object.throwDecodedError (node_modules/selenium-webdriver/lib/error.js:521:15)
    at parseHttpResponse (node_modules/selenium-webdriver/lib/http.js:514:13)
    at Executor.execute (node_modules/selenium-webdriver/lib/http.js:446:28)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at Task.exec (prevent_parallel_calls.ts:28:20)
    at onFailure (retry_for_truthy.ts:39:13)
    at retryForSuccess (retry_for_success.ts:84:7)
    at retryForTruthy (retry_for_truthy.ts:27:3)
    at RetryService.waitFor (retry.ts:87:5)
    at DataGridService.clickRowToggle (data_grid.ts:327:7)
    at _context_navigation.ts:60:9
    at runAttempt (retry_for_success.ts:29:15)
    at retryForSuccess (retry_for_success.ts:98:21)
    at retryForTruthy (retry_for_truthy.ts:27:3)
    at RetryService.waitFor (retry.ts:87:5)
    at Context.<anonymous> (_context_navigation.ts:57:7)
    at Object.apply (wrap_function.js:73:16)
    at onFailure (retry_for_truthy.ts:39:13)
    at retryForSuccess (retry_for_success.ts:84:7)
    at retryForTruthy (retry_for_truthy.ts:27:3)
    at RetryService.waitFor (retry.ts:87:5)
    at Context.<anonymous> (_context_navigation.ts:57:7)
    at Object.apply (wrap_function.js:73:16)

First failure: kibana-on-merge - main

@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label Jul 16, 2024
@botelastic botelastic bot added the needs-team Issues missing a team label label Jul 16, 2024
@kibanamachine kibanamachine added the Team:DataDiscovery Discover, search (e.g. data plugin and KQL), data views, saved searches. For ES|QL, use Team:ES|QL. label Jul 16, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-data-discovery (Team:DataDiscovery)

@botelastic botelastic bot removed the needs-team Issues missing a team label label Jul 16, 2024
@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@mistic
Copy link
Member

mistic commented Jul 16, 2024

Skipped.

main: 1112842

@kertal kertal added the impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. label Jul 16, 2024
@davismcphee davismcphee added the loe:small Small Level of Effort label Jul 16, 2024
@jughosta jughosta self-assigned this Jul 22, 2024
@kibanamachine kibanamachine reopened this Nov 18, 2024
@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - 8.16

@kertal kertal added impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. and removed impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. labels Dec 3, 2024
@kertal
Copy link
Member

kertal commented Dec 6, 2024

it was failing differently now, but just once, let's see if it comes back, closing for now

@kertal kertal closed this as not planned Won't fix, can't repro, duplicate, stale Dec 6, 2024
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 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:DataDiscovery Discover, search (e.g. data plugin and KQL), data views, saved searches. For ES|QL, use Team:ES|QL.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants