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 15898 - Test DataObjectInvalidationTest failed
Summary: Test DataObjectInvalidationTest failed
Status: CLOSED INVALID
Alias: None
Product: platform
Classification: Unclassified
Component: Data Systems (show other bugs)
Version: 3.x
Hardware: PC Linux
: P4 blocker (vote)
Assignee: Jesse Glick
URL:
Keywords: TEST
Depends on:
Blocks:
 
Reported: 2001-09-25 17:36 UTC by Jaroslav Tulach
Modified: 2008-12-22 17:59 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
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 Jaroslav Tulach 2001-09-25 17:36:44 UTC 
On dual processor machine running linux 1.3.1 RH7.0 kernel 2.4.10:

junit.framework.AssertionFailedError: After forcing refresh on a folder node, a
data object is not started to be created >1 time expected:<1> but was:<3>
        at junit.framework.Assert.fail(Assert.java:158)
        at junit.framework.Assert.failNotEquals(Assert.java:164)
        at junit.framework.Assert.assertEquals(Assert.java:101)
        at junit.framework.Assert.assertEquals(Assert.java:87)
        at
org.openide.loaders.DataObjectInvalidationTest.testDataObjectsCreatedOncePerFile(DataObjectInvalidationTest.java:126)
        at java.lang.reflect.Method.invoke(Native Method)
        at junit.framework.TestCase.runTest(TestCase.java:189)
        at junit.framework.TestCase.runBare(TestCase.java:163)
        at junit.framework.TestResult$1.protect(TestResult.java:106)
        at junit.framework.TestResult.runProtected(TestResult.java:124)
        at junit.framework.TestResult.run(TestResult.java:109)
        at junit.framework.TestCase.run(TestCase.java:154)
        at junit.framework.TestSuite.runTest(TestSuite.java:198)
        at junit.framework.TestSuite.run(TestSuite.java:193)
        at
org.netbeans.xtest.junit.JUnitTestRunnerExt.run(JUnitTestRunnerExt.java:163)
        at
org.netbeans.xtest.junit.JUnitTestRunnerExt.main(JUnitTestRunnerExt.java:303)
Comment 1 Jesse Glick 2001-09-26 13:18:04 UTC 
By the way do you have any idea why this might be so? You agree this
is a bug?
Comment 2 Jesse Glick 2001-10-02 14:59:10 UTC 
Found it, the setup utility for the test was not quite right. (Was
permitting a loader pool change to be fired a second after it was
called, which interfered with this test that was sensitive to
unexpected loader pool changes.) Will commit setup utility fix soon.
Comment 3 Quality Engineering 2003-07-01 15:51:41 UTC 
Resolved for 3.4.x or earlier, no new info since then -> verified
Comment 4 Quality Engineering 2003-07-01 16:28:51 UTC 
Resolved for 3.4.x or earlier, no new info since then -> closing.