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:
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:
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)
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:
Failure screenshot:
Second failure
context app context link in discover should open the context view with the filters disabled
Failure message:
Failure screenshot:
Third failure
context app context link in discover should navigate to the first document and then back to discover
Failure message:
Failure screenshot: