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: X-Pack Accessibility Tests.x-pack/test/accessibility/apps/lens·ts - Lens lens #90723

Closed
kibanamachine opened this issue Feb 9, 2021 · 9 comments · Fixed by #91397
Closed

Failing test: X-Pack Accessibility Tests.x-pack/test/accessibility/apps/lens·ts - Lens lens #90723

kibanamachine opened this issue Feb 9, 2021 · 9 comments · Fixed by #91397
Assignees
@flash1293
Labels
failed-test A test failure on a tracked branch, potentially flaky-test Feature:Lens Team:Visualizations Visualization editors, elastic-charts and infrastructure

Comments

@kibanamachine
Copy link
Contributor

kibanamachine commented Feb 9, 2021 •
edited
Loading

A test failed on a tracked branch

Error: retry.tryForTime timeout: Error: retry.try timeout: TimeoutError: Waiting for element to be located By(css selector, [data-test-subj="createVisualizationPromptButton"])
Wait timed out after 10035ms
    at /dev/shm/workspace/kibana/node_modules/selenium-webdriver/lib/webdriver.js:842:17
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
    at onFailure (/dev/shm/workspace/parallel/11/kibana/test/common/services/retry/retry_for_success.ts:17:9)
    at retryForSuccess (/dev/shm/workspace/parallel/11/kibana/test/common/services/retry/retry_for_success.ts:57:13)
    at Retry.try (/dev/shm/workspace/parallel/11/kibana/test/common/services/retry/retry.ts:32:14)
    at Proxy.clickByCssSelector (/dev/shm/workspace/parallel/11/kibana/test/functional/services/common/find.ts:419:7)
    at TestSubjects.click (/dev/shm/workspace/parallel/11/kibana/test/functional/services/common/test_subjects.ts:105:7)
    at /dev/shm/workspace/parallel/11/kibana/test/functional/services/listing_table.ts:195:11
    at runAttempt (/dev/shm/workspace/parallel/11/kibana/test/common/services/retry/retry_for_success.ts:27:15)
    at retryForSuccess (/dev/shm/workspace/parallel/11/kibana/test/common/services/retry/retry_for_success.ts:66:21)
    at Retry.tryForTime (/dev/shm/workspace/parallel/11/kibana/test/common/services/retry/retry.ts:23:14)
    at ListingTable.clickNewButton (/dev/shm/workspace/parallel/11/kibana/test/functional/services/listing_table.ts:186:7)
    at VisualizePage.clickNewVisualization (/dev/shm/workspace/parallel/11/kibana/test/functional/page_objects/visualize_page.ts:55:7)
    at VisualizePage.navigateToNewVisualization (/dev/shm/workspace/parallel/11/kibana/test/functional/page_objects/visualize_page.ts:121:7)
    at Context.<anonymous> (test/accessibility/apps/lens.ts:34:7)
    at Object.apply (/dev/shm/workspace/parallel/11/kibana/packages/kbn-test/src/functional_test_runner/lib/mocha/wrap_function.js:73:16)
    at onFailure (/dev/shm/workspace/parallel/11/kibana/test/common/services/retry/retry_for_success.ts:17:9)
    at retryForSuccess (/dev/shm/workspace/parallel/11/kibana/test/common/services/retry/retry_for_success.ts:57:13)
    at Retry.tryForTime (/dev/shm/workspace/parallel/11/kibana/test/common/services/retry/retry.ts:23:14)
    at ListingTable.clickNewButton (/dev/shm/workspace/parallel/11/kibana/test/functional/services/listing_table.ts:186:7)
    at VisualizePage.clickNewVisualization (/dev/shm/workspace/parallel/11/kibana/test/functional/page_objects/visualize_page.ts:55:7)
    at VisualizePage.navigateToNewVisualization (/dev/shm/workspace/parallel/11/kibana/test/functional/page_objects/visualize_page.ts:121:7)
    at Context.<anonymous> (test/accessibility/apps/lens.ts:34:7)
    at Object.apply (/dev/shm/workspace/parallel/11/kibana/packages/kbn-test/src/functional_test_runner/lib/mocha/wrap_function.js:73:16)

First failure: Jenkins Build
@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label Feb 9, 2021
@mistic mistic added the Team:Visualizations Visualization editors, elastic-charts and infrastructure label Feb 9, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-app (Team:KibanaApp)

@flash1293
Copy link
Contributor

Same as #88927

@flash1293 flash1293 self-assigned this Feb 10, 2021
@flash1293
Copy link
Contributor

I hope #91000 fill fix this one as well

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@flash1293
Copy link
Contributor

As this seems to be pretty unstable right now, I'm going to switch the Lens a11y tests over to the fixture data loaded via es archiver (which seems to work better), in the hope the issue is limited to sample data and not a11y tests in general. This will buy us some time to investigate and fix #91000

@flash1293 flash1293 mentioned this issue Feb 15, 2021
Merged
@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine kibanamachine reopened this Jun 25, 2021
@flash1293
Copy link
Contributor

Good old Failed to load resource: net::ERR_NETWORK_CHANGED

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@flash1293 flash1293

Labels
failed-test A test failure on a tracked branch, potentially flaky-test Feature:Lens Team:Visualizations Visualization editors, elastic-charts and infrastructure
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[Lens] Switch to es archiver fixtures instead of sample data flash1293/kibana
4 participants
@flash1293 @mistic @elasticmachine @kibanamachine