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: | [TEST] RootContextTest.testContextTreeView failure | ||
|---|---|---|---|
| Product: | platform | Reporter: | Jesse Glick <jglick> |
| Component: | Explorer | Assignee: | Jiri Rechtacek <jrechtacek> |
| Status: | VERIFIED FIXED | ||
| Severity: | blocker | Keywords: | TEST |
| Priority: | P3 | ||
| Version: | 3.x | ||
| Hardware: | All | ||
| OS: | All | ||
| Issue Type: | DEFECT | Exception Reporter: | |
| Bug Depends on: | 32465 | ||
| Bug Blocks: | |||
| Attachments: | XTest log | ||
|
Description
Jesse Glick
2003-01-31 20:47:58 UTC
Created attachment 8757 [details]
XTest log
Test failed sometimes on the tested platform: Windows 2000-5.0-x86 and Windows XP-5.1-x86. I'm going to remove this test from stable testbag first, it should be solved in nb35 release. RootContextTest.testContextTreeView temporary removed from stable. because a resource lack, it will be solved in 4.0. It test files because ExplorerManager.setRootContext() is replaned to AWT-queue if needed. A following EM.setSelectedNodes() fires immediately a vetoable change, it can come before a new root is set, thus PropertyVetoException is thrown. I filed a task 32465 to force all changes come from AWT-queue. I changed RootContextTest to call EM.setSelectedNodes() from AWT. It works for me on Mar26 dev build. reopened Jirka, the right resolution is fixed. closed |