Skip to content

Conversation

@alpar-t
Copy link
Contributor

@alpar-t alpar-t commented Nov 11, 2019

Relates to #15385.
Hoping to get some insight on CI failures.

Relates to elastic#15385.
Hoping to get some insight on CI failures.
@alpar-t alpar-t added the :Delivery/Build Build or test infrastructure label Nov 11, 2019
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-infra (:Core/Infra/Build)

@alpar-t
Copy link
Contributor Author

alpar-t commented Nov 11, 2019

@elasticmachine update branch

@alpar-t
Copy link
Contributor Author

alpar-t commented Nov 12, 2019

@mark-vieira I'm going to merge this to be able to test these jobs. Will act on any feedback on a new PR.

@alpar-t alpar-t merged commit 77da9c9 into elastic:master Nov 12, 2019
@alpar-t alpar-t deleted the packaging-tests-stall branch November 12, 2019 08:08
alpar-t added a commit that referenced this pull request Nov 12, 2019
Relates to #15385.
Hoping to get some insight on CI failures.
@alpar-t alpar-t added v7.5.0 and removed v7.4.3 labels Nov 12, 2019
alpar-t added a commit that referenced this pull request Nov 12, 2019
Relates to #15385.
Hoping to get some insight on CI failures.
rm(installation.config("elasticsearch.keystore"));

Archives.runElasticsearch(installation, sh);
try {
Copy link
Contributor

Choose a reason for hiding this comment

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

Would it make sense to just bake this into waitForElasticsearch()?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

The pid file will not always be at the same location. We could but it would take significantly more work to make sure we always track the pid file in the installation so we can reliably reference it

Copy link
Contributor

Choose a reason for hiding this comment

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

That's fine. If we expect this to be mostly temporary, or only really helpful for this test, then let's press on as-is.

@mark-vieira mark-vieira added the Team:Delivery Meta label for Delivery team label Nov 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

:Delivery/Build Build or test infrastructure Team:Delivery Meta label for Delivery team v7.5.0 v7.6.0 v8.0.0-alpha1

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants