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 51038 - some errors in InstanceDataObjectModuleTest2
Summary: some errors in InstanceDataObjectModuleTest2
Status: CLOSED INVALID
Alias: None
Product: editor
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 4.x
Hardware: PC Linux
: P2 blocker (vote)
Assignee: issues@editor
URL:
Keywords: TEST
Depends on:
Blocks:
 
Reported: 2004-11-01 15:19 UTC by pzajac
Modified: 2007-11-05 13:44 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
log1 (7.98 KB, text/html)
2004-11-01 15:19 UTC, pzajac
Details
log2 (7.98 KB, text/html)
2004-11-01 15:20 UTC, pzajac
Details
log3 (6.21 KB, text/plain)
2004-11-01 15:20 UTC, pzajac
Details

Note You need to log in before you can comment on or make changes to this bug.
Description pzajac 2004-11-01 15:19:13 UTC
linux, windowsxp, jdk 1.5
see to the attachment for details
Comment 1 pzajac 2004-11-01 15:19:44 UTC
Created attachment 18644 [details]
log1
Comment 2 pzajac 2004-11-01 15:20:05 UTC
Created attachment 18645 [details]
log2
Comment 3 pzajac 2004-11-01 15:20:25 UTC
Created attachment 18646 [details]
log3
Comment 4 Jaroslav Tulach 2004-11-01 16:05:54 UTC
This test is not "unit" that much, it is integration one, as it runs
in whole ide and enabled and disables all modules. 

The failure is from editor module, so I am assigning to them. Btw. I
could not find the reason for the exception in JMIUtils, the code
seems to be changed.

Comment 5 Martin Roskanin 2004-11-01 16:27:01 UTC
Petr, it is reproducible?
Jarda, what is the third exception about?
Editor ends up with InterruptedException. Last commit to JMIUtils was
done in 29.10. It seems code is valid. There is nothing suspicious in
the line 1161, just refreshSettings();
Comment 6 Jaroslav Tulach 2004-11-02 09:22:55 UTC
And what was on line 1161 before? Anyway if this was single time
failure, Petr might be able to accept invalid state for the issue or
at least change of priority. Am I right?
Comment 7 Martin Roskanin 2004-11-02 09:48:49 UTC
Before on 1161: Empty line just after the fields declaration of
ClassesIterator innerclass. The body of the method "settingsChange",
(where stacktrace leads us) was not changed.

I guess, "something" interrupted the thread just on the "innocent" :-)
line 1161 in editor module.
Comment 8 pzajac 2004-11-02 09:54:05 UTC
I can accept invalid state. It is easier for me. If the test fails
again I'll reopen this issue and add more information. 
Comment 9 Martin Roskanin 2004-11-02 10:01:25 UTC
OK, it sounds reasonable. Changing to invalid.
Comment 10 pzajac 2004-11-15 09:06:28 UTC
v