maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Rosenvold (JIRA)" <>
Subject [jira] Updated: (SUREFIRE-468) When tests timeout, report files on disk are incorrect
Date Mon, 07 Mar 2011 20:49:23 GMT


Kristian Rosenvold updated SUREFIRE-468:

    Fix Version/s:     (was: 2.7.2)

> When tests timeout, report files on disk are incorrect
> ------------------------------------------------------
>                 Key: SUREFIRE-468
>                 URL:
>             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.
> 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:
For more information on JIRA, see:


View raw message