Failing test: Serverless Observability Discover Context Awareness Functional Tests.x-pack/test_serverless/functional/test_suites/common/discover/context_awareness/extensions/_get_additional_cell_actions·ts - discover/context_awareness extension getAdditionalCellActions data view mode should not render incompatible cell action for message column

[kibanamachine]

A test failed on a tracked branch

Error: retry.try reached timeout 120000 ms
TimeoutError: Waiting for element to be located By(css selector, [data-test-subj="euiDataGridBody"] [data-test-subj="dataGridRowCell"][data-gridcell-column-index="6"][data-gridcell-visible-row-index="0"])
Wait timed out after 10036ms
    at /opt/buildkite-agent/builds/bk-agent-prod-gcp-1726736379337222779/elastic/kibana-on-merge/kibana/node_modules/selenium-webdriver/lib/webdriver.js:915:22
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at onFailure (retry_for_success.ts:18:9)
    at retryForSuccess (retry_for_success.ts:85:7)
    at RetryService.try (retry.ts:52:12)
    at DataGridService.getCellActionButton (data_grid.ts:135:5)
    at DataGridService.clickCellExpandButton (data_grid.ts:152:26)
    at DataGridService.clickCellExpandButtonExcludingControlColumns (data_grid.ts:173:5)
    at Context.<anonymous> (_get_additional_cell_actions.ts:154:9)
    at Object.apply (wrap_function.js:74:16)

First failure: kibana-on-merge - main

[elasticmachine]

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

[kibanamachine]

New failure: kibana-on-merge - main

[kibanamachine]

New failure: kibana-on-merge - main

[jbudz]

/skip

[kibanamachine]

Skipped

main: 9f499ec67dd6bbb8d96ee6fd202eb4b53a0cdbd8

[kertal]

I've got a question about this @davismcphee , looking at the screen it becomes clear, why it failes. There should be a message columns, provided by the contextual awareness of the given data view. However it's neither rendered, nor are the columns part of the URL state, so there seems to be some flakiness when selecting the data view involved. But now i wonder, where to look to resolve this? Thx!

[kibanamachine]

New failure: kibana-on-merge - main

[kertal]

Closing, hasn't failed recently

[kibanamachine]

New failure: kibana-on-merge - main

[jughosta]

Looks like we can't resolve this flakiness unless we improve the default app state extension.

[davismcphee]

Yeah unfortunately it's a tricky one and I've still been unable to reproduce since it's so infrequent... Clearly some sort of race condition but it's unclear where. If we're lucky some of the changes in https://github.com/elastic/kibana/pull/200584 may address it.