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 73086 - Random test failure (Data Object Not Modified): testChangeModel in XmlMultiViewEditorTest
Summary: Random test failure (Data Object Not Modified): testChangeModel in XmlMultiVi...
Status: RESOLVED FIXED
Alias: None
Product: xml
Classification: Unclassified
Component: XML Multiview (show other bugs)
Version: 5.x
Hardware: All All
: P3 blocker (vote)
Assignee: issues@xml
URL:
Keywords: RANDOM, TEST
Depends on:
Blocks:
 
Reported: 2006-02-28 10:02 UTC by Petr Jiricka
Modified: 2009-10-08 15:26 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Stack trace of the exception in test (1.54 KB, text/plain)
2006-02-28 10:03 UTC, Petr Jiricka
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Petr Jiricka 2006-02-28 10:02:13 UTC
Test method testChangeModel in:
org.netbeans.modules.xml.multiview.test. XmlMultiViewEditorTest

fails randomly. Attaching the stack trace. See also this URL (internally):
http://ffjqa.czech/automatedtests/xtest/netbeans_5.5/200602270300/qa-unit/qa-bilbo_1/testrun_060227-150832/testbag_51/htmlresults/suites/TEST-org.netbeans.modules.xml.multiview.test.XmlMultiViewEditorTest.html#testChangeModel%22
Comment 1 Petr Jiricka 2006-02-28 10:03:48 UTC
Created attachment 29044 [details]
Stack trace of the exception in test
Comment 2 Erno Mononen 2007-08-20 14:49:13 UTC
The test still fails every now and then. The problem is that the test (or in fact all tests in the class) relies on 
Thread.sleep and sometimes the model synchronizer hasn't yet updated the model when the assert is executed.
Comment 3 Vince Kraemer 2008-12-03 19:29:17 UTC
bad tm value... reset to tbd
Comment 4 Petr Jiricka 2009-10-08 15:26:32 UTC
We have been running this test regularly for some time on http://bertram.netbeans.org/hudson/job/javaee/, and I haven't
see a failure. Looks like this is fixed now, let's reopen if it reappears.