elastic / kibana

Your window into the Elastic Stack
https://www.elastic.co/products/kibana
Other
19.67k stars 8.23k forks source link

[FLAKY ON MKI] `x-pack/test_serverless/functional/test_suites/common/management/data_views/_edit_field.ts` #200869

Open wayneseymour opened 2 days ago

wayneseymour commented 2 days ago

Summary

2 Tests failing once so far, on mki.

Config

x-pack/test_serverless/functional/test_suites/observability/common_configs/config.group1.ts

Test 1

Serverless Common UI - Management Data View Management edit field field preview should show preview for fields in _source

Error message

Error: retry.tryForTime reached timeout 5000 ms
Error: Expected previewText to eql [css], but got: [png]
    at Assertion.assert (expect.js:100:11)
    at Assertion.eql (expect.js:244:8)
    at settings_page.ts:1073:30
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at runAttempt (retry_for_success.ts:30:15)
    at retryForSuccess (retry_for_success.ts:99:21)
    at RetryService.tryForTime (retry.ts:38:12)
    at SettingsPageObject.changeAndValidateFieldFormat (settings_page.ts:1071:5)
    at Context. (_edit_field.ts:33:9)
    at Object.apply (wrap_function.js:74:16)
    at onFailure (retry_for_success.ts:18:9)
    at retryForSuccess (retry_for_success.ts:85:7)
    at RetryService.tryForTime (retry.ts:38:12)
    at SettingsPageObject.changeAndValidateFieldFormat (settings_page.ts:1071:5)
    at Context. (_edit_field.ts:33:9)
    at Object.apply (wrap_function.js:74:16)

Screenshot

Image

Test 2

Serverless Common UI - Management Data View Management edit field field preview should show preview for fields not in _source

Error message

ElementNotInteractableError: element not interactable
  (Session info: chrome=131.0.6778.69)
    at Object.throwDecodedError (![Image](https://github.com/user-attachments/assets/2bb89e7c-6c74-4bc2-aa59-d73c7f9ce607)
/selenium-webdriver/lib/error.js:521:15)
    at parseHttpResponse (node_modules/selenium-webdriver/lib/http.js:514:13)
    at Executor.execute (node_modules/selenium-webdriver/lib/http.js:446:28)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at Task.exec (prevent_parallel_calls.ts:29:20) {
  remoteStacktrace: '#0 0x577ba28074ca \n' +
    '#1 0x577ba231a47d \n' +
    '#2 0x577ba236370c \n' +
    '#3 0x577ba2361bb7 \n' +
    '#4 0x577ba238d372 \n' +
    '#5 0x577ba235d938 \n' +
    '#6 0x577ba238d53e \n' +
    '#7 0x577ba23abde0 \n' +
    '#8 0x577ba238d113 \n' +
    '#9 0x577ba235bbe0 \n' +
    '#10 0x577ba235cbbe \n' +
    '#11 0x577ba27d3e4b \n' +
    '#12 0x577ba27d7de2 \n' +
    '#13 0x577ba27c0d2c \n' +
    '#14 0x577ba27d8957 \n' +
    '#15 0x577ba27a64bf \n' +
    '#16 0x577ba27f6348 \n' +
    '#17 0x577ba27f6510 \n' +
    '#18 0x577ba2806346 \n' +
    '#19 0x786089b651c4 \n'
}

Screenshot

Image

Developer Notes

from @davismcphee

I think ElementNotInteractableError: element not interactable is a red herring, and the second failure only occurs because after the first failure, the flyout is left open. so the element we are attempting to click is obscured by it and we get the “not interactable” error. the issue causing the first failure Expected previewText to eql [css], but got: [png] looks to be that the flyout occasionally opens to a document other than the one we’re expecting. I see AVo_PUMjeg4e7W9DbxTE in the screenshot, but we’re expecting AVo_PUMjeg4e7W9DbxTD (“D” vs “E” at the end of the ID). I’m unsure why this would be other than possibly something in ingestion occasionally causes a different doc to be returned by default? I believe it’s unrelated to what we’re actually testing though, so one option would be to manually set the Document ID field to AVo_PUMjeg4e7W9DbxTD before checking the value to ensure we’re looking at the right doc.

elasticmachine commented 2 days ago

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