Bugzilla – Full Text Bug Listing
| Summary: | A team compare test hangs the unit tests with user prompt | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | David Williams <david_williams> | ||||
| Component: | Team | Assignee: | Platform Team Inbox <platform-team-inbox> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | ||||||
| Version: | 4.2 | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Linux | ||||||
| Whiteboard: | stalebug | ||||||
| Attachments: |
|
||||||
The screenshoot suggests that this problem was generated by SaveableCompareEditorInputTest#testModifyAndSaveBothSidesOfCompareEditorJava. This test modifies two sites of the compare editor, saves them, verifies if editor is not dirty and closes the editor. I can imagine a timing issue when editor is not yet saved before we attempt to close it, but the assertion on isDirty should rule this problem out. I have never seen this problem before and I run CVS tests quite frequently. Has this happen only once to you? yes, just once. And, I wasn't running them "carefully" or anything (e.g. I might have been doing other work on computer. Feel free to close as "works for me". I just reported in case it was helpful. This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. If the bug is still relevant, please remove the "stalebug" whiteboard tag. |
Created attachment 214664 [details] screen shot of dialog waiting for a respose I got some unit tests running on my local machine (where I can see the display) and saw this "hang" caused by a user prompt. At least, I'm assuming its not intentional, and the test would sit there for 2 hours until is was forcefully killed by ant. I'll attach a screen shot, but at the time of this prompt, the command line running the test was 4433 davidw 02:23 13.5 1769824 230568 2181176 /home/davidw/jdks/ibm-java-x86_64-60-SR9FP2/jre/bin/java -Xms40m -Xmx384m -XX:MaxPermSize=256m -DPLUGIN_PATH= -classpath /home/shared/hudson/hudsonhome/jobs/eclipse-JUnit-Linux2/workspace/ws/2012-04-27_01-59-03/eclipse-testing/test-eclipse/eclipse/plugins/org.eclipse.equinox.launcher_1.3.0.v20120308-1358.jar org.eclipse.core.launcher.Main -application org.eclipse.test.uitestapplication -data /home/shared/hudson/hudsonhome/jobs/eclipse-JUnit-Linux2/workspace/ws/2012-04-27_01-59-03/eclipse-testing/test-eclipse/eclipse/team_test_workspace formatter=org.apache.tools.ant.taskdefs.optional.junit.XMLJUnitResultFormatter,/home/shared/hudson/hudsonhome/jobs/eclipse-JUnit-Linux2/workspace/ws/2012-04-27_01-59-03/eclipse-testing/test-eclipse/eclipse/org.eclipse.team.tests.core.AllTeamUITests.xml -testPluginName org.eclipse.team.tests.core -className org.eclipse.team.tests.core.AllTeamUITests -os linux -ws gtk -arch x86_64 -consolelog -timeout 7200000