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 69511 - Failure in commit validation on my computer
Summary: Failure in commit validation on my computer
Status: RESOLVED FIXED
Alias: None
Product: ide
Classification: Unclassified
Component: Code (show other bugs)
Version: 5.x
Hardware: All All
: P1 blocker (vote)
Assignee: Jiri Skrivanek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-11-29 09:16 UTC by Jaroslav Tulach
Modified: 2006-01-16 09:09 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
The results (184.38 KB, application/x-compressed)
2005-11-29 12:26 UTC, Jaroslav Tulach 		Details
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 2005-11-29 09:16:40 UTC 
Something wrong in XML
Comment 1 Jiri Skrivanek 2005-11-29 09:40:27 UTC 
Please, attach or send me zipped results.
http://qa.netbeans.org/bugzilla/issue-reports.html ;-)
Comment 2 Jaroslav Tulach 2005-11-29 12:26:28 UTC 
Created attachment 27378 [details]
The results
Comment 3 Jaroslav Tulach 2005-11-29 12:27:17 UTC 
Sorry, I had the failure zipped, but forgot to attach it.
Comment 4 Jiri Skrivanek 2005-11-29 13:52:27 UTC 
Well, it is an issue which appears from time to time. I added a diagnostic to
IDEValidation.java already. It says that DTD.dtd node is created, DTD.dtd is
opened in editor, but then DTD.dtd node is destroyed and probably recreated
because screen shot shows it. But the test still works with destroyed node. I
don't know why it is re-created. Because of sorting?
Comment 5 Jaroslav Tulach 2005-11-30 06:49:15 UTC 
The only way to find the reason for random failures like this is to enable 
logging and see what is happening in the system. The best would imho be if 
there was one log shared between the jemmy tests and the system. That way one 
could see the sequence of actions that really happened.
Comment 6 Jiri Skrivanek 2005-12-01 14:22:13 UTC 
I fixed it in jellytools. When a node is re-created we find valid TreePath in
getTreePath() method.


/cvs/jellytools/src/org/netbeans/jellytools/nodes/Node.java,v  <--  Node.java
new revision: 1.19; previous revision: 1.18
done
Checking in NodeTest.java;
/cvs/jellytools/test/unit/src/org/netbeans/jellytools/nodes/NodeTest.java,v  <--
 NodeTest.java
new revision: 1.14; previous revision: 1.13
Comment 7 Jiri Skrivanek 2006-01-16 09:09:14 UTC 
One more place where getTreePath() has to be called:

/cvs/jellytools/src/org/netbeans/jellytools/nodes/Node.java,v  <--  Node.java
new revision: 1.21; previous revision: 1.20
/cvs/jellytools/test/unit/src/org/netbeans/jellytools/nodes/NodeTest.java,v  <--
 NodeTest.java
new revision: 1.15; previous revision: 1.14