Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.7.1
-
Fix Version/s: 2.9
-
Component/s: Junit 4.7+ (parallel) support
-
Labels:None
-
Complexity:Intermediate
-
Number of attachments :
Description
This is running m3 with -T 1C (8 core build machine).
[17:52:38]: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.7.1:test (default-test) on project hornet-stinger: Error while executing forked tests.; nested exception is java.lang.IllegalStateException: testSetCompleted called before testSetStarting -> [Help 1]
Seems like it doesn't happen as frequently as previously
Issue Links
- depends upon
-
PLXUTILS-138
executeCommandLine with timeout leaves StreamPumpers pumping data to client after method is returned
-
Are you setting the "forkTimeout" parameter in your surefire settings ? We have identified a race condition that could occur if the forked process times out while still outputting to stdout/stderr. Just setting "forkTimeout" is actually enough to trigger
this, it would happen even with "forkMode=never" as long as forkTimeout is set.
Actually the issue would probably happen quite frequently as long as the process outputs to stderr/stdout at the exact time it times out with "forkTimeout".