Skip to content

Conversation

@jsoriano
Copy link
Member

@jsoriano jsoriano commented Feb 10, 2025

Errors are ignored in two more cases now: when the status of the stack cannot be obtained, and when using the compose provider, when the elasticsearch service doesn't exist.

This should help on executions of pipeline tests against existing servers using only environment variables on default configuration, what is a common use case according to #2387.

Fixes #2387.

Errors are ignored in two cases more now: when the status of the stack cannot be obtained, and when using the compose provider, when the elasticsearch service doesn't exist. This should help on executions of pipeline tests against existing servers using only environment variables on default configuration.
@jsoriano jsoriano self-assigned this Feb 10, 2025
@elasticmachine
Copy link
Collaborator

elasticmachine commented Feb 10, 2025

💛 Build succeeded, but was flaky

Failed CI Steps

History

cc @jsoriano

Copy link
Contributor

@mrodm mrodm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@jsoriano jsoriano merged commit 79d7596 into elastic:main Feb 11, 2025
3 checks passed
@jsoriano jsoriano deleted the test-pipeline-environment branch February 11, 2025 11:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

3 participants