-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Failing test: Chrome UI Functional Tests.test/functional/apps/dashboard/group5/embed_mode·ts - dashboard app - group 5 embed mode default URL params renders as expected #163207
Comments
Pinging @elastic/kibana-presentation (Team:Presentation) |
New failure: CI Build - main |
I'm not sure how true this is, but this failure where everything is slightly off from the baseline reminds me a lot of the difference in Kibana rendering that we see when using apple silicon vs Intel. Not sure what to do with this one other than to monitor it for a little while try to upgrade the baseline to the apple silicon version if it continues to fail. |
New failure: CI Build - main |
/skip |
Skipped main: 1d38289 |
New failure: CI Build - main |
Unasigning myself so another engineer with ARM mac can generate a fix. Fix is to unskip test and locally rebuild snapshots. Similar to #163361 |
Closes #163207 ## Summary Since Chrome was updated in the CI environment, our old CI-generated screenshots were outdated - this PR updates the `embed_mode` screenshot tests so that we are once again in sync with the CI environment. For more context, please refer to #160085 ### Checklist - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios ### For maintainers - [ ] This was checked for breaking API changes and was [labeled appropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)
Closes #163207 ## Summary This PR updates the embed mode baseline screenshot so that the failing test can be unskipped. This test is, unfortunately, very fragile because the font rendering is prone to changing between Chrome updates - however, there isn't really a better way of checking for rendering issues, so we'll have to continue just updating the baseline whenever a failure happens 🙈 ### Checklist - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [x] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed: - Flaky test runner: https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/4749 ![image](https://github.com/elastic/kibana/assets/8698078/eeb87dca-4542-4333-af8b-58d07a8c911e) ### For maintainers - [ ] This was checked for breaking API changes and was [labeled appropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)
New failure: kibana-on-merge - main |
New failure: kibana-on-merge - main |
New failure: kibana-on-merge - main |
New failure: kibana-on-merge - main |
New failure: kibana-on-merge - main |
New failure: kibana-on-merge - main |
New failure: kibana-on-merge - main |
New failure: kibana-on-merge - main |
New failure: kibana-on-merge - main |
New failure: kibana-on-merge - main |
New failure: kibana-on-merge - main |
New failure: kibana-on-merge - main |
New failure: kibana-on-merge - main |
New failure: kibana-on-merge - main |
New failure: kibana-on-merge - main |
New failure: kibana-on-merge - main |
New failure: kibana-on-merge - 8.15 |
New failure: kibana-on-merge - 8.15 |
New failure: kibana-elasticsearch-snapshot-verify - 8.15 |
New failure: kibana-elasticsearch-snapshot-verify - 8.15 |
A test failed on a tracked branch
First failure: CI Build - main
The text was updated successfully, but these errors were encountered: