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: Chrome X-Pack UI Functional Tests with ES SSL - Cases - group 2.x-pack/test/functional_with_es_ssl/apps/cases/group2/attachment_framework·ts - Cases Attachment framework Attachment hooks Modal attaches correctly #157642

Closed
kibanamachine opened this issue May 12, 2023 · 9 comments · Fixed by #190602
Assignees
Labels
failed-test A test failure on a tracked branch, potentially flaky-test Feature:Cases Cases feature Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@kibanamachine
Copy link
Contributor

kibanamachine commented May 12, 2023

A test failed on a tracked branch

Error: retry.try timeout: TimeoutError: Waiting for element to be located By(css selector, [data-test-subj="case-fixture-attach-to-existing-case"])
Wait timed out after 10018ms
    at /home/buildkite-agent/builds/kb-n2-4-spot-e9a94b5d04746cd0/elastic/kibana-on-merge/kibana/node_modules/selenium-webdriver/lib/webdriver.js:929:17
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96: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 Proxy.clickByCssSelector (find.ts:407:5)
    at TestSubjects.click (test_subjects.ts:164:5)
    at CommonPageObject.clickAndValidate (common_page.ts:514:5)
    at openModal (attachment_framework.ts:283:11)
    at Context.<anonymous> (attachment_framework.ts:337:13)
    at Object.apply (wrap_function.js:73:16)

First failure: CI Build - 8.8

@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label May 12, 2023
@botelastic botelastic bot added the needs-team Issues missing a team label label May 12, 2023
@kibanamachine kibanamachine added the Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) label May 12, 2023
@elasticmachine
Copy link
Contributor

Pinging @elastic/response-ops (Team:ResponseOps)

@botelastic botelastic bot removed the needs-team Issues missing a team label label May 12, 2023
@cnasikas
Copy link
Member

Closing as it was introduced by https://github.com/elastic/kibana-buildkite/pull/82

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@cnasikas cnasikas added the Feature:Cases Cases feature label Jun 13, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/response-ops-cases (Feature:Cases)

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@kibanamachine
Copy link
Contributor Author

New failure: kibana-on-merge - main

@mistic
Copy link
Member

mistic commented Jun 19, 2024

Skipped.

main: 2d6484d

seanrathier pushed a commit to seanrathier/kibana that referenced this issue Jun 21, 2024
@guskovaue guskovaue self-assigned this Aug 15, 2024
@guskovaue guskovaue linked a pull request Aug 15, 2024 that will close this issue
1 task
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 Feature:Cases Cases feature Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants