Failing test: Traces in Discover - Waterfall flyout usage - Open in Discover from child flyout sections navigates to the correct data

[kibanamachine]

A test failed on a tracked branch

Scout Test Details:

Field	Value
Test ID	53f97d0c42b6e9b-287bab24f344d0f
Target	cloud-stateful-classic
Location	src/platform/plugins/shared/discover/test/scout/ui/parallel_tests/traces_experience/waterfall_flyout_usage.spec.ts
Duration	30.49s
Module	discover (plugin)
Config path	src/platform/plugins/shared/discover/test/scout/ui/parallel.playwright.config.ts
Code Owners	elastic/obs-exploration-team

Error: expect(locator).toBeVisible() failed

Locator: locator('[data-test-subj="dscPage"]')
Expected: visible
Timeout: 30000ms
Error: element(s) not found

Call log:
  - Expect "toBeVisible" with timeout 30000ms
  - waiting for locator('[data-test-subj="dscPage"]')

    at Proxy.waitForDiscoverPage (src/platform/packages/shared/kbn-scout/src/playwright/page_objects/discover_app.ts:31:57)
    at Proxy.goto (src/platform/packages/shared/kbn-scout/src/playwright/page_objects/discover_app.ts:25:16)
    at openTraceTimeline (src/platform/plugins/shared/discover/test/scout/ui/parallel_tests/traces_experience/waterfall_flyout_usage.spec.ts:33:3)
    at src/platform/plugins/shared/discover/test/scout/ui/parallel_tests/traces_experience/waterfall_flyout_usage.spec.ts:257:11
    at src/platform/plugins/shared/discover/test/scout/ui/parallel_tests/traces_experience/waterfall_flyout_usage.spec.ts:255:9

First failure: appex-qa-stateful-kibana-scout-tests - main

Failure screenshots are available in the Buildkite HTML report and artifacts.

[elasticmachine]

Pinging @elastic/obs-exploration-team (Team:obs-exploration)

[Bluefinger]

This looks like kibana never is able to finish navigating to Discover. Not sure if there is a "fix" for this other than bumping the timeout up from 30secs to 60secs, but if simply navigating to Discover is causing issues, then this is probably an infra issue rather than the test itself.

[jorgeoliveira117]

Attempting a simply fix in #266190

[jorgeoliveira117]

After some investigation with the @elastic/appex-qa team we're dismissing this failing test as it was most likely just a transient environment issue, in the failure we can see that Kibana was just taking a long time to load.
Also, after this failed test was flagged, there were no more similar failures as seen here