NullPointerException at Java8StepDefinition.isDefinedAt

[mpkorstanje]

Summary

Test failure produces this stack trace. Not sure about the circumstances:

java.lang.NullPointerException
	at cucumber.runtime.java8.Java8StepDefinition.isDefinedAt(Java8StepDefinition.java:111)
	at cucumber.runtime.StepDefinitionMatch.removeFrameworkFramesAndAppendStepLocation(StepDefinitionMatch.java:153)
	at cucumber.runtime.StepDefinitionMatch.runStep(StepDefinitionMatch.java:44)
	at cucumber.api.TestStep.executeStep(TestStep.java:78)
	at cucumber.api.TestStep.run(TestStep.java:61)
	at cucumber.api.TestCase.run(TestCase.java:28)
	at cucumber.runner.Runner.runPickle(Runner.java:80)
	at cucumber.runtime.junit.PickleRunners$NoStepDescriptions.run(PickleRunners.java:140)
	at cucumber.runtime.junit.FeatureRunner.runChild(FeatureRunner.java:68)
	at cucumber.runtime.junit.FeatureRunner.runChild(FeatureRunner.java:23)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at cucumber.runtime.junit.FeatureRunner.run(FeatureRunner.java:73)
	at cucumber.api.junit.Cucumber.runChild(Cucumber.java:99)
	at cucumber.api.junit.Cucumber.runChild(Cucumber.java:41)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
	at org.apache.maven.surefire.junitcore.pc.Scheduler$1.run(Scheduler.java:393)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)

Your Environment

• Version used: cucumber-jvm:2.0.0
• Operating System and version: Unix

[brasmusson]

Well, technically StackTraceElement.getFileName() can return null. It looks like if new Exception().getStackTrace()[3] was to return a StackTraceElement without the file name information, this stack trace would appear. However, I have not been able to reproduce the problem.

[mpkorstanje]

I'll look into reproducing this.

[mpkorstanje]

I'm stumped.

1. I can reproduce this exception by running my existing test set on the build server but not my development machine.
2. A scenario must fail to produce the error, but not every failure generates the error.
3. Repeated failure of the same scenario has an apparently random chance to produce this error.
4. Failing steps range in complexity from trivial to complex. They are all lambda step definitions but just about every variation is covered.

This all leads me to thinking that it might be specific jdk version of the buildserver that has an issue in combination with some jdk jit magic.

Despite being unable to properly diagnose this I think following the technical specification would the right solution so: return location.getFileName() != null && location.getFileName().equals(stackTraceElement.getFileName());

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.