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

failsOnMKI: serverless discover context link test suite #191237

Open
pheyos opened this issue Aug 24, 2024 · 1 comment
Open

failsOnMKI: serverless discover context link test suite #191237

pheyos opened this issue Aug 24, 2024 · 1 comment
Labels
failed-test A test failure on a tracked branch, potentially flaky-test impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. loe:small Small Level of Effort Team:DataDiscovery Discover App Team (Document Explorer, Saved Search, Surrounding documents, Graph) test-failure-flaky

Comments

@pheyos
Copy link
Member

pheyos commented Aug 24, 2024

The serverless discover context link test suite started to become flaky (5 out of the last 8 runs failed) for three tests when running against MKI.

Test file: x-pack/test_serverless/functional/test_suites/common/context/_discover_navigation.ts

Note that this might be related to a recent update of the used Chrome browser version which was held back for local / PR testing.

Failure details

First failure

context app context link in discover should open the context view with the selected document as anchor and allows selecting next anchor`

Failure message:

StaleElementReferenceError: stale element reference: stale element not found in the current frame
  (Session info: chrome=128.0.6613.84)
    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)

Failure screenshot:
image

Second failure

context app context link in discover should open the context view with the filters disabled

Failure message:

Error: expected 0 to equal 2
    at Assertion.assert (expect.js:100:11)
    at Assertion.apply (expect.js:227:8)
    at Assertion.be (expect.js:69:22)
    at Context. (_discover_navigation.ts:113:40)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at Object.apply (wrap_function.js:73:16)

Failure screenshot:
image

Third failure

context app context link in discover should navigate to the first document and then back to discover

Failure message:

Error: retry.try reached timeout 120000 ms
TimeoutError: Waiting for element to be located By(css selector, [data-test-subj="successorsLoadMoreButton"])
Wait timed out after 10002ms
    at /root/.qaf/data/git/kibana/node_modules/selenium-webdriver/lib/webdriver.js:913:22
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at onFailure (retry_for_success.ts:17:9)
    at retryForSuccess (retry_for_success.ts:84:7)
    at RetryService.try (retry.ts:51:12)
    at ContextPageObject.waitUntilContextLoadingHasFinished (context_page.ts:83:12)
    at Context. (_discover_navigation.ts:117:7)
    at Object.apply (wrap_function.js:73:16)

Failure screenshot:
image

@pheyos pheyos added failed-test A test failure on a tracked branch, potentially flaky-test test-failure-flaky Team:DataDiscovery Discover App Team (Document Explorer, Saved Search, Surrounding documents, Graph) labels Aug 24, 2024
@elasticmachine
Copy link
Contributor

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

pheyos added a commit that referenced this issue Aug 24, 2024
## Summary

This PR skips the failing serverless discover and visualize tests for
MKI runs.

For more details, see the corresponding issues #191237 and #191238.
@kertal kertal added the impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. label Aug 26, 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:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. loe:small Small Level of Effort Team:DataDiscovery Discover App Team (Document Explorer, Saved Search, Surrounding documents, Graph) test-failure-flaky
Projects
None yet
Development

No branches or pull requests

4 participants