-
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 X-Pack UI Functional Tests.x-pack/test/functional/apps/canvas/custom_elements·ts - Canvas app custom elements deletes custom element when prompted #63004
Comments
Pinging @elastic/kibana-test-triage (failed-test) |
New failure: Jenkins Build |
Pinging @elastic/kibana-canvas (Team:Canvas) |
New failure: Jenkins Build |
New failure: Jenkins Build |
New failure: Jenkins Build |
New failure: Jenkins Build |
We skipped this suite when skipping for #62927 |
New failure: Jenkins Build |
1 similar comment
New failure: Jenkins Build |
New failure: Jenkins Build |
New failure: Jenkins Build |
New failure: Jenkins Build |
1 similar comment
New failure: Jenkins Build |
New failure: Jenkins Build |
New failure: Jenkins Build |
New failure: Jenkins Build |
New failure: Jenkins Build |
New failure: Jenkins Build |
Skip from #62927 was backported to keep this from continually failing 7.7 and 7.6 |
@cqliu1 mind if I ask what the version labels are for? This failed in 7.8 just now: https://kibana-ci.elastic.co/job/elasticsearch+snapshots+verify/659/testReport/junit/Chrome%20X-Pack%20UI%20Functional%20Tests/x-pack_test_functional_apps_canvas_custom_elements%C2%B7ts/Kibana_Pipeline___kibana_xpack_agent___Canvas_app_custom_elements_deletes_custom_element_when_prompted/ |
I added the labels to keep track which versions a fix for these tests would need to be backported to. I thought this test was fixed in 7.8, but I'll keep investigating the failure and work on a fix for 7.8. |
Not skipping the test unless it fails more, but it failed on 7.9/7.x as well: https://kibana-ci.elastic.co/job/elasticsearch+snapshots+verify/726/execution/node/320/log/?consoleFull |
New failure: Jenkins Build |
New failure: Jenkins Build |
Closing this issue. Looks like it got reopened by a failure on a branch where it was not backported. It's not skipped on main anymore and we have not seen any failures in over a year. |
A test failed on a tracked branch
First failure: Jenkins Build
The text was updated successfully, but these errors were encountered: