[
https://jira.codehaus.org/browse/SUREFIRE-468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed SUREFIRE-468.
-----------------------------------
Resolution: Won't Fix
Please refer to
https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014
if you're wondering why this issue was closed out.
Assignee, if you think you can fix this bug anytime soon, please reopen and
proceed appropriately.
> When tests timeout, report files on disk are incorrect
> ------------------------------------------------------
>
> Key: SUREFIRE-468
> URL: https://jira.codehaus.org/browse/SUREFIRE-468
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin, process forking
> Affects Versions: 2.4.2
> Reporter: A
> Assignee: Kristian Rosenvold
>
> 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 was sent by Atlassian JIRA
(v6.1.6#6162)
