This occurs on Solaris/Linux on AWT PIT build for mustang b38

java version "1.6.0-awt.pit-int-awt-blade"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.6.0-awt.pit-int-awt-blade-dm97671_11_May_2005_10_32-b00)
Java HotSpot(TM) Client VM (build 1.6.0-ea-b35, mixed mode)

The regression testcase java/awt/xembed/server/RunTestXEmbed.java fails. The jtr file attached.
  xxxxx@xxxxx   2005-05-18 05:20:34 GMT

N/A

From .jtr the client is missing WINDOW_ACTIVATED - most likely a problem in the test case.  Not critical for Mustang, but should investigate in Dolphin before we integrate browser feature.
  xxxxx@xxxxx   2005-05-26 12:52:05 GMT
I have found many interesting things about the test, and the problems are not with the test itself only, but also inside Xembed implementation.

First, the test always reports it is passed even if some test cases inside are failed (with the exception of timeouts, crashes, etc.) So the test should be modified to handle test cases failures correctly.

Second, all the test cases are always failed on my desktop. Most often the failing check is the very first one: 'waitWindowActivated'. This message should be sent by XEmbedCanvasPeer when it finds a client reparented into it. However, the corresponding XReparentNotify never gets dispatched to the XEmbedCanvasPeer because of quite another bug: 6501838.

I have a temporary fix for 6501838 and with this fix all other XEmbed server test cases seem to pass. So I'm waiting for the fix for 6501838 to be integrated and then putback the fix for java/awt/xembed/server/RunTestXEmbed.java test.
Posted Date : 2006-12-13 01:39:40.0