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

[test-failed]: Chrome UI Functional Tests1.test/functional/apps/discover/_runtime_fields_editor·ts - discover app discover integration with runtime fields editor allows adding custom label to existing fields #112316

Closed
liza-mae opened this issue Sep 15, 2021 · 1 comment
Labels
failed-test A test failure on a tracked branch, potentially flaky-test needs-team Issues missing a team label test-cloud

Comments

@liza-mae
Copy link
Contributor

Version: 7.15.0
Class: Chrome UI Functional Tests1.test/functional/apps/discover/_runtime_fields_editor·ts
Stack Trace:

Error: retry.try timeout: Error: retry.try timeout: TimeoutError: Waiting for element to be located By(css selector, [data-test-subj="field-bytes"])
Wait timed out after 10046ms
   at /var/lib/jenkins/workspace/elastic+estf-cloud-kibana-tests/JOB/basicGrp1/TASK/saas_run_kibana_tests/node/ess-testing/ci/cloud/common/build/kibana/node_modules/selenium-webdriver/lib/webdriver.js:842:17
   at processTicksAndRejections (internal/process/task_queues.js:95:5)
   at onFailure (test/common/services/retry/retry_for_success.ts:17:9)
   at retryForSuccess (test/common/services/retry/retry_for_success.ts:57:13)
   at RetryService.try (test/common/services/retry/retry.ts:31:12)
   at Proxy.clickByCssSelector (test/functional/services/common/find.ts:360:5)
   at TestSubjects.click (test/functional/services/common/test_subjects.ts:105:5)
   at /var/lib/jenkins/workspace/elastic+estf-cloud-kibana-tests/JOB/basicGrp1/TASK/saas_run_kibana_tests/node/ess-testing/ci/cloud/common/build/kibana/test/functional/page_objects/discover_page.ts:309:7
   at runAttempt (test/common/services/retry/retry_for_success.ts:27:15)
   at retryForSuccess (test/common/services/retry/retry_for_success.ts:66:21)
   at RetryService.try (test/common/services/retry/retry.ts:31:12)
   at DiscoverPageObject.editField (test/functional/page_objects/discover_page.ts:308:5)
   at Context.<anonymous> (test/functional/apps/discover/_runtime_fields_editor.ts:44:7)
   at Object.apply (node_modules/@kbn/test/target_node/functional_test_runner/lib/mocha/wrap_function.js:87:16)
   at onFailure (test/common/services/retry/retry_for_success.ts:17:9)
   at retryForSuccess (test/common/services/retry/retry_for_success.ts:57:13)
   at RetryService.try (test/common/services/retry/retry.ts:31:12)
   at DiscoverPageObject.editField (test/functional/page_objects/discover_page.ts:308:5)
   at Context.<anonymous> (test/functional/apps/discover/_runtime_fields_editor.ts:44:7)
   at Object.apply (node_modules/@kbn/test/target_node/functional_test_runner/lib/mocha/wrap_function.js:87:16)

Other test failures:

  • discover app discover integration with runtime fields editor allows creation of a new field
  • discover app discover integration with runtime fields editor allows editing of a newly created field
  • discover app discover integration with runtime fields editor allows creation of a new field and use it in a saved search
  • discover app discover integration with runtime fields editor deletes a runtime field
  • discover app discover integration with runtime fields editor doc view includes runtime fields

Test Report: https://internal-ci.elastic.co/view/Stack%20Tests/job/elastic+estf-cloud-kibana-tests/2352/testReport/

@liza-mae liza-mae added failed-test A test failure on a tracked branch, potentially flaky-test test-cloud labels Sep 15, 2021
@botelastic botelastic bot added the needs-team Issues missing a team label label Sep 15, 2021
@liza-mae
Copy link
Contributor Author

Original: #110360 fixed by: #111925, looks like it did not make this BC, closing for now.

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 needs-team Issues missing a team label test-cloud
Projects
None yet
Development

No branches or pull requests

1 participant