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.

Sign up for GitHub

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

Jump to bottom

Failing test: Chrome X-Pack UI Functional Tests.x-pack/test/functional/apps/index_management/data_streams_tab/data_streams_tab·ts - Index Management app Index Management: data streams tab Data streams tab Modify data streams index mode allows to upgrade data stream from time series to logsdb index mode #205412

Open
kibanamachine opened this issue Jan 2, 2025 · 3 comments · May be fixed by #205485
Open

Failing test: Chrome X-Pack UI Functional Tests.x-pack/test/functional/apps/index_management/data_streams_tab/data_streams_tab·ts - Index Management app Index Management: data streams tab Data streams tab Modify data streams index mode allows to upgrade data stream from time series to logsdb index mode #205412

kibanamachine opened this issue Jan 2, 2025 · 3 comments · May be fixed by #205485
Labels
failed-test A test failure on a tracked branch, potentially flaky-test Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more

Comments

@kibanamachine
Copy link
Contributor

kibanamachine commented Jan 2, 2025 •
edited
Loading

A test failed on a tracked branch

Error: retry.try reached timeout 120000 ms
Error: retry.try reached timeout 120000 ms
TimeoutError: Waiting for element to be located By(css selector, [data-test-subj="kibanaCodeEditor"])
Wait timed out after 10011ms
    at /opt/buildkite-agent/builds/bk-agent-prod-gcp-1735833845797519157/elastic/kibana-on-merge/kibana/node_modules/selenium-webdriver/lib/webdriver.js:928: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 Proxy.clickByCssSelector (find.ts:420:5)
    at TestSubjects.click (test_subjects.ts:169:5)
    at test_subjects.ts:278:7
    at runAttempt (retry_for_success.ts:30:15)
    at retryForSuccess (retry_for_success.ts:99:21)
    at RetryService.try (retry.ts:52:12)
    at TestSubjects.setValue (test_subjects.ts:275:12)
    at Context.<anonymous> (data_streams_tab.ts:363:9)
    at Object.apply (wrap_function.js:74:16)
    at onFailure (retry_for_success.ts:18:9)
    at retryForSuccess (retry_for_success.ts:85:7)
    at RetryService.try (retry.ts:52:12)
    at TestSubjects.setValue (test_subjects.ts:275:12)
    at Context.<anonymous> (data_streams_tab.ts:363:9)
    at Object.apply (wrap_function.js:74:16)

First failure: kibana-on-merge - main
@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label Jan 2, 2025
@botelastic botelastic bot added the needs-team Issues missing a team label label Jan 2, 2025
@kibanamachine kibanamachine added the Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more label Jan 2, 2025
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-management (Team:Kibana Management)

@botelastic botelastic bot removed the needs-team Issues missing a team label label Jan 2, 2025
@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - 8.x

@SoniaSanzV SoniaSanzV linked a pull request Jan 3, 2025 that will close this issue
Open
@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - 8.x

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
failed-test A test failure on a tracked branch, potentially flaky-test Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add waitUntilLoadingHasFinished in failing tests SoniaSanzV/kibana
2 participants
@elasticmachine @kibanamachine