-
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: X-Pack Endpoint Functional Tests.x-pack/test/functional_endpoint/apps/endpoint/policy_list·ts - endpoint When on the Endpoint Policy List and policies exists "before all" hook for "should show policy on the list" #66579
Comments
New failure: Jenkins Build |
Pinging @elastic/kibana-test-triage (failed-test) |
New failure: Jenkins Build |
1 similar comment
New failure: Jenkins Build |
Pinging @elastic/endpoint-app-team (Feature:Endpoint) |
New failure: Jenkins Build |
1 similar comment
New failure: Jenkins Build |
New failure: Jenkins Build |
Hi @spalger do you know if the Kibana startup logs are capture as part of a build? I'm looking at this Jenkins job - https://kibana-ci.elastic.co/job/elastic+kibana+master/5155/testReport/ - and the stack trace does not provide much as to why a given API call caused a HTTP 500. I wanted to see if the startup of kibana generated any errors for the x-pack Ingest plugin. |
Yeah, it doesn't show any errors but you can find the logs at https://kibana-ci.elastic.co/job/elastic+kibana+master/5155/execution/node/608/log/?consoleFull. The Kibana server is started outside of the test executor so its logs are not associated with the test specifically. Here are the startup logs from the last failure:
|
New failure: Jenkins Build |
1 similar comment
New failure: Jenkins Build |
Pinging @elastic/endpoint-management (Team:Endpoint Management) |
New failure: Jenkins Build |
This should be fixed now. Closing. |
A test failed on a tracked branch
First failure: Jenkins Build
The text was updated successfully, but these errors were encountered: