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: Accessibility Tests.test/accessibility/apps/filter_panel·ts - a11y tests using flights sample data Filter panel a11y test on invert inclusion of all filters view #140244

Closed
kibanamachine opened this issue Sep 8, 2022 · 4 comments
Assignees
Labels
failed-test A test failure on a tracked branch, potentially flaky-test Team:QA Team label for QA Team

Comments

@kibanamachine
Copy link
Contributor

A test failed on a tracked branch

Error: retry.try timeout: TimeoutError: Waiting for element to be located By(css selector, [data-test-subj="filter-sets-applyToAllFilters"])
Wait timed out after 10039ms
    at /var/lib/buildkite-agent/builds/kb-n2-4-spot-970578fe5436e432/elastic/kibana-on-merge/kibana/node_modules/selenium-webdriver/lib/webdriver.js:906:17
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at onFailure (test/common/services/retry/retry_for_success.ts:17:9)
    at retryForSuccess (test/common/services/retry/retry_for_success.ts:59:13)
    at RetryService.try (test/common/services/retry/retry.ts:31:12)
    at Proxy.clickByCssSelector (test/functional/services/common/find.ts:368:5)
    at TestSubjects.click (test/functional/services/common/test_subjects.ts:104:5)
    at Context.<anonymous> (test/accessibility/apps/filter_panel.ts:79:7)
    at Object.apply (node_modules/@kbn/test/target_node/functional_test_runner/lib/mocha/wrap_function.js:87:16)

First failure: CI Build - 8.4

@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label Sep 8, 2022
@botelastic botelastic bot added the needs-team Issues missing a team label label Sep 8, 2022
@jsanz
Copy link
Member

jsanz commented Sep 8, 2022

@bhavyarm should this and #140248 failed tests be assigned to the QA or the Operations team?

@bhavyarm bhavyarm self-assigned this Sep 8, 2022
@bhavyarm
Copy link
Contributor

bhavyarm commented Sep 8, 2022

I am working on this right now @jsanz - getting some help from Stratoula. Here is the PR - #139834. Thanks for the ping. Cheers!

@bhavyarm bhavyarm added the Team:QA Team label for QA Team label Sep 8, 2022
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-qa (Team:QA)

@botelastic botelastic bot removed the needs-team Issues missing a team label label Sep 8, 2022
@bhavyarm
Copy link
Contributor

Closed by #139834

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:QA Team label for QA Team
Projects
None yet
Development

No branches or pull requests

4 participants