Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Cannot Reproduce
-
2.13
-
None
-
None
-
Ubuntu 12.04. OpenJDK 7u9.
Description
We have a multi-module Maven project. One of the modules has the following Surefire configuration:
<plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-surefire-plugin</artifactId> <configuration> <parallel>classes</parallel> <runOrder>random</runOrder> <threadCount>1</threadCount> <forkedProcessTimeoutInSeconds>300</forkedProcessTimeoutInSeconds> </configuration> </plugin>
Notice the 300s timeout. We've seen multiple instances where the build succeeds even if the tests time out. Here's an example:
[INFO] Reactor Summary: [INFO] [INFO] Project 1 ......................................... SUCCESS [4.742s] [INFO] Project 2 ......................................... SUCCESS [5:15.220s]
Notice that Project 2 (which had the 300s timeout) above has run > 5 min. Earlier, in the log we see this:
mojoSucceeded org.apache.maven.plugins:maven-surefire-plugin:2.13(default-test) [ERROR] There was a timeout or other error in the fork [JENKINS] Recording test results projectSucceeded <project 2 details>
So clearly Maven did hit a timeout and yet succeeded the build. I'm happy to provide any other information about our setup. I don't have an isolated, reproducible test case yet however.