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_with_es_ssl/apps/triggers_actions_ui/connectors·ts - Actions and Triggers app Connectors should test a connector and display a successful result #88796
Comments
New failure: Jenkins Build |
Here is the error I saw in the build log:
Looks like it failed because the action failed (and the test is for the UI when the action. succeeds:
|
New failure: Jenkins Build |
Pinging @elastic/kibana-alerting-services (Team:Alerting Services) |
New failure: Jenkins Build |
1 similar comment
New failure: Jenkins Build |
New failure: Jenkins Build |
New failure: Jenkins Build |
Huh, did ES change so that indices must have mappings now? If so, we should probably set the mappings when we create the connector, since it appears the index is always going to be a new index, given the connector generated (connectorName and indexName are UUID-based): kibana/x-pack/test/functional_with_es_ssl/apps/triggers_actions_ui/connectors.ts Lines 281 to 292 in 7297cc3
|
Nope. I managed to reproduce locally - the UI driver sometime selects the wrong index in the ComboBox. |
New failure: CI Build - 7.16 |
New failure: CI Build - 8.0 |
New failure: CI Build - 7.17 |
New failure: CI Build - main |
New failure: CI Build - 8.0 |
New failure: CI Build - main |
New failure: CI Build - 7.17 |
A test failed on a tracked branch
First failure: Jenkins Build
The text was updated successfully, but these errors were encountered: