-
Notifications
You must be signed in to change notification settings - Fork 14
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
Running ES service causes issues #11
Comments
Thanks for raising this @kendaleiv By default the nodes public MyTestCluster() : base(new XunitClusterConfiguration("6.2.0")
{
StartingPortNumber = 9201
})
{
} I'm inclined to keep it this way rather than trying to do something clever, @codebrain @russcam thoughts? |
I would be inclined to leave it the way it currently is, otherwise we'd have to start inspecting the local environment to determine available ports and that seems like overkill at this stage. |
@Mpdreamz Setting |
However, setting it like public MyTestCluster() : base(new XunitClusterConfiguration("6.2.0") { StartingPortNumber = 9251 }) does work. |
This is somewhat expected as everything materializes in the constructor chaining. It oughta be a constructor argument really :) Are you already using any of the code in this repository @kendaleiv ? |
Yeah, we moved to this from https://github.com/poulfoged/Elasticsearch-Inside. I understand this project is currently prerelease. 😃 |
On Windows 10 with the
elasticsearch-service-x64
version 6.2.4 running I'm unable to getElastic.Xunit.ExampleMinimal
to work as expected. However, with the service stopped it works great.I'm guessing this is related:
The text was updated successfully, but these errors were encountered: