Diwaker Gupta created SUREFIRE-953:
--------------------------------------
Summary: Multi-module build succeeds even if tests time out
Key: SUREFIRE-953
URL: https://jira.codehaus.org/browse/SUREFIRE-953
Project: Maven Surefire
Issue Type: Bug
Components: Junit 4.x support, Maven Surefire Plugin
Affects Versions: 2.13
Environment: Ubuntu 12.04. OpenJDK 7u9.
Reporter: Diwaker Gupta
We have a multi-module Maven project. One of the modules has the following
Surefire configuration:
{noformat}
<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>
{noformat}
Notice the 300s timeout. We've seen multiple instances where the build succeeds
even if the tests time out. Here's an example:
{noformat}
[INFO] Reactor Summary:
[INFO]
[INFO] Project 1 ......................................... SUCCESS [4.742s]
[INFO] Project 2 ......................................... SUCCESS [5:15.220s]
{noformat}
Notice that Project 2 (which had the 300s timeout) above has run > 5 min.
Earlier, in the log we see this:
{noformat}
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>
{noformat}
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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
