[
https://issues.apache.org/jira/browse/SUREFIRE-1300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15659321#comment-15659321
]
Tibor Digana edited comment on SUREFIRE-1300 at 11/12/16 9:03 AM:
------------------------------------------------------------------
When I launched the build of the sample I got:
{quote}
[INFO] parallel='none', perCoreThreadCount=true, threadCount=0,
{quote}
This is printed by MOJO class executed in Maven process which refers to
parameters written in POM.
Therefore I have said that these tests do not use any annotations and config
for parallel execution. That's the reason that maybe TestNG should not need to
make a lookup of this parameter {{threadCount}}. WDYT?
Do you have such section in TestNG which makes a lookup of {{threadCount}} if
{{parallel}} execution is detected? Other features maybe would make another
lookup.
was (Author: tibor17):
When I launched the build of the sample I got:
{{parallel='none', perCoreThreadCount=true, threadCount=0, useUn }}
This is printed by MOJO class executed in Maven process which refers to
parameters written in POM.
Therefore I have said that these tests do not use any annotations and config
for parallel execution. That's the reason that maybe TestNG should not need to
lookup this parameter {{threadCount}}. WDYT?
Do you have such section in TestNG which makes a lookup of {{threadCount}} if
{{parallel}} execution is detected? Other features maybe would make another
lookup.
> threadCount is 0 when surefire-junit47 and surefire-testng are used together
> ----------------------------------------------------------------------------
>
> Key: SUREFIRE-1300
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1300
> Project: Maven Surefire
> Issue Type: Bug
> Components: Junit 4.x support, TestNG support
> Reporter: Julien Herr
> Assignee: Tibor Digana
> Priority: Minor
>
> Initial discussion:
> https://github.com/easymock/easymock/pull/186#discussion_r85655490
> Sample on: https://gist.github.com/juherr/6eb3e93e2db33979b7e90b63ddadc888
> Workaround: Force `<threadCount>1</threadCount>` in surefire configuration
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
