You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Tim Wu T <ti...@ericsson.com> on 2014/04/24 21:57:55 UTC

Maven sure fire plugin npe problem.

Hi everyone,

I am not sure if some of you met this problem before, we have some smoke test in Jenkins sever, which will run some test case through maven sure fire plugin, version is 2.17

But it will always throw an exception like this:
java.lang.NullPointerException
     at org.apache.maven.surefire.report.SmartStackTraceParser.<init>(SmartStackTraceParser.java:60)
     at org.apache.maven.surefire.report.PojoStackTraceWriter.smartTrimmedStackTrace(PojoStackTraceWriter.java:60)
     at org.apache.maven.surefire.booter.ForkingRunListener.encode(ForkingRunListener.java:328)
     at org.apache.maven.surefire.booter.ForkingRunListener.encode(ForkingRunListener.java:312)
     at org.apache.maven.surefire.booter.ForkingRunListener.toString(ForkingRunListener.java:258)
     at org.apache.maven.surefire.booter.ForkingRunListener.testFailed(ForkingRunListener.java:137)
     at org.apache.maven.surefire.testng.TestNGReporter.onTestFailure(TestNGReporter.java:105)
     at org.testng.internal.Invoker.runTestListeners(Invoker.java:1901)
     at org.testng.internal.Invoker.runTestListeners(Invoker.java:1885)
     at org.testng.internal.Invoker.invokeMethod(Invoker.java:788)
     at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:907)
     at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1237)
     at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127)
     at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111)
     at org.testng.TestRunner.privateRun(TestRunner.java:767)
     at org.testng.TestRunner.run(TestRunner.java:617)
     at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
     at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329)
     at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291)
     at org.testng.SuiteRunner.run(SuiteRunner.java:240)
     at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:51)
     at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:85)
     at org.testng.TestNG.runSuitesSequentially(TestNG.java:1197)
     at org.testng.TestNG.runSuitesLocally(TestNG.java:1122)
     at org.testng.TestNG.run(TestNG.java:1030)
     at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:293)
     at org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:84)
     at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:91)
     at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200)
     at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
     at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)



I try to google something, but I don't get any good feedback.

Thanks in advance.

Br,
Tim

RE: Maven sure fire plugin npe problem.

Posted by Tim Wu T <ti...@ericsson.com>.
Hi Stephen,

Thanks for your info, your solution works for me :)

Br,
Tim

-----Original Message-----
From: Stephen Connolly [mailto:stephen.alan.connolly@gmail.com] 
Sent: den 27 april 2014 11:41
To: Maven Users List
Subject: Re: Maven sure fire plugin npe problem.

You signup for an account on xircles.codehaus.org... Effing jira templating does not make it easy to put that notice on the generic login screen so it is hard for people to guess... If you go to jira.codehaus.org you can see the not to use xircles... But sadly nowhere else :-(

The curse of the spammers forcing a non-jira signup process on the RoW

On Saturday, 26 April 2014, Tim Wu T <ti...@ericsson.com> wrote:

> Not sure if anyone could show me how to create a TR for this, I don't 
> have a JIRA account.
>
> Br,
> Tim
>
> -----Original Message-----
> From: Tim Wu T [mailto:tim.t.wu@ericsson.com <javascript:;>]
> Sent: den 26 april 2014 22:53
> To: Maven Users List
> Subject: RE: Maven sure fire plugin npe problem.
>
> Hi,
>
> After detail investigation, I can prove this is a bug of maven 
> surefire plugin, after version 2.12. That means from 2.12~2.17 it met 
> the same problem.
>
> The problem will happen in a special condition, you don't met any 
> error during the test case execution time, however, you set the result 
> to fail during IInvokedMethodListener#afterInovation, such as 
> result.setStatus(Fail),
>
> Then maven surefire plugin will run ITestListener#onTestFailure method 
> twice and throw a Null pointer exception.
>
> Currently, I rollback our plugin version to 2.12 to avoid this type of 
> problem.
>
> Br,
> Tim
> -----Original Message-----
> From: kristian.rosenvold@zenior.no 
> [mailto:kristian.rosenvold@zenior.no]
> On Behalf Of Kristian Rosenvold
> Sent: den 25 april 2014 07:42
> To: Maven Users List
> Subject: Re: Maven sure fire plugin npe problem.
>
> It would appear that testng is not reporting the throwable that is 
> cause of the failure. You might want to try a few different testNG 
> versions to see if this is a recently introduced regression.
>
> Surefire should probably not NPE on this, but gaining some insight 
> into the root cause is probably a good thing (tm).
>
> Kristian
>
>
>
> 2014-04-24 21:57 GMT+02:00 Tim Wu T <ti...@ericsson.com>:
>
> > Hi everyone,
> >
> > I am not sure if some of you met this problem before, we have some 
> > smoke test in Jenkins sever, which will run some test case through 
> > maven sure fire plugin, version is 2.17
> >
> > But it will always throw an exception like this:
> > java.lang.NullPointerException
> >      at
> >
> org.apache.maven.surefire.report.SmartStackTraceParser.<init>(SmartSta
> ckTraceParser.java:60)
> >      at
> >
> org.apache.maven.surefire.report.PojoStackTraceWriter.smartTrimmedStac
> kTrace(PojoStackTraceWriter.java:60)
> >      at
> >
> org.apache.maven.surefire.booter.ForkingRunListener.encode(ForkingRunL
> istener.java:328)
> >      at
> >
> org.apache.maven.surefire.booter.ForkingRunListener.encode(ForkingRunL
> istener.java:312)
> >      at
> >
> org.apache.maven.surefire.booter.ForkingRunListener.toString(ForkingRu
> nListener.java:258)
> >      at
> >
> org.apache.maven.surefire.booter.ForkingRunListener.testFailed(Forking
> RunListener.java:137)
> >      at
> >
> org.apache.maven.surefire.testng.TestNGReporter.onTestFailure(TestNGRe
> porter.java:105)
> >      at org.testng.internal.Invoker.runTestListeners(Invoker.java:1901)
> >      at org.testng.internal.Invoker.runTestListeners(Invoker.java:1885)
> >      at org.testng.internal.Invoker.invokeMethod(Invoker.java:788)
> >      at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:907)
> >      at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1237)
> >      at
> >
> org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorke
> r.java:127)
> >      at
> org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111)
> >      at org.testng.TestRunner.privateRun(TestRunner.java:767)
> >      at org.testng.TestRunner.run(TestRunner.java:617)
> >      at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
> >      at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329)
> >      at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291)
> >      at org.testng.SuiteRunner.run(SuiteRunner.java:240)
> >      at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:51)
> >      at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:85)
> >      at org.testng.TestNG.runSuitesSequentially(TestNG.java:1197)
> >      at org.testng.TestNG.runSuitesLocally(TestNG.java:1122)
> >      at org.testng.TestNG.run(TestNG.java:1030)
> >      at
> > org.apach



--
Sent from my phone

Re: Maven sure fire plugin npe problem.

Posted by Stephen Connolly <st...@gmail.com>.
You signup for an account on xircles.codehaus.org... Effing jira templating
does not make it easy to put that notice on the generic login screen so it
is hard for people to guess... If you go to jira.codehaus.org you can see
the not to use xircles... But sadly nowhere else :-(

The curse of the spammers forcing a non-jira signup process on the RoW

On Saturday, 26 April 2014, Tim Wu T <ti...@ericsson.com> wrote:

> Not sure if anyone could show me how to create a TR for this, I don't have
> a JIRA account.
>
> Br,
> Tim
>
> -----Original Message-----
> From: Tim Wu T [mailto:tim.t.wu@ericsson.com <javascript:;>]
> Sent: den 26 april 2014 22:53
> To: Maven Users List
> Subject: RE: Maven sure fire plugin npe problem.
>
> Hi,
>
> After detail investigation, I can prove this is a bug of maven surefire
> plugin, after version 2.12. That means from 2.12~2.17 it met the same
> problem.
>
> The problem will happen in a special condition, you don't met any error
> during the test case execution time, however, you set the result to fail
> during IInvokedMethodListener#afterInovation, such as
> result.setStatus(Fail),
>
> Then maven surefire plugin will run ITestListener#onTestFailure method
> twice and throw a Null pointer exception.
>
> Currently, I rollback our plugin version to 2.12 to avoid this type of
> problem.
>
> Br,
> Tim
> -----Original Message-----
> From: kristian.rosenvold@zenior.no [mailto:kristian.rosenvold@zenior.no]
> On Behalf Of Kristian Rosenvold
> Sent: den 25 april 2014 07:42
> To: Maven Users List
> Subject: Re: Maven sure fire plugin npe problem.
>
> It would appear that testng is not reporting the throwable that is cause
> of the failure. You might want to try a few different testNG versions to
> see if this is a recently introduced regression.
>
> Surefire should probably not NPE on this, but gaining some insight into
> the root cause is probably a good thing (tm).
>
> Kristian
>
>
>
> 2014-04-24 21:57 GMT+02:00 Tim Wu T <ti...@ericsson.com>:
>
> > Hi everyone,
> >
> > I am not sure if some of you met this problem before, we have some
> > smoke test in Jenkins sever, which will run some test case through
> > maven sure fire plugin, version is 2.17
> >
> > But it will always throw an exception like this:
> > java.lang.NullPointerException
> >      at
> >
> org.apache.maven.surefire.report.SmartStackTraceParser.<init>(SmartStackTraceParser.java:60)
> >      at
> >
> org.apache.maven.surefire.report.PojoStackTraceWriter.smartTrimmedStackTrace(PojoStackTraceWriter.java:60)
> >      at
> >
> org.apache.maven.surefire.booter.ForkingRunListener.encode(ForkingRunListener.java:328)
> >      at
> >
> org.apache.maven.surefire.booter.ForkingRunListener.encode(ForkingRunListener.java:312)
> >      at
> >
> org.apache.maven.surefire.booter.ForkingRunListener.toString(ForkingRunListener.java:258)
> >      at
> >
> org.apache.maven.surefire.booter.ForkingRunListener.testFailed(ForkingRunListener.java:137)
> >      at
> >
> org.apache.maven.surefire.testng.TestNGReporter.onTestFailure(TestNGReporter.java:105)
> >      at org.testng.internal.Invoker.runTestListeners(Invoker.java:1901)
> >      at org.testng.internal.Invoker.runTestListeners(Invoker.java:1885)
> >      at org.testng.internal.Invoker.invokeMethod(Invoker.java:788)
> >      at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:907)
> >      at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1237)
> >      at
> >
> org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127)
> >      at
> org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111)
> >      at org.testng.TestRunner.privateRun(TestRunner.java:767)
> >      at org.testng.TestRunner.run(TestRunner.java:617)
> >      at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
> >      at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329)
> >      at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291)
> >      at org.testng.SuiteRunner.run(SuiteRunner.java:240)
> >      at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:51)
> >      at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:85)
> >      at org.testng.TestNG.runSuitesSequentially(TestNG.java:1197)
> >      at org.testng.TestNG.runSuitesLocally(TestNG.java:1122)
> >      at org.testng.TestNG.run(TestNG.java:1030)
> >      at
> > org.apach



-- 
Sent from my phone

RE: Maven sure fire plugin npe problem.

Posted by Tim Wu T <ti...@ericsson.com>.
Not sure if anyone could show me how to create a TR for this, I don't have a JIRA account.

Br,
Tim

-----Original Message-----
From: Tim Wu T [mailto:tim.t.wu@ericsson.com] 
Sent: den 26 april 2014 22:53
To: Maven Users List
Subject: RE: Maven sure fire plugin npe problem.

Hi,

After detail investigation, I can prove this is a bug of maven surefire plugin, after version 2.12. That means from 2.12~2.17 it met the same problem.

The problem will happen in a special condition, you don't met any error during the test case execution time, however, you set the result to fail during IInvokedMethodListener#afterInovation, such as result.setStatus(Fail),

Then maven surefire plugin will run ITestListener#onTestFailure method twice and throw a Null pointer exception.

Currently, I rollback our plugin version to 2.12 to avoid this type of problem.

Br,
Tim
-----Original Message-----
From: kristian.rosenvold@zenior.no [mailto:kristian.rosenvold@zenior.no] On Behalf Of Kristian Rosenvold
Sent: den 25 april 2014 07:42
To: Maven Users List
Subject: Re: Maven sure fire plugin npe problem.

It would appear that testng is not reporting the throwable that is cause of the failure. You might want to try a few different testNG versions to see if this is a recently introduced regression.

Surefire should probably not NPE on this, but gaining some insight into the root cause is probably a good thing (tm).

Kristian



2014-04-24 21:57 GMT+02:00 Tim Wu T <ti...@ericsson.com>:

> Hi everyone,
>
> I am not sure if some of you met this problem before, we have some 
> smoke test in Jenkins sever, which will run some test case through 
> maven sure fire plugin, version is 2.17
>
> But it will always throw an exception like this:
> java.lang.NullPointerException
>      at
> org.apache.maven.surefire.report.SmartStackTraceParser.<init>(SmartStackTraceParser.java:60)
>      at
> org.apache.maven.surefire.report.PojoStackTraceWriter.smartTrimmedStackTrace(PojoStackTraceWriter.java:60)
>      at
> org.apache.maven.surefire.booter.ForkingRunListener.encode(ForkingRunListener.java:328)
>      at
> org.apache.maven.surefire.booter.ForkingRunListener.encode(ForkingRunListener.java:312)
>      at
> org.apache.maven.surefire.booter.ForkingRunListener.toString(ForkingRunListener.java:258)
>      at
> org.apache.maven.surefire.booter.ForkingRunListener.testFailed(ForkingRunListener.java:137)
>      at
> org.apache.maven.surefire.testng.TestNGReporter.onTestFailure(TestNGReporter.java:105)
>      at org.testng.internal.Invoker.runTestListeners(Invoker.java:1901)
>      at org.testng.internal.Invoker.runTestListeners(Invoker.java:1885)
>      at org.testng.internal.Invoker.invokeMethod(Invoker.java:788)
>      at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:907)
>      at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1237)
>      at
> org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127)
>      at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111)
>      at org.testng.TestRunner.privateRun(TestRunner.java:767)
>      at org.testng.TestRunner.run(TestRunner.java:617)
>      at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
>      at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329)
>      at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291)
>      at org.testng.SuiteRunner.run(SuiteRunner.java:240)
>      at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:51)
>      at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:85)
>      at org.testng.TestNG.runSuitesSequentially(TestNG.java:1197)
>      at org.testng.TestNG.runSuitesLocally(TestNG.java:1122)
>      at org.testng.TestNG.run(TestNG.java:1030)
>      at
> org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:293)
>      at
> org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:84)
>      at
> org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:91)
>      at
> org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200)
>      at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
>      at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:1
> 03)
>
>
>
> I try to google something, but I don't get any good feedback.
>
> Thanks in advance.
>
> Br,
> Tim
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

RE: Maven sure fire plugin npe problem.

Posted by Tim Wu T <ti...@ericsson.com>.
Hi,

After detail investigation, I can prove this is a bug of maven surefire plugin, after version 2.12. That means from 2.12~2.17 it met the same problem.

The problem will happen in a special condition, you don't met any error during the test case execution time, however, you set the result to fail during IInvokedMethodListener#afterInovation, such as result.setStatus(Fail),

Then maven surefire plugin will run ITestListener#onTestFailure method twice and throw a Null pointer exception.

Currently, I rollback our plugin version to 2.12 to avoid this type of problem.

Br,
Tim
-----Original Message-----
From: kristian.rosenvold@zenior.no [mailto:kristian.rosenvold@zenior.no] On Behalf Of Kristian Rosenvold
Sent: den 25 april 2014 07:42
To: Maven Users List
Subject: Re: Maven sure fire plugin npe problem.

It would appear that testng is not reporting the throwable that is cause of the failure. You might want to try a few different testNG versions to see if this is a recently introduced regression.

Surefire should probably not NPE on this, but gaining some insight into the root cause is probably a good thing (tm).

Kristian



2014-04-24 21:57 GMT+02:00 Tim Wu T <ti...@ericsson.com>:

> Hi everyone,
>
> I am not sure if some of you met this problem before, we have some 
> smoke test in Jenkins sever, which will run some test case through 
> maven sure fire plugin, version is 2.17
>
> But it will always throw an exception like this:
> java.lang.NullPointerException
>      at
> org.apache.maven.surefire.report.SmartStackTraceParser.<init>(SmartStackTraceParser.java:60)
>      at
> org.apache.maven.surefire.report.PojoStackTraceWriter.smartTrimmedStackTrace(PojoStackTraceWriter.java:60)
>      at
> org.apache.maven.surefire.booter.ForkingRunListener.encode(ForkingRunListener.java:328)
>      at
> org.apache.maven.surefire.booter.ForkingRunListener.encode(ForkingRunListener.java:312)
>      at
> org.apache.maven.surefire.booter.ForkingRunListener.toString(ForkingRunListener.java:258)
>      at
> org.apache.maven.surefire.booter.ForkingRunListener.testFailed(ForkingRunListener.java:137)
>      at
> org.apache.maven.surefire.testng.TestNGReporter.onTestFailure(TestNGReporter.java:105)
>      at org.testng.internal.Invoker.runTestListeners(Invoker.java:1901)
>      at org.testng.internal.Invoker.runTestListeners(Invoker.java:1885)
>      at org.testng.internal.Invoker.invokeMethod(Invoker.java:788)
>      at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:907)
>      at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1237)
>      at
> org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127)
>      at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111)
>      at org.testng.TestRunner.privateRun(TestRunner.java:767)
>      at org.testng.TestRunner.run(TestRunner.java:617)
>      at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
>      at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329)
>      at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291)
>      at org.testng.SuiteRunner.run(SuiteRunner.java:240)
>      at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:51)
>      at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:85)
>      at org.testng.TestNG.runSuitesSequentially(TestNG.java:1197)
>      at org.testng.TestNG.runSuitesLocally(TestNG.java:1122)
>      at org.testng.TestNG.run(TestNG.java:1030)
>      at
> org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:293)
>      at
> org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:84)
>      at
> org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:91)
>      at
> org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200)
>      at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
>      at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:1
> 03)
>
>
>
> I try to google something, but I don't get any good feedback.
>
> Thanks in advance.
>
> Br,
> Tim
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: Maven sure fire plugin npe problem.

Posted by Kristian Rosenvold <kr...@gmail.com>.
It would appear that testng is not reporting the throwable that is cause of
the failure. You might want to try a few different testNG versions to see
if this is a recently introduced regression.

Surefire should probably not NPE on this, but gaining some insight into the
root cause is probably a good thing (tm).

Kristian



2014-04-24 21:57 GMT+02:00 Tim Wu T <ti...@ericsson.com>:

> Hi everyone,
>
> I am not sure if some of you met this problem before, we have some smoke
> test in Jenkins sever, which will run some test case through maven sure
> fire plugin, version is 2.17
>
> But it will always throw an exception like this:
> java.lang.NullPointerException
>      at
> org.apache.maven.surefire.report.SmartStackTraceParser.<init>(SmartStackTraceParser.java:60)
>      at
> org.apache.maven.surefire.report.PojoStackTraceWriter.smartTrimmedStackTrace(PojoStackTraceWriter.java:60)
>      at
> org.apache.maven.surefire.booter.ForkingRunListener.encode(ForkingRunListener.java:328)
>      at
> org.apache.maven.surefire.booter.ForkingRunListener.encode(ForkingRunListener.java:312)
>      at
> org.apache.maven.surefire.booter.ForkingRunListener.toString(ForkingRunListener.java:258)
>      at
> org.apache.maven.surefire.booter.ForkingRunListener.testFailed(ForkingRunListener.java:137)
>      at
> org.apache.maven.surefire.testng.TestNGReporter.onTestFailure(TestNGReporter.java:105)
>      at org.testng.internal.Invoker.runTestListeners(Invoker.java:1901)
>      at org.testng.internal.Invoker.runTestListeners(Invoker.java:1885)
>      at org.testng.internal.Invoker.invokeMethod(Invoker.java:788)
>      at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:907)
>      at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1237)
>      at
> org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127)
>      at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111)
>      at org.testng.TestRunner.privateRun(TestRunner.java:767)
>      at org.testng.TestRunner.run(TestRunner.java:617)
>      at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
>      at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329)
>      at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291)
>      at org.testng.SuiteRunner.run(SuiteRunner.java:240)
>      at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:51)
>      at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:85)
>      at org.testng.TestNG.runSuitesSequentially(TestNG.java:1197)
>      at org.testng.TestNG.runSuitesLocally(TestNG.java:1122)
>      at org.testng.TestNG.run(TestNG.java:1030)
>      at
> org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:293)
>      at
> org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:84)
>      at
> org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:91)
>      at
> org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200)
>      at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
>      at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
>
>
>
> I try to google something, but I don't get any good feedback.
>
> Thanks in advance.
>
> Br,
> Tim
>

Re: Maven sure fire plugin npe problem.

Posted by yaroslavTir <ya...@gmail.com>.
And also I use spock framework, not TestNG



--
View this message in context: http://maven.40175.n5.nabble.com/Maven-sure-fire-plugin-npe-problem-tp5791902p5805616.html
Sent from the Maven - Users mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: Maven sure fire plugin npe problem.

Posted by yaroslavTir <ya...@gmail.com>.
Ok, sounds good.
anyway just in case here is me reproduce on github:
https://github.com/YaroslavTir/surefile-plugin-problem



--
View this message in context: http://maven.40175.n5.nabble.com/Maven-sure-fire-plugin-npe-problem-tp5791902p5805615.html
Sent from the Maven - Users mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: Maven sure fire plugin npe problem.

Posted by Andreas Gudian <an...@gmail.com>.
There is an issue filed for it already:
https://jira.codehaus.org/browse/SUREFIRE-1077

The fix should be quite simple, I just didn't get to it, yet. But we should
aim for wrapping up Surefire 2.18 within the next (very) weeks, which would
include this issue.



Am Donnerstag, 18. September 2014 schrieb Martin Gainty :

>
>
> > Date: Thu, 18 Sep 2014 05:12:01 -0700
> > From: yaroslavTir@gmail.com <javascript:;>
> > To: users@maven.apache.org <javascript:;>
> > Subject: Re: Maven sure fire plugin npe problem.
> >
> > Hi all,
> > I have the same problem. I also revert surefire plugin to the 2.12
> version
> > and everything begin to work. Does you found what was wrong? Do I need to
> > send my "non working" example?
>
> MG>please file a JIRA and attach a zip including all files from base
> folder out
> MG>be mindful that errors from package phase and or TESTS run in
> /target/surefire-reports must not have ClassNotFoundException
> MG>thanks
> >
> >
> >
> > --
> > View this message in context:
> http://maven.40175.n5.nabble.com/Maven-sure-fire-plugin-npe-problem-tp5791902p5805605.html
> > Sent from the Maven - Users mailing list archive at Nabble.com.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> <javascript:;>
> > For additional commands, e-mail: users-help@maven.apache.org
> <javascript:;>
> >
>

RE: Maven sure fire plugin npe problem.

Posted by Martin Gainty <mg...@hotmail.com>.

> Date: Thu, 18 Sep 2014 05:12:01 -0700
> From: yaroslavTir@gmail.com
> To: users@maven.apache.org
> Subject: Re: Maven sure fire plugin npe problem.
> 
> Hi all,
> I have the same problem. I also revert surefire plugin to the 2.12 version
> and everything begin to work. Does you found what was wrong? Do I need to
> send my "non working" example?
 
MG>please file a JIRA and attach a zip including all files from base folder out
MG>be mindful that errors from package phase and or TESTS run in /target/surefire-reports must not have ClassNotFoundException 
MG>thanks
> 
> 
> 
> --
> View this message in context: http://maven.40175.n5.nabble.com/Maven-sure-fire-plugin-npe-problem-tp5791902p5805605.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>

Re: Maven sure fire plugin npe problem.

Posted by yaroslavTir <ya...@gmail.com>.
Hi all,
I have the same problem. I also revert surefire plugin to the 2.12 version
and everything begin to work. Does you found what was wrong? Do I need to
send my "non working" example?



--
View this message in context: http://maven.40175.n5.nabble.com/Maven-sure-fire-plugin-npe-problem-tp5791902p5805605.html
Sent from the Maven - Users mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org