-
Notifications
You must be signed in to change notification settings - Fork 635
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
test test_no_config fails with custom ES port #843
Comments
Try using |
The code properly recognizes when a given host and port are used. The test is mostly to ensure that defaults are used when things are empty. If I read in the passed host and port, then those defaults would be just as wrong. I'm not sure I can do what you're asking. I will see if I can change the test to behave more like a unit test, even though it's an integration test. In the meanwhile, you can safely ignore this error as it's a false positive. It is doing what it's supposed to do: use localhost and 9200 as the connection criteria if none are provided. |
I'll use an if statement. If |
Right now,I've just commented out the test. The condition to run the test based on the host:port seems like the best solution for this case. Another approach would be to skip the test with something like: |
Thanks |
On gentoo linux we run the curator tests with es on custom port. Test test_no_config fails because without config it tries to connect to port 9200.
How to reproduce:
start ES on port 15000
Curator tries to connect to port 9200
The text was updated successfully, but these errors were encountered: