You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Kristian Rosenvold (JIRA)" <ji...@codehaus.org> on 2011/01/02 13:23:57 UTC

[jira] Closed: (SUREFIRE-679) [regression] TestNG suite no longer succeeds, with error "testSetStarting called twice"

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

Kristian Rosenvold closed SUREFIRE-679.
---------------------------------------

       Resolution: Fixed
    Fix Version/s: 2.7.2

Fixed with testcase in r1054391. Bug required TestNG AND redirectTestOutputToFile=true AND non-suite setup (>1 test). It would also cause "Test Set Starting" to be printed twice. It is not related to SUREFIRE-639.

I am getting initializeArchiva(org.apache.archiva.web.test.ArchivaAdminTest) failing now, which I suspect is totally different. You may want to re-test your use-case.

> [regression] TestNG suite no longer succeeds, with error "testSetStarting called twice"
> ---------------------------------------------------------------------------------------
>
>                 Key: SUREFIRE-679
>                 URL: http://jira.codehaus.org/browse/SUREFIRE-679
>             Project: Maven Surefire
>          Issue Type: Bug
>          Components: TestNG support
>    Affects Versions: 2.7.1
>            Reporter: Brett Porter
>            Assignee: Kristian Rosenvold
>             Fix For: 2.7.2
>
>
> I'm receiving this error in 2.7.1:
> "Error while executing forked tests.; nested exception is java.lang.IllegalStateException: testSetStarting called twice"
> This did not occur with 2.5 on the same project. It is using TestNG with a suite XML and Cargo + Selenium
> You should be able to reproduce it by checking out http://svn.apache.org/repos/asf/archiva/trunk, changing the surefire version in the root POM, and running:
> mvn clean install
> cd archiva-modules/archiva-web/archiva-webapp-test
> mvn clean install
> I'll have to come back to investigate the cause later - the project is quite crusty and there may be some misconfiguration also.

-- 
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