Failing test: Serverless Search Functional Tests.x-pack/test_serverless/functional/test_suites/search/empty_page·ts - serverless search UI empty pages should show search specific empty page in discover

[kibanamachine]

A test failed on a tracked branch

Error: retry.try timeout: Error: expected null to not equal null
    at Assertion.assert (expect.js:100:11)
    at Assertion.apply (expect.js:227:8)
    at Assertion.be (expect.js:69:22)
    at svl_common_navigation.ts:150:72
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at runAttempt (retry_for_success.ts:29:15)
    at retryForSuccess (retry_for_success.ts:68:21)
    at RetryService.try (retry.ts:31:12)
    at Object.expectBreadcrumbExists (svl_common_navigation.ts:149:11)
    at Context.<anonymous> (empty_page.ts:30:7)
    at Object.apply (wrap_function.js:73:16)
    at onFailure (retry_for_success.ts:17:9)
    at retryForSuccess (retry_for_success.ts:59:13)
    at RetryService.try (retry.ts:31:12)
    at Object.expectBreadcrumbExists (svl_common_navigation.ts:149:11)
    at Context.<anonymous> (empty_page.ts:30:7)
    at Object.apply (wrap_function.js:73:16)

First failure: CI Build - main

[elasticmachine]

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

[Dosant]

Another login page issue

[vadimkibana]

Closing, as the error was with the login screen; and test did not fail again, se we expect that the login is fixed now.

If it is re-opened, we will take a closer look.

[kibanamachine]

New failure: CI Build - main

[Dosant]

Also the login page

@elastic/kibana-operations, @elastic/kibana-qa It doesn't look like we should just skip this test, because as I understand, this test is failing just because it is the first test in the suite. If we skip this, then the next one starts failing. Have you see this login screen failures before? Seems like something should be approached holistically and not test-by-test

Similar failures and skipped tests: #165924 (comment), #165386 these are from another suite, but also the first tests

[jbudz]

Correct, we can't reliably skip this error because it impacts most test suites.

@dmlemeshko is testing some stability improvements at #166936