Configuring the threadCount globally in the jdbc pom fixes the issues I'm experiencing. I'm
still not sure why it makes the difference, as the integration tests should already have it
configured, and the unit tests should not interfere, but the fact is that this is fixing the
mentioned issues. Here is the diff. Worth adding it to the PR?
```diff
diff --git a/jdbc/pom.xml b/jdbc/pom.xml
index 4408891..da9e43c 100644
--- a/jdbc/pom.xml
+++ b/jdbc/pom.xml
@@ -125,6 +125,9 @@
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
+ <configuration>
+ <threadCount>1</threadCount>
+ </configuration>
<executions>
<execution>
<id>integration</id>
```
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/217#issuecomment-151814871
|