-
Notifications
You must be signed in to change notification settings - Fork 25.6k
Create a thread dump if ES fails to start in packaging tests #48932
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
Conversation
Relates to elastic#15385. Hoping to get some insight on CI failures.
|
Pinging @elastic/es-core-infra (:Core/Infra/Build) |
|
@elasticmachine update branch |
|
@mark-vieira I'm going to merge this to be able to test these jobs. Will act on any feedback on a new PR. |
Relates to #15385. Hoping to get some insight on CI failures.
Relates to #15385. Hoping to get some insight on CI failures.
| rm(installation.config("elasticsearch.keystore")); | ||
|
|
||
| Archives.runElasticsearch(installation, sh); | ||
| try { |
There was a problem hiding this comment.
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()?
There was a problem hiding this comment.
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
There was a problem hiding this comment.
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.
Relates to #15385.
Hoping to get some insight on CI failures.