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

[FAILS ON MKI] Serverless Search Functional Tests - Common Group 1.x-pack/test_serverless/functional/test_suites/common/management/data_views/_edit_field·ts #180568

Closed
wayneseymour opened this issue Apr 11, 2024 · 4 comments
Labels
failed-test A test failure on a tracked branch, potentially flaky-test impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. Team:DataDiscovery Discover App Team (Document Explorer, Saved Search, Surrounding documents, Graph)
Projects

Comments

@wayneseymour
Copy link
Member

wayneseymour commented Apr 11, 2024

x-pack/test_serverless/functional/test_suites/common/management/data_views/_edit_field.ts is failing on MKI runs, introduced in #164656

x-pack/test_serverless/functional/test_suites/common/management/data_views/_edit_field.ts error(s):
1.
Screenshot 2024-04-11 at 12 27 44

Error: retry.tryForTime reached timeout 5000 ms
Error: expected 'png' to equal 'css'
    at Assertion.assert (expect.js:100:11)
    at Assertion.apply (expect.js:227:8)
    at Assertion.be (expect.js:69:22)
    at _edit_field.ts:39:34
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at runAttempt (retry_for_success.ts:29:15)
    at retryForSuccess (retry_for_success.ts:98:21)
    at RetryService.tryForTime (retry.ts:37:12)
    at Context. (_edit_field.ts:37:9)
    at Object.apply (wrap_function.js:73:16)
    at onFailure (retry_for_success.ts:17:9)
    at retryForSuccess (retry_for_success.ts:84:7)
    at RetryService.tryForTime (retry.ts:37:12)
    at Context. (_edit_field.ts:37:9)
    at Object.apply (wrap_function.js:73:16)

Screenshot 2024-04-11 at 12 28 40

ElementNotInteractableError: element not interactable
  (Session info: chrome=123.0.6312.105)
    at Object.throwDecodedError (node_modules/selenium-webdriver/lib/error.js:521:15)
    at parseHttpResponse (node_modules/selenium-webdriver/lib/http.js:510:13)
    at Executor.execute (node_modules/selenium-webdriver/lib/http.js:443:28)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at Task.exec (prevent_parallel_calls.ts:28:20) {
  remoteStacktrace: '#0 0x562a8e723863 \n' +
    '#1 0x562a8e419717 \n' +
    '#2 0x562a8e45e70f \n' +
    '#3 0x562a8e45cb60 \n' +
    '#4 0x562a8e4865a2 \n' +
    '#5 0x562a8e458e98 \n' +
    '#6 0x562a8e48676e \n' +
    '#7 0x562a8e4a4c19 \n' +
    '#8 0x562a8e486343 \n' +
    '#9 0x562a8e457593 \n' +
    '#10 0x562a8e457f5e \n' +
    '#11 0x562a8e6e784b \n' +
    '#12 0x562a8e6eb7a5 \n' +
    '#13 0x562a8e6d5571 \n' +
    '#14 0x562a8e6ec332 \n' +
    '#15 0x562a8e6ba87f \n' +
    '#16 0x562a8e712728 \n' +
    '#17 0x562a8e7128fb \n' +
    '#18 0x562a8e7229b4 \n' +
    '#19 0x7f22cd422134 \n'
}
@wayneseymour wayneseymour added Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. Team:DataDiscovery Discover App Team (Document Explorer, Saved Search, Surrounding documents, Graph) labels Apr 11, 2024
@elasticmachine
Copy link
Contributor

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

@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-data-discovery (Team:DataDiscovery)

@kibanamachine kibanamachine added this to Inbox in Discover Apr 11, 2024
wayneseymour added a commit to wayneseymour/kibana that referenced this issue Apr 11, 2024
@wayneseymour wayneseymour removed the Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more label Apr 11, 2024
@wayneseymour wayneseymour changed the title fails on MKI: 2 suites fails on MKI: Serverless Search Functional Tests - Common Group 1.x-pack/test_serverless/functional/test_suites/common/management/data_views/_edit_field·ts Apr 11, 2024
wayneseymour added a commit that referenced this issue Apr 12, 2024
….x-pack/test_serverless/functional/test_suites/common/management/data_views/_edit_field·ts (#180569)

See #180568
mattkime added a commit that referenced this issue May 9, 2024
…less compatible (#181349)

## Summary

Change data import / export method so test works in MKI environment.

Closes #171479 and
#180568

Verified by running functional test runner run locally against MKI
environment.
@wayneseymour wayneseymour changed the title fails on MKI: Serverless Search Functional Tests - Common Group 1.x-pack/test_serverless/functional/test_suites/common/management/data_views/_edit_field·ts [FAILS ON MKI]: Serverless Search Functional Tests - Common Group 1.x-pack/test_serverless/functional/test_suites/common/management/data_views/_edit_field·ts May 24, 2024
@wayneseymour wayneseymour added the failed-test A test failure on a tracked branch, potentially flaky-test label May 24, 2024
@wayneseymour wayneseymour changed the title [FAILS ON MKI]: Serverless Search Functional Tests - Common Group 1.x-pack/test_serverless/functional/test_suites/common/management/data_views/_edit_field·ts [FAILS ON MKI] Serverless Search Functional Tests - Common Group 1.x-pack/test_serverless/functional/test_suites/common/management/data_views/_edit_field·ts May 24, 2024
@kertal
Copy link
Member

kertal commented May 28, 2024

@mattkime wasn't that closed in #1831349 and it's just not closed because in the description it was mentioned as Closes #171479 and #180568, because then GitHub just thinks the #171479 was closed. In this case it would need to be written like

closes #171479, closes #180568

to work as expected

@davismcphee
Copy link
Contributor

Yes it looks like this was fixed by #181349, and I confirmed it no longer has the failsOnMKI tag in main. I'm going to close this issue as completed now. @mattkime please reopen if I'm missing something here.

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 impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. Team:DataDiscovery Discover App Team (Document Explorer, Saved Search, Surrounding documents, Graph)
Projects
No open projects
Development

No branches or pull requests

5 participants