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

["Brett Porter (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/SUREFIRE-679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=249882#action_249882 ] 

Brett Porter edited comment on SUREFIRE-679 at 12/29/10 8:04 AM:
-----------------------------------------------------------------

after repairing the startup problems, the test suite progresses as normal. However, at the end the same error appears, so it seems it's not related to the initializeArchiva method.

I can see if I can come up with a test case soon.

      was (Author: brettporter):
    after repairing the startup problems, the test suite progresses as normal. The method above that contained a failure has both @BeforeTest and @Parameters (with the former the most likely issue).

I can see if I can come up with a test case soon.
  
> [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
>
> 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