[ci] skip tests that fail on chrome 128+ #192830
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
delanni
changed the title
delanni
force-pushed
the
skip-tests-failing-on-chrome-next
branch
from
6e2fdb8 to
d345565
Compare
delanni
added
release_note:skip
|
@elastic/kibana-visualizations - could you also give an approval and a keepsake item your backlog to adjust these after we roll out the current chrome? |
💛 Build succeeded, but was flaky
Failed CI StepsMetrics [docs]
History
To update your PR or re-run it, just comment with: |
dej611
approved these changes
Sep 16, 2024
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Sep 16, 2024
## Summary Currently `google-chrome-stable` is pinned to `v127.x.x` as with `v128.x.x` we get a few FTR breakages (some of them on visual inaccuracies, some other). We'd like to unpin chrome, and move on to 128, and start fixing these test failures. So we're skipping the failures temporarily, bumping chrome to 128, then allow for unskipping and fixing these. (cherry picked from commit f458714)
💔 Some backports could not be created
Note: Successful backport PRs will be merged automatically after passing CI. Manual backportTo create the backport manually run: Questions ?Please refer to the Backport tool documentation |
kibanamachine
added a commit
that referenced
this pull request
Sep 16, 2024
# Backport This will backport the following commits from `main` to `8.x`: - [[ci] skip tests that fail on chrome 128+ (#192830)](#192830) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Alex Szabo","email":"[email protected]"},"sourceCommit":{"committedDate":"2024-09-16T13:18:49Z","message":"[ci] skip tests that fail on chrome 128+ (#192830)\n\n## Summary\r\nCurrently `google-chrome-stable` is pinned to `v127.x.x` as with\r\n`v128.x.x` we get a few FTR breakages (some of them on visual\r\ninaccuracies, some other).\r\n\r\nWe'd like to unpin chrome, and move on to 128, and start fixing these\r\ntest failures. So we're skipping the failures temporarily, bumping\r\nchrome to 128, then allow for unskipping and fixing these.","sha":"f4587149987aa21ec9345e887bc7121d75792ea5","branchLabelMapping":{"^v9.0.0$":"main","^v8.16.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:all-open"],"title":"[ci] skip tests that fail on chrome 128+","number":192830,"url":"https://github.com/elastic/kibana/pull/192830","mergeCommit":{"message":"[ci] skip tests that fail on chrome 128+ (#192830)\n\n## Summary\r\nCurrently `google-chrome-stable` is pinned to `v127.x.x` as with\r\n`v128.x.x` we get a few FTR breakages (some of them on visual\r\ninaccuracies, some other).\r\n\r\nWe'd like to unpin chrome, and move on to 128, and start fixing these\r\ntest failures. So we're skipping the failures temporarily, bumping\r\nchrome to 128, then allow for unskipping and fixing these.","sha":"f4587149987aa21ec9345e887bc7121d75792ea5"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/192830","number":192830,"mergeCommit":{"message":"[ci] skip tests that fail on chrome 128+ (#192830)\n\n## Summary\r\nCurrently `google-chrome-stable` is pinned to `v127.x.x` as with\r\n`v128.x.x` we get a few FTR breakages (some of them on visual\r\ninaccuracies, some other).\r\n\r\nWe'd like to unpin chrome, and move on to 128, and start fixing these\r\ntest failures. So we're skipping the failures temporarily, bumping\r\nchrome to 128, then allow for unskipping and fixing these.","sha":"f4587149987aa21ec9345e887bc7121d75792ea5"}}]}] BACKPORT--> Co-authored-by: Alex Szabo <[email protected]>
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
delanni
added a commit
to delanni/kibana
that referenced
this pull request
Sep 20, 2024
## Summary Currently `google-chrome-stable` is pinned to `v127.x.x` as with `v128.x.x` we get a few FTR breakages (some of them on visual inaccuracies, some other). We'd like to unpin chrome, and move on to 128, and start fixing these test failures. So we're skipping the failures temporarily, bumping chrome to 128, then allow for unskipping and fixing these. (cherry picked from commit f458714) # Conflicts: # test/functional/apps/kibana_overview/_analytics.ts # x-pack/test/functional/apps/lens/group6/workspace_size.ts
delanni
added a commit
that referenced
this pull request
Sep 20, 2024
# Backport This will backport the following commits from `main` to `8.15`: - [[ci] skip tests that fail on chrome 128+ (#192830)](#192830) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Alex Szabo","email":"[email protected]"},"sourceCommit":{"committedDate":"2024-09-16T13:18:49Z","message":"[ci] skip tests that fail on chrome 128+ (#192830)\n\n## Summary\r\nCurrently `google-chrome-stable` is pinned to `v127.x.x` as with\r\n`v128.x.x` we get a few FTR breakages (some of them on visual\r\ninaccuracies, some other).\r\n\r\nWe'd like to unpin chrome, and move on to 128, and start fixing these\r\ntest failures. So we're skipping the failures temporarily, bumping\r\nchrome to 128, then allow for unskipping and fixing these.","sha":"f4587149987aa21ec9345e887bc7121d75792ea5","branchLabelMapping":{"^v9.0.0$":"main","^v8.16.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:all-open","v8.16.0"],"number":192830,"url":"https://github.com/elastic/kibana/pull/192830","mergeCommit":{"message":"[ci] skip tests that fail on chrome 128+ (#192830)\n\n## Summary\r\nCurrently `google-chrome-stable` is pinned to `v127.x.x` as with\r\n`v128.x.x` we get a few FTR breakages (some of them on visual\r\ninaccuracies, some other).\r\n\r\nWe'd like to unpin chrome, and move on to 128, and start fixing these\r\ntest failures. So we're skipping the failures temporarily, bumping\r\nchrome to 128, then allow for unskipping and fixing these.","sha":"f4587149987aa21ec9345e887bc7121d75792ea5"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","labelRegex":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/192830","number":192830,"mergeCommit":{"message":"[ci] skip tests that fail on chrome 128+ (#192830)\n\n## Summary\r\nCurrently `google-chrome-stable` is pinned to `v127.x.x` as with\r\n`v128.x.x` we get a few FTR breakages (some of them on visual\r\ninaccuracies, some other).\r\n\r\nWe'd like to unpin chrome, and move on to 128, and start fixing these\r\ntest failures. So we're skipping the failures temporarily, bumping\r\nchrome to 128, then allow for unskipping and fixing these.","sha":"f4587149987aa21ec9345e887bc7121d75792ea5"}},{"branch":"8.x","label":"v8.16.0","labelRegex":"^v8.16.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/193012","number":193012,"state":"MERGED","mergeCommit":{"sha":"612e5780f66598d54d6af5dc7b4b21c294beea39","message":"[8.x] [ci] skip tests that fail on chrome 128+ (#192830) (#193012)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.x`:\n- [[ci] skip tests that fail on chrome 128+\n(#192830)](https://github.com/elastic/kibana/pull/192830)\n\n<!--- Backport version: 9.4.3 -->\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n<!--BACKPORT [{\"author\":{\"name\":\"Alex\nSzabo\",\"email\":\"[email protected]\"},\"sourceCommit\":{\"committedDate\":\"2024-09-16T13:18:49Z\",\"message\":\"[ci]\nskip tests that fail on chrome 128+ (#192830)\\n\\n## Summary\\r\\nCurrently\n`google-chrome-stable` is pinned to `v127.x.x` as with\\r\\n`v128.x.x` we\nget a few FTR breakages (some of them on visual\\r\\ninaccuracies, some\nother).\\r\\n\\r\\nWe'd like to unpin chrome, and move on to 128, and start\nfixing these\\r\\ntest failures. So we're skipping the failures\ntemporarily, bumping\\r\\nchrome to 128, then allow for unskipping and\nfixing\nthese.\",\"sha\":\"f4587149987aa21ec9345e887bc7121d75792ea5\",\"branchLabelMapping\":{\"^v9.0.0$\":\"main\",\"^v8.16.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"release_note:skip\",\"v9.0.0\",\"backport:all-open\"],\"title\":\"[ci]\nskip tests that fail on chrome\n128+\",\"number\":192830,\"url\":\"https://github.com/elastic/kibana/pull/192830\",\"mergeCommit\":{\"message\":\"[ci]\nskip tests that fail on chrome 128+ (#192830)\\n\\n## Summary\\r\\nCurrently\n`google-chrome-stable` is pinned to `v127.x.x` as with\\r\\n`v128.x.x` we\nget a few FTR breakages (some of them on visual\\r\\ninaccuracies, some\nother).\\r\\n\\r\\nWe'd like to unpin chrome, and move on to 128, and start\nfixing these\\r\\ntest failures. So we're skipping the failures\ntemporarily, bumping\\r\\nchrome to 128, then allow for unskipping and\nfixing\nthese.\",\"sha\":\"f4587149987aa21ec9345e887bc7121d75792ea5\"}},\"sourceBranch\":\"main\",\"suggestedTargetBranches\":[],\"targetPullRequestStates\":[{\"branch\":\"main\",\"label\":\"v9.0.0\",\"branchLabelMappingKey\":\"^v9.0.0$\",\"isSourceBranch\":true,\"state\":\"MERGED\",\"url\":\"https://github.com/elastic/kibana/pull/192830\",\"number\":192830,\"mergeCommit\":{\"message\":\"[ci]\nskip tests that fail on chrome 128+ (#192830)\\n\\n## Summary\\r\\nCurrently\n`google-chrome-stable` is pinned to `v127.x.x` as with\\r\\n`v128.x.x` we\nget a few FTR breakages (some of them on visual\\r\\ninaccuracies, some\nother).\\r\\n\\r\\nWe'd like to unpin chrome, and move on to 128, and start\nfixing these\\r\\ntest failures. So we're skipping the failures\ntemporarily, bumping\\r\\nchrome to 128, then allow for unskipping and\nfixing these.\",\"sha\":\"f4587149987aa21ec9345e887bc7121d75792ea5\"}}]}]\nBACKPORT-->\n\nCo-authored-by: Alex Szabo <[email protected]>"}}]}] BACKPORT-->
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Currently
google-chrome-stableis pinned tov127.x.xas withv128.x.xwe get a few FTR breakages (some of them on visual inaccuracies, some other).We'd like to unpin chrome, and move on to 128, and start fixing these test failures. So we're skipping the failures temporarily, bumping chrome to 128, then allow for unskipping and fixing these.
Relates to: https://github.com/elastic/kibana-operations/issues/199