Failing test: Execution Context Functional Tests.x-pack/test/functional_execution_context/tests/browser·ts - Execution context Browser apps "after all" hook in "Browser apps"

[kibanamachine]

A test failed on a tracked branch

Error: retry.tryForTime timeout: TimeoutError: Waiting for element to be located By(css selector, [data-test-subj="removeSampleDataSetflights"])
Wait timed out after 10040ms
    at /dev/shm/workspace/parallel/21/kibana/node_modules/selenium-webdriver/lib/webdriver.js:842:17
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:95:5)
    at onFailure (/dev/shm/workspace/parallel/21/kibana/test/common/services/retry/retry_for_success.ts:17:9)
    at retryForSuccess (/dev/shm/workspace/parallel/21/kibana/test/common/services/retry/retry_for_success.ts:57:13)
    at RetryService.tryForTime (/dev/shm/workspace/parallel/21/kibana/test/common/services/retry/retry.ts:22:12)
    at TestSubjects.waitForEnabled (/dev/shm/workspace/parallel/21/kibana/test/functional/services/common/test_subjects.ts:305:5)
    at HomePageObject.removeSampleDataSet (/dev/shm/workspace/parallel/21/kibana/test/functional/page_objects/home_page.ts:55:5)
    at Context.<anonymous> (test/functional_execution_context/tests/browser.ts:29:7)
    at Object.apply (/dev/shm/workspace/parallel/21/kibana/node_modules/@kbn/test/target_node/functional_test_runner/lib/mocha/wrap_function.js:87:16)

First failure: Jenkins Build

[kibanamachine]

New failure: Jenkins Build

[kibanamachine]

New failure: Jenkins Build

[kibanamachine]

New failure: Jenkins Build

[lukeelmers]

closing for now as we haven't seen any activity on this in ~60 days.

[kibanamachine]

New failure: CI Build - main

[elasticmachine]

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

[kibanamachine]

New failure: CI Build - main

[kibanamachine]

New failure: CI Build - main

[mistic]

Skipped.

main: e404798

[gsoldevila]

I think I found the explanation to the flaky behavior: Pay close attention to the screen capture below (running locally, animations disabled):

https://github.com/elastic/kibana/assets/25349407/117dfec0-165e-4ffb-a9c0-5ab89d89b750

Notice how, after clicking the Remove link, the UI shows the Removing + spinner and then, for a fraction of second, we have the Remove button again. Looking at the trace of the failing test:

• We can see how it successfully removes the data set on the first attempt.
• The remove logic is on a retry block, which checks the presence of the Remove button to determine the remove was successful.
• If that check happens during that split second where the Remove button appears again before being actually deleted, this will cause the logic to attempt to delete it again, but it will get stuck awaiting to find that very same button.

[gsoldevila]

Here are the entry points to the failing line:

• https://github.com/elastic/kibana/blob/main/x-pack/test/functional_execution_context/tests/browser.ts#L51
• https://github.com/elastic/kibana/blob/main/test/functional/page_objects/home_page.ts#L116

[elasticmachine]

Pinging @elastic/appex-sharedux (Team:SharedUX)

[bhavyarm]

@gsoldevila I removed your assignment because you assigned shared-ux team. Cheers!

[kibanamachine]

New failure: kibana-on-merge - main

[afharo]

Wow! An error in the afterAll trying to clean up the installed data samples 😢

[afharo]

it looks like CI has been flaky due to external factors this week. Let's close and wait for the next occurrence.

[kibanamachine]

New failure: kibana-on-merge - main

[eokoneyo]

it's happened again :( ... taking a look, for what it's worth the test passed on the second run

[eokoneyo]

This was resolved in https://github.com/elastic/kibana/pull/199005