-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
linux x64, Jenkins LTS 2.60.3, Maven Integration plugin 2.17
If a project configures surefire to timeout after a reasonable time using -Dsurefire.exitTimeout=180 -Dsurefire.timeout=180 and the tests time out you'll see
[ERROR] There was a timeout or other error in the fork
[JENKINS] Recording test results
However Jenkins decides that the tests succeeded and completes the build and all success actions.
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
This condition can be simulated by setting an artificially low surefire timeout.
Same here. In a regular shell (locally, not in Jenkins) the error is manifested as a build failure:
That is with mvn -e .... Without it you won't see the stacktrace but the return code is 1 either way!