-
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 Fleet API Integration Tests.x-pack/test/fleet_api_integration/apis/integrations/inputs_with_standalone_docker_agent·ts - Fleet Endpoints Integrations inputs_with_standalone_docker_agent "before all" hook for "generate a valid config for standalone agents" #184681
Comments
Pinging @elastic/fleet (Team:Fleet) |
@nchaulet - I think maybe we need retries for spinning up this docker container? Sometimes the elastic docker registry 502's. We have the same problem in FTR tests. |
Looks like the flakyness was in calling the artificat API (retrieving elastic-agent docker image version) we probably can add some retry to that request to start. Or maybe have a fixed version |
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 |
Skipped. main: 2194f85 |
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 |
/skip |
Skipped main: 3f3a842 |
Missing docker image for elastic-agent: docker.elastic.co/beats/elastic-agent:8.15.0 |
New failure: kibana-on-merge - main |
New failure: kibana-on-merge - main |
/skip edit: missed the skip above, whoops. |
Skipped main: 7968b14 |
New failure: kibana-elasticsearch-snapshot-verify - main |
No failures since July. I think this is fixed by the Linked PR we just had a single failure after the fact. |
A test failed on a tracked branch
First failure: kibana-on-merge - main
The text was updated successfully, but these errors were encountered: