-
-
Notifications
You must be signed in to change notification settings - Fork 200
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
LogEntries not being recorded on subsequent tests #132
Comments
Running on same port will indeed behave wrong, I think that the server is not really shutdown or that the OS does not yet release the port connection from client to server. I've added a test with different ports, and that one is ok. So for now I would suggest not to use the same port, but always random. |
Recently merged pull request addresses this in .NET core; it was not an issue in full framework - 297743a |
Hi, I'm still experiencing a similar problem. When I access the LogEntries collection the first time I'm getting no results. It looks like the LogEntries collection is not updated immediately because after adding |
I'm having the same issue where log entries are coming back as empty, I'm running it on Linux version 4.15.0-202-generic. |
I have also tried removing random porting & I have tried with random porting both fail. |
@Zakashi92 |
Starting WireMock subsequent times on the same port with the same stubs appears to work, but the LogEntries are not recorded meaning you can't verify what was sent to the server.
I first noticed this using xunit in a Dotnet Core Web API project. The above is a simple reproduction using a console app.
EDIT: This is WireMock.Net 1.0.3.16 running on netcoreapp2.0
The text was updated successfully, but these errors were encountered: