JDK-6560348 : PIT : java/awt/xembed/server/RunTestXEmbed.java fails
  • Type: Bug
  • Component: client-libs
  • Sub-Component: java.awt
  • Affected Version: 6u2,7
  • Priority: P4
  • Status: Closed
  • Resolution: Fixed
  • OS: generic,solaris_10
  • CPU: generic,sparc
  • Submitted: 2007-05-22
  • Updated: 2011-03-07
  • Resolved: 2011-03-07
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 7 Other
7 b126Fixed OpenJDK6Fixed
Related Reports
Duplicate :  
JDK-6847159 - test/java/awt/xembed/server/RunTestXEmbed.java fails
Description
PIT : java/awt/xembed/server/RunTestXEmbed.java fails in  6u2 B03 pit build. The testcase fails in solaris & linux. I have attached the log.
Comments
EVALUATION http://hg.openjdk.java.net/jdk7/build/jdk/rev/9deace8396f9
17-01-2011
EVALUATION Pushed: http://hg.openjdk.java.net/jdk7/tl/jdk/rev/9deace8396f9
23-12-2010
EVALUATION The evaluation submitted by the author of the fix: This test fails when it's started on default desktop in Fedora 1x and RHEL 5/6. Original version of this test works correctly only in cases where the top of the screen is "free" (it can contains common windows, icons etc. of course). But in default Gnome configuration on Fedoras and RHELs top of the screen is occupied by panel containing Gnome menu and several widgets (NetworkManager, clocks, sound volume...). It means that common window (frame) cannot be created with y-coordinate set to zero, because such window is automatically moved down by circa 25 pixels (depending on theme used, of course). And this test does not correctly compute y-coordinates of both its windows (client and server). There are several ways to fix this issue, but the simplest one is to create client and server window using non-zero y-coordinates.
20-12-2010
EVALUATION Problem I noticed is not related to embedding, but is in getting rectangles of some components right after they are created. They (rectangles) are used by a Robot, which performs some mouse clicking. On X, after toplevel is created, it gets asynchroniously reparented by window manager, which causes (asynchronious) relayout of components. We're not synchronizing with these, so we sometimes get wrong rectangles. Robot will then click in the wrong places, and some tests may fail. Not sure, if XEmbed problems really exist... If rectangles problem is corrected, test passes.
22-10-2007
EVALUATION This is not a regression in 6u2-b03 build, at least I also see some test failures with 7.0 latest builds. It seems that the test itself is not robust enough and should be corrected, in particular how XEMBED_WINDOW_ACTIVATED is handled. It is also possible that some bugs in our XEmbed implementation exist.
25-05-2007