Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failing test: Serverless Observability Functional Tests - Common Group 1.x-pack/test_serverless/functional/test_suites/common/platform_security/navigation/avatar_menu·ts - Serverless Common UI - Platform Security Avatar menu displays User Menu when clicked #167803

Closed
kibanamachine opened this issue Oct 2, 2023 · 4 comments
Assignees
Labels
failed-test A test failure on a tracked branch, potentially flaky-test Team:Security Team focused on: Auth, Users, Roles, Spaces, Audit Logging, and more!

Comments

@kibanamachine
Copy link
Contributor

A test failed on a tracked branch

Error: retry.tryForTime timeout: Error: retry.tryForTime timeout: Error: retry.try timeout: TimeoutError: Waiting for element to be located By(css selector, [data-test-subj="kibanaChrome"])
Wait timed out after 61161ms
    at /var/lib/buildkite-agent/builds/kb-n2-4-spot-a6f1631ba43e2504/elastic/kibana-on-merge/kibana/node_modules/selenium-webdriver/lib/webdriver.js:929:17
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at onFailure (retry_for_success.ts:17:9)
    at retryForSuccess (retry_for_success.ts:59:13)
    at RetryService.try (retry.ts:31:12)
    at common_page.ts:273:21
    at runAttempt (retry_for_success.ts:29:15)
    at retryForSuccess (retry_for_success.ts:68:21)
    at RetryService.tryForTime (retry.ts:22:12)
    at CommonPageObject.navigateToApp (common_page.ts:272:5)
    at svl_common_navigation.ts:21:9
    at runAttempt (retry_for_success.ts:29:15)
    at retryForSuccess (retry_for_success.ts:68:21)
    at RetryService.tryForTime (retry.ts:22:12)
    at Object.navigateToKibanaHome (svl_common_navigation.ts:20:7)
    at Context.<anonymous> (avatar_menu.ts:29: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.tryForTime (retry.ts:22:12)
    at CommonPageObject.navigateToApp (common_page.ts:272:5)
    at svl_common_navigation.ts:21:9
    at runAttempt (retry_for_success.ts:29:15)
    at retryForSuccess (retry_for_success.ts:68:21)
    at RetryService.tryForTime (retry.ts:22:12)
    at Object.navigateToKibanaHome (svl_common_navigation.ts:20:7)
    at Context.<anonymous> (avatar_menu.ts:29: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.tryForTime (retry.ts:22:12)
    at Object.navigateToKibanaHome (svl_common_navigation.ts:20:7)
    at Context.<anonymous> (avatar_menu.ts:29:7)
    at Object.apply (wrap_function.js:73:16)

First failure: CI Build - main

@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label Oct 2, 2023
@botelastic botelastic bot added the needs-team Issues missing a team label label Oct 2, 2023
@mistic mistic added the Team:Observability Team label for Observability Team (for things that are handled across all of observability) label Oct 3, 2023
@elasticmachine
Copy link
Contributor

Pinging @elastic/unified-observability (Team:Observability)

@botelastic botelastic bot removed the needs-team Issues missing a team label label Oct 3, 2023
@simianhacker
Copy link
Member

@elastic/platform-security Can you take a look at this?

@gtback
Copy link
Member

gtback commented Oct 23, 2023

Naming things is hard 😉 But I don't think this is for the (Cloud) Platform Security (SRE) team. Maybe @elastic/kibana-security ?

@jeramysoucy jeramysoucy added Team:Security Team focused on: Auth, Users, Roles, Spaces, Audit Logging, and more! and removed Team:Observability Team label for Observability Team (for things that are handled across all of observability) labels Oct 23, 2023
@SiddharthMantri
Copy link
Contributor

Closing as this issue was address by @dmlemeshko in #166936 and can be closed since it no new failures have been reported since this was merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
failed-test A test failure on a tracked branch, potentially flaky-test Team:Security Team focused on: Auth, Users, Roles, Spaces, Audit Logging, and more!
Projects
None yet
Development

No branches or pull requests

7 participants