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 50107 - error in InstanceDataObjectTest
Summary: error in InstanceDataObjectTest
Status: CLOSED FIXED
Alias: None
Product: platform
Classification: Unclassified
Component: Data Systems (show other bugs)
Version: 4.x
Hardware: PC Linux
: P3 blocker (vote)
Assignee: David Konecny
URL:
Keywords: TEST
Depends on:
Blocks:
 
Reported: 2004-10-07 16:10 UTC by pzajac
Modified: 2008-12-23 00:40 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
test log (9.50 KB, text/html)
2004-10-07 16:11 UTC, pzajac 		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 pzajac 2004-10-07 16:10:45 UTC 
Test Case:  	
testWeAreAbleToResetSharedClassObjectByCallingResetOnItIssue20962
Test Suite: 
org.openide.loaders. InstanceDataObjectTest
Module Name: 	openide 

Host	:	qa-linux-s5.czech.sun.com
Operating System Name	:	Linux
Operating System Version	:	2.4.20-31.9
System Architecture	:	i386
Java Version	:	1.4.2_06
Java Vendor	:	Sun Microsystems Inc.
User Language	:	en
Comment 1 pzajac 2004-10-07 16:11:25 UTC 
Created attachment 18134 [details]
test log
Comment 2 Jaroslav Tulach 2004-10-11 09:35:46 UTC 
My test, but not my failure. I have not touched convertors at all. I
do not know what is wrong - maybe classpath does not contain
core/settings?
Comment 3 David Konecny 2004-10-11 10:51:41 UTC 
If core/settings would be missing on classpath then the test would
constantly fail. But it is always passing on my comp (WinXP) -
lowering to P3.

Yarda, do you have an idea why the original exception is not reported?
InstanceDataObject.convertorWriteMethod() throws exception annotated
by real cause but the cause is not in xtest report. That could help us
a bit to learn why "write" method could not be called.
Comment 4 Jaroslav Tulach 2004-10-11 13:20:05 UTC 
I guess xtest supports ErrorManager reports only in IDE mode not in
unit. [editorial commnet: It would be hard in unit mode anyway as some
tests replace the lookup completely and there is no way].

The simplest way how to learn more about the innerexception is to also
use new Exception ().initCause. More complicated ways include
registration of own ErrorManager - either by providing own lookup
(prefered), or by creating appropriate file in Services folder.
Comment 5 David Konecny 2004-10-12 10:38:35 UTC 
Improved logging. Hopefully it will help next time when test fails.
src/org/openide/loaders/InstanceDataObject.java;
new revision: 1.18; previous revision: 1.17
Comment 6 pzajac 2004-11-02 17:56:47 UTC 
v