You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Stephen Connolly (JIRA)" <ji...@codehaus.org> on 2010/08/09 16:10:32 UTC

[jira] Updated: (SUREFIRE-468) When tests timeout, report files on disk are incorrect

     [ http://jira.codehaus.org/browse/SUREFIRE-468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stephen Connolly updated SUREFIRE-468:
--------------------------------------

    Fix Version/s:     (was: 2.6)
                   Backlog

Moving to the backlog as it's not a regression and it is more pressing to get 2.6 out first

> 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: Maven Surefire Plugin, process forking
>    Affects Versions: 2.4.2
>            Reporter: A
>             Fix For: Backlog
>
>
> 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