JDK-8349521 : Test java/awt/Component/ComponentEventTest.java failed: ComponentMoved not triggered for class java.awt.Frame
  • Type: Bug
  • Component: client-libs
  • Sub-Component: java.awt
  • Affected Version: 25
  • Priority: P4
  • Status: Closed
  • Resolution: Duplicate
  • OS: linux_ubuntu
  • Submitted: 2025-02-06
  • Updated: 2025-02-21
  • Resolved: 2025-02-18
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 25
25Resolved
Related Reports
Relates :  
JDK-8350301 - ComponentEventTest.java test fails with exception
Description
Component java.awt.Frame[frame0,578,468,767x139,layout=java.awt.FlowLayout,title=Component Event Test,resizable,normal]
  enabled false
ComponentHidden: java.awt.Frame[frame0,578,468,767x139,hidden,disabled,layout=java.awt.FlowLayout,title=Component Event Test,resizable,normal]
ComponentShown: java.awt.Frame[frame0,578,468,767x139,disabled,layout=java.awt.FlowLayout,title=Component Event Test,resizable,normal]
----------System.err:(13/860)----------
java.lang.RuntimeException: FAIL: ComponentMoved not triggered for class java.awt.Frame
	at ComponentEventTest.doTest(ComponentEventTest.java:308)
	at ComponentEventTest.doTest(ComponentEventTest.java:160)
	at ComponentEventTest.main(ComponentEventTest.java:143)
	at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:104)
	at java.base/java.lang.reflect.Method.invoke(Method.java:565)
	at com.sun.javatest.regtest.agent.MainWrapper$MainTask.run(MainWrapper.java:138)
	at java.base/java.lang.Thread.run(Thread.java:1447)
Comments
This test is supposed to be ProblemListed and this issue was filed when JDK-8348190 had been integrated, which was then backed out, and then re-done under JDK-8349515. So the problem only arises because the problem-list is not being used correctly, which is what JDK-8350129 is addressing. Hence closing as a duplicate.
18-02-2025