| Summary: | [find/replace] Test failures on Linux - selection destroyed | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Dani Megert <daniel_megert> | ||||
| Component: | Text | Assignee: | Rajesh <rthakkar> | ||||
| Status: | VERIFIED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | deepakazad, markus.kell.r, rthakkar | ||||
| Version: | 3.7 | ||||||
| Target Milestone: | 3.7 M2 | ||||||
| Hardware: | PC | ||||||
| OS: | Linux-GTK | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Dani Megert
Rajesh, can you get access to a Linux machine somehow? It also looks like the very first time a search string is entered and something selected, it resets the selection in the find field to column 0. Maybe related to bug 323272? In your latest patch you removed the runEventQueue() call that Markus added in testShiftEnterReversesSearchDirection, why? This fails now on Linux. The other failing test is testFocusNotChangedWhenButtonMnemonicPressed. >I've commented them out for now.
Reverted testShiftEnterReversesSearchDirection to the version from Markus. Please try to test your next version of the patch on a Linux box.
(In reply to comment #2) > In your latest patch you removed the runEventQueue() call that Markus added in > testShiftEnterReversesSearchDirection, why? This fails now on Linux. > > The other failing test is testFocusNotChangedWhenButtonMnemonicPressed. The runEventQueue call that Markus added in testShiftEnterReversesSearchDirection is still there in the last patch, it just got moved down one line which shouldn't matter. The other changes in that method are required for the Traverse listener in the application to be called, else by calling traverse on the shell will cause the Selection listener in the application to be called, which means Traverse listener will not get tested. Like you said earlier, the issue could be related to bug 323272. I will look around for a Linux box, not sure if I can get one easily. >The runEventQueue call that Markus added in >testShiftEnterReversesSearchDirection is still there in the last patch, Right. >I will look around for a Linux box, not sure if I can get one easily. Otherwise you will have to do it on our build machine once you got introduced to it. (In reply to comment #4) > The runEventQueue call that Markus added in > testShiftEnterReversesSearchDirection is still there in the last patch, it just > got moved down one line which shouldn't matter. I haven't debugged it, but I think it does matter. FindReplaceDialog#fActiveShell is set from a ShellListener, and the reason for putting runEventQueue(); in front of Shell shell= ((Shell)fFindReplaceDialog.get("fActiveShell")); was to make sure the shell has really been activated (which happens asynchronously on GTK, see bug 286244). (In reply to comment #5) > >I will look around for a Linux box, not sure if I can get one easily. > Otherwise you will have to do it on our build machine once you got introduced > to it. I have emailed you the details of the Linux machine I use for testing. Created attachment 177938 [details]
Fix
Dani, you were right, the shell activation event hasn't happened which is why the runEventQueue call needed to be where it was. Changes work on GTK and Windows.
Thanks for the patch. Committed to HEAD. Available in builds >= N20100901-2000. Verified in I20100914-0100. |