Skip to content

Fix compilation failure in :qa:vagrant #40083

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

Merged
merged 1 commit into from
Mar 15, 2019

Conversation

davidkyle
Copy link
Member

Looks like a merge fail between #39882 and #39937

I added the test-mute label as the build is broken and this simple change will fix it

@davidkyle davidkyle added :Delivery/Packaging RPM and deb packaging, tar and zip archives, shell and batch scripts v8.0.0 >test-mute Use for PR that only mute tests labels Mar 15, 2019
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-infra

@tvernum tvernum self-requested a review March 15, 2019 09:32
Copy link
Contributor

@tvernum tvernum left a comment

Choose a reason for hiding this comment

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

LGTM, although I don't like abusing test-mute for this (but I have no better suggestion)

@davidkyle
Copy link
Member Author

Thanks Tim

@davidkyle davidkyle merged commit cbd87f7 into elastic:master Mar 15, 2019
@davidkyle davidkyle deleted the fix-packaging-compilation branch March 15, 2019 09:38
andrershov pushed a commit that referenced this pull request Mar 18, 2019
This commit adds cd $ES_HOME to elasticsearch-env and removes it from
elasticsearch. This way, both elasticsearch and elasticsearch-cli are
executed with the working directory set to $ES_HOME. The need for the
fix arose from the following bug:
1. Explicitly set path.data to relative to ES_HOME path in
elasticsearch.yml.
2. Run elasticsearch from any directory. Elasticsearch is able to
correctly start.
3. Stop elasticsearch.
4. Run elasticsearch-node unsafe-bootstrap, not from ES_HOME directory.
It will fail with an exception.
This commit fixes the issue and adds a new test.

This PR fixes the issue and adds a new test.
Also tests >=100 are renamed because alphabetic order does not work for
them.

(cherry picked from commit 2ffc293
with fixes by #40083 and #40118)
@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/Packaging RPM and deb packaging, tar and zip archives, shell and batch scripts Team:Delivery Meta label for Delivery team >test-mute Use for PR that only mute tests v7.0.0-rc1 v8.0.0-alpha1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants