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.
Summary: | error in InstanceDataObjectTest | ||
---|---|---|---|
Product: | platform | Reporter: | pzajac <pzajac> |
Component: | Data Systems | Assignee: | David Konecny <dkonecny> |
Status: | CLOSED FIXED | ||
Severity: | blocker | CC: | jtulach |
Priority: | P3 | Keywords: | TEST |
Version: | 4.x | ||
Hardware: | PC | ||
OS: | Linux | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: | test log |
Description
pzajac
2004-10-07 16:10:45 UTC
Created attachment 18134 [details]
test log
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? 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. 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. 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 v |