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 242052 - AssertionError: Project was null for projectURI: memory://fs79/
Summary: AssertionError: Project was null for projectURI: memory://fs79/
Status: RESOLVED DUPLICATE of bug 241893
Alias: None
Product: java
Classification: Unclassified
Component: JUnit (show other bugs)
Version: 8.0
Hardware: PC Linux
: P3 normal (vote)
Assignee: Theofanis Oikonomou
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-02-18 13:43 UTC by mprentice
Modified: 2014-02-18 16:29 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 207732

Attachments
stacktrace (2.62 KB, text/plain)
2014-02-18 13:43 UTC, mprentice 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description mprentice 2014-02-18 13:43:46 UTC 
This issue was reported manually by mprentice.
It already has 1 duplicates 


Build: NetBeans IDE Dev (Build 201402140001)
VM: Java HotSpot(TM) 64-Bit Server VM, 24.51-b03, Java(TM) SE Runtime Environment, 1.7.0_51-b13
OS: Linux

User Comments:
mprentice: Expanding a JUnit test suite's results in the Test Results view.




Stacktrace: 
java.lang.AssertionError: Project was null for projectURI: memory://fs79/
   at org.netbeans.modules.gsf.testrunner.api.Report.getProject(Report.java:111)
   at org.netbeans.modules.gsf.testrunner.api.TestsuiteNodeChildren.createNodeForKey(TestsuiteNodeChildren.java:85)
   at org.netbeans.modules.gsf.testrunner.api.TestsuiteNodeChildren.createNodeForKey(TestsuiteNodeChildren.java:55)
   at org.openide.nodes.ChildFactory.createNodesForKey(ChildFactory.java:120)
   at org.openide.nodes.AsynchChildren.createNodes(AsynchChildren.java:160)
   at org.openide.nodes.Children$Keys$KE.nodes(Children.java:1662)
Comment 1 mprentice 2014-02-18 13:43:48 UTC 
Created attachment 145357 [details]
stacktrace
Comment 2 Theofanis Oikonomou 2014-02-18 16:29:37 UTC 
Not exactly duplicate but the main cause is that project was null when creating the Report belonging to the specific TestSession through the JUnitOutputReader. So fixing bug 241893 will solve this one as well

*** This bug has been marked as a duplicate of bug 241893 ***