Running tests in parallel with Wiremock 3.0.0 triggers random timing/concurrency issues

[henrykuijpers]

Proposal

When upgrading from 2.35.2 to 3.0.0, timing issues have been encountered when running tests in parallel.

Even if no tests are executed containing Wiremock usage, having the dependency active is already enough to cause the issues. It looks like threading and/or race condition.

Reproduction steps

Provide a bunch of tests and include Wiremock 3.0.0. Notice that tests have random failures. Provide Wiremock 2.35.2. Notice that those tests are stable again.

References

No response

[leeturner]

Hi, I don't seem to be able to reproduce this. In your bug report you reference WireMock 3.0.0. By this do you mean specifically this version or do you just mean the 3.x.x releases in general.

If you have an example project I could take a look at that would be awesome and really help me diagnose the issue.

Also, could you let me know which WireMock dependency you are using - is it wiremock standalone or the direct wiremock dependency?

[leeturner]

Hi, we are planning on releasing 3.6.0 this week if possible. If you could come back with any additional information we might be able to look into this before the next release.