[
http://jira.codehaus.org/browse/SUREFIRE-468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=132943#action_132943
]
A commented on SUREFIRE-468:
----------------------------
It should not stop execution of subsequent tests if "testFailureIgnore" system
property is set. Sorry , I've forgot to include that in the issue description.
So the issues are really two:
1. report generation
2. not all tests executed even when "testFailureIgnore" system property is set.
> When tests timeout, report files on disk are incorrect
> ------------------------------------------------------
>
> Key: SUREFIRE-468
> URL: http://jira.codehaus.org/browse/SUREFIRE-468
> Project: Maven Surefire
> Issue Type: Bug
> Components: plugin, process forking
> Affects Versions: 2.4.2
> Reporter: A
> Fix For: 2.5
>
>
> When forkmode is always/prtest (probably that could be true for the last test
> and forkmode once) when one test hangs and timeout occurs, est suite
> execution stops and report file for the offending test not generated. That
> could mislead somebody to think all tests passed if all tests before the
> offending one passed.
> AFAICT that should be synchronized between one of these:
> 1. CommandLineUtils.executeCommandLine()
> 2. SurefireBooter.fork()
> 3. SurefireBooter.run()
> 4. SurefirePlugin.execute()
> Probably fork must detect a timeout. Then the timeout be gracefully handled
> by generating a report file for the test. Then continue execution of
> remaining tests.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
