This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 218444 - NullPointerException at org.netbeans.modules.gsf.testrunner.api.Report.<init>
Summary: NullPointerException at org.netbeans.modules.gsf.testrunner.api.Report.<init>
Alias: None
Product: utilities
Classification: Unclassified
Component: Test Runner (show other bugs)
Version: 7.2
Hardware: All All
: P3 normal (vote)
Assignee: Theofanis Oikonomou
Depends on:
Reported: 2012-09-17 07:47 UTC by Exceptions Reporter
Modified: 2012-11-16 22:22 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 191552

stacktrace (2.38 KB, text/plain)
2012-09-17 07:47 UTC, Exceptions Reporter

Note You need to log in before you can comment on or make changes to this bug.
Description Exceptions Reporter 2012-09-17 07:47:51 UTC
This issue was reported manually by mmirilovic.
It already has 38 duplicates 

Build: NetBeans IDE 7.2 (Build 201207171143)
VM: Java HotSpot(TM) 64-Bit Server VM, 22.0-b10, Java(TM) SE Runtime Environment, 1.7.0_02-b13
OS: Windows 7

User Comments:
GUEST: This seems to be related to expanding the test tree on the LHS of the "Test Results" view when running a JUnit test.

This doesn't appear to be repeatable consistently.

The NPE appears to linger into the next test run (of the same test).

GUEST: Frequent NPE when running JUnits. not obviuosly repeatable.

GUEST: Running a normal JUnit test.

GUEST: Are you sick of these? I am.

   at org.netbeans.modules.gsf.testrunner.api.Report.<init>(
   at org.netbeans.modules.gsf.testrunner.api.TestSession.getReport(
   at org.netbeans.modules.junit.output.JUnitOutputReader.closePereviousReport(
   at org.netbeans.modules.junit.output.JUnitOutputReader.testTaskFinished(
   at org.netbeans.modules.junit.output.JUnitAntLogger.taskFinished(
Comment 1 Exceptions Reporter 2012-09-17 07:47:53 UTC
Created attachment 124429 [details]
Comment 2 Theofanis Oikonomou 2012-11-16 22:22:51 UTC
The project is null for some reason. While fixing bug 221343 (the stacktrace is similar) added assertion to get info for the uri that produces such behaviour: