Closed jmisur closed 11 years ago
Correction: 3rd run was also successful, so it happened only during first run when the dependencies were downloaded.
I haven't seen this kind of behaviour before, although I always run integration tests with the maven-failsafe-plugin instead of the maven-surefire-plugin (I don't see why this would make any difference though). It looks like the mongo server has received an instruction to shut down.
Are you running any kind of parallel build? If so, is it possible that you have parallel instances of the plugin sharing the same port? This could also occur if you run multiple separate maven builds (if the same mongo port is used).
It wasn't parallel build for sure, because it run just for the first time only on one branch. I will try to use another plugin, however the problem didn't occur anymore, so this ticket is effectively invalid until it will happen to somebody again. Maybe just one of a kind coincidence.
Okay I'll close the issue for now. I think something on your system sent mongo an instruction to shutdown.
Hi, I just tried out this plugin and it's cool! However, sometimes I got this error:
First it occured during first run of the plugin, then it ran successfully, then 3rd run also failed. Nothing was changed in between, seems like random behavior. My tests are plain simple read/write, nothing special.
My maven config: