Failing test: Serverless Observability Functional Tests.x-pack/test_serverless/functional/test_suites/observability/observability_log_explorer/header_menu·ts - serverless observability UI Observability Log Explorer Header menu "after all" hook for "should inject the app header menu on the top navbar"

[kibanamachine]

A test failed on a tracked branch

Error: timed out waiting for Waiting for logout to complete
    at onFailure (retry_for_truthy.ts:39:13)
    at retryForSuccess (retry_for_success.ts:59:13)
    at retryForTruthy (retry_for_truthy.ts:27:3)
    at RetryService.waitFor (retry.ts:59:5)
    at SecurityPageObject.forceLogout (security_page.ts:319:7)
    at Object.forceLogout (svl_common_page.ts:95:7)
    at Context.<anonymous> (header_menu.ts:34:7)
    at Object.apply (wrap_function.js:73:16)

First failure: CI Build - main

[elasticmachine]

Pinging @elastic/infra-monitoring-ui (Team:Infra Monitoring UI)

[tonyghiani]

Fixed by #167482

[kibanamachine]

New failure: CI Build - main

[elasticmachine]

Pinging @elastic/obs-ux-logs-team (Team:obs-ux-logs)

[kibanamachine]

New failure: CI Build - 8.12

[chrisdistasio]

@gbamparop is this failed test something that needs to be addressed or is it resolved now?

[gbamparop]

@chrisdistasio we discussed the failing tests with the team a while back and it seems that most of the open ones are not related to our changes but we will keep monitoring them.

[chrisdistasio]

thanks @gbamparop! is your team the rightful owner and what is the mechanism to continue (active?) monitoring? is there a separate issue for it?

what should we do with this specific issue?

[gbamparop]

We normally discuss the new issues for test failures in team meetings. We can close the issue but it could still be reopened in the future due to flakiness. @tonyghiani WDYT?

[tonyghiani]

As for other tests where we noticed flakiness, this is not related to a failure on our test implementation, instead is caused by unreliability on the login/logout step which causes random flakiness (see the test screenshot to notice the issue).

I don't think there is much we can do in this case and it will probably occur again, maybe on different tests than this.