United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
Bug ID: JDK-6560348 PIT : java/awt/xembed/server/RunTestXEmbed.java fails
JDK-6560348 : PIT : java/awt/xembed/server/RunTestXEmbed.java fails

Details
Type:
Bug
Submit Date:
2007-05-22
Status:
Closed
Updated Date:
2011-03-07
Project Name:
JDK
Resolved Date:
2011-03-07
Component:
client-libs
OS:
generic,solaris_10
Sub-Component:
java.awt
CPU:
sparc,generic
Priority:
P4
Resolution:
Fixed
Affected Versions:
6u2,7
Fixed Versions:

Related Reports
Backport:
Duplicate:

Sub Tasks

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

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.
                                     
2007-05-25
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.
                                     
2007-10-22
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.
                                     
2010-12-20
EVALUATION

Pushed:

http://hg.openjdk.java.net/jdk7/tl/jdk/rev/9deace8396f9
                                     
2010-12-23
EVALUATION

http://hg.openjdk.java.net/jdk7/build/jdk/rev/9deace8396f9
                                     
2011-01-17



Hardware and Software, Engineered to Work Together