mirror of
https://github.com/elastic/kibana.git
synced 2025-04-24 17:59:23 -04:00
# Backport This will backport the following commits from `main` to `8.8`: - [Update ftr services to handle occasional WebDriverError (#157283)](https://github.com/elastic/kibana/pull/157283) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Dzmitry Lemechko","email":"dzmitry.lemechko@elastic.co"},"sourceCommit":{"committedDate":"2023-05-10T18:00:44Z","message":"Update ftr services to handle occasional WebDriverError (#157283)\n\n## Summary\r\n\r\nStarting with Chrome v113 we noticed that `_area_chart.ts` suite became\r\nflaky #156821 failing with\r\n`WebDriverError: unknown error: unhandled inspector error:\r\n{\"code\":-32000,\"message\":\"No node with given id found\"}`\r\nUpdating chromedriver to v113 did not solve the issue and more tests\r\nstarted to fail with the same error.\r\n\r\nIt happens occasionally when driver returns unhandled error instead of\r\nStaleElementReferenceException. This PR adds the error to the\r\n`RETRY_ON_ERRORS` list, so that FTR can search for the element again and\r\nre-try the action on it:\r\n\r\n```\r\n │ debg getVisibleText: elementId=29C3E81151C86107290DD8F020524333_element_290\r\n │ debg Chromedriver issue #4440, WebElementWrapper.getVisibleText: WebDriverError: unknown error: unhandled inspector error: {\"code\":-32000,\"message\":\"No node with given id found\"}\r\n │ (Session info: chrome=113.0.5672.63)\r\n │ debg current ElementID=29C3E81151C86107290DD8F020524333_element_290\r\n │ debg new ElementID=29C3E81151C86107290DD8F020524333_element_293\r\n │ debg Searching again for the element 'By(css selector, [data-test-subj=\"visEditorInterval\"] + .euiFormErrorText)', 2 attempts left\r\n │ debg getVisibleText: elementId=29C3E81151C86107290DD8F020524333_element_293\r\n └- ✓ pass (1.8s)\r\n```\r\n\r\nThere is no need to use `Retry` service, `WebDriverWrapper.retryCall`\r\nshould handle the issue.\r\n\r\nFlaky test runner 100x for Vis Editor config:\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2236\r\nFlaky test runner 100x for Cases config:\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2237\r\n\r\nAnd 2 more 100x:\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2239\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2237","sha":"7f4ceb1d302cf24411c1b82030b882e87a8616dd","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v8.7.2","v8.9.0","v8.8.1"],"number":157283,"url":"https://github.com/elastic/kibana/pull/157283","mergeCommit":{"message":"Update ftr services to handle occasional WebDriverError (#157283)\n\n## Summary\r\n\r\nStarting with Chrome v113 we noticed that `_area_chart.ts` suite became\r\nflaky #156821 failing with\r\n`WebDriverError: unknown error: unhandled inspector error:\r\n{\"code\":-32000,\"message\":\"No node with given id found\"}`\r\nUpdating chromedriver to v113 did not solve the issue and more tests\r\nstarted to fail with the same error.\r\n\r\nIt happens occasionally when driver returns unhandled error instead of\r\nStaleElementReferenceException. This PR adds the error to the\r\n`RETRY_ON_ERRORS` list, so that FTR can search for the element again and\r\nre-try the action on it:\r\n\r\n```\r\n │ debg getVisibleText: elementId=29C3E81151C86107290DD8F020524333_element_290\r\n │ debg Chromedriver issue #4440, WebElementWrapper.getVisibleText: WebDriverError: unknown error: unhandled inspector error: {\"code\":-32000,\"message\":\"No node with given id found\"}\r\n │ (Session info: chrome=113.0.5672.63)\r\n │ debg current ElementID=29C3E81151C86107290DD8F020524333_element_290\r\n │ debg new ElementID=29C3E81151C86107290DD8F020524333_element_293\r\n │ debg Searching again for the element 'By(css selector, [data-test-subj=\"visEditorInterval\"] + .euiFormErrorText)', 2 attempts left\r\n │ debg getVisibleText: elementId=29C3E81151C86107290DD8F020524333_element_293\r\n └- ✓ pass (1.8s)\r\n```\r\n\r\nThere is no need to use `Retry` service, `WebDriverWrapper.retryCall`\r\nshould handle the issue.\r\n\r\nFlaky test runner 100x for Vis Editor config:\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2236\r\nFlaky test runner 100x for Cases config:\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2237\r\n\r\nAnd 2 more 100x:\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2239\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2237","sha":"7f4ceb1d302cf24411c1b82030b882e87a8616dd"}},"sourceBranch":"main","suggestedTargetBranches":["8.7","8.8"],"targetPullRequestStates":[{"branch":"8.7","label":"v8.7.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/157283","number":157283,"mergeCommit":{"message":"Update ftr services to handle occasional WebDriverError (#157283)\n\n## Summary\r\n\r\nStarting with Chrome v113 we noticed that `_area_chart.ts` suite became\r\nflaky #156821 failing with\r\n`WebDriverError: unknown error: unhandled inspector error:\r\n{\"code\":-32000,\"message\":\"No node with given id found\"}`\r\nUpdating chromedriver to v113 did not solve the issue and more tests\r\nstarted to fail with the same error.\r\n\r\nIt happens occasionally when driver returns unhandled error instead of\r\nStaleElementReferenceException. This PR adds the error to the\r\n`RETRY_ON_ERRORS` list, so that FTR can search for the element again and\r\nre-try the action on it:\r\n\r\n```\r\n │ debg getVisibleText: elementId=29C3E81151C86107290DD8F020524333_element_290\r\n │ debg Chromedriver issue #4440, WebElementWrapper.getVisibleText: WebDriverError: unknown error: unhandled inspector error: {\"code\":-32000,\"message\":\"No node with given id found\"}\r\n │ (Session info: chrome=113.0.5672.63)\r\n │ debg current ElementID=29C3E81151C86107290DD8F020524333_element_290\r\n │ debg new ElementID=29C3E81151C86107290DD8F020524333_element_293\r\n │ debg Searching again for the element 'By(css selector, [data-test-subj=\"visEditorInterval\"] + .euiFormErrorText)', 2 attempts left\r\n │ debg getVisibleText: elementId=29C3E81151C86107290DD8F020524333_element_293\r\n └- ✓ pass (1.8s)\r\n```\r\n\r\nThere is no need to use `Retry` service, `WebDriverWrapper.retryCall`\r\nshould handle the issue.\r\n\r\nFlaky test runner 100x for Vis Editor config:\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2236\r\nFlaky test runner 100x for Cases config:\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2237\r\n\r\nAnd 2 more 100x:\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2239\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2237","sha":"7f4ceb1d302cf24411c1b82030b882e87a8616dd"}},{"branch":"8.8","label":"v8.8.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
---|---|---|
.. | ||
accessibility | ||
analytics | ||
api_integration | ||
common | ||
examples | ||
functional | ||
harden | ||
health_gateway | ||
interactive_setup_api_integration | ||
interactive_setup_functional | ||
interpreter_functional | ||
node_roles_functional | ||
package | ||
plugin_functional | ||
scripts | ||
server_integration | ||
ui_capabilities/newsfeed_err | ||
tsconfig.json |