After upgrading to Kotest 5.0.0 (from 4.6.3) I'm s...
# kotests
Sebastian Schuberth
11/27/2021, 2:36 PMAfter upgrading to Kotest 5.0.0 (from 4.6.3) I'm seeing some unit test fail that use Wiremock to start / stop a server in
beforeSpec {}afterSpec {}Sebastian Schuberth
11/27/2021, 2:41 PMSebastian Schuberth
11/27/2021, 2:44 PMThe issue apparently cannot be reproduced when just running the single test on its own; it only appears when also running other tests that use Wiremock.
Sebastian Schuberth
11/27/2021, 2:45 PMTo reproduce, checkout https://github.com/oss-review-toolkit/ort/tree/kotest-upgrade and run
./gradlew :advisor:testb
Big Chungus
11/27/2021, 2:46 PMSmells like some leaking race condition.
Big Chungus
11/27/2021, 2:47 PMOr maybe your mocks are not cleaned up from other tests. Are you using shared instance of wiremock for all your tests?
s
Sebastian Schuberth
11/27/2021, 2:54 PMEach spec uses its own
WireMockServere
Emil Kantis
11/27/2021, 3:29 PMIs it always failing with connecting to port 8080? Your wiremock server says it should use a dynamic port, so not sure where the 8080 comes from?
s
Sebastian Schuberth
11/27/2021, 3:38 PMGood catch about the 8080, it actually should be a random port...
Sebastian Schuberth
11/27/2021, 5:16 PMLooks like calling
configureFor()beforeTest()beforeSpec()2 Views