JDK-7124230 : [macosx] Dual screen failure java/awt/Multiscreen/LocationRelativeToTest/LocationRelativeToTest.java
  • Type: Bug
  • Component: client-libs
  • Sub-Component: java.awt
  • Affected Version: 7
  • Priority: P3
  • Status: Open
  • Resolution: Unresolved
  • OS: os_x
  • CPU: generic
  • Submitted: 2011-12-23
  • Updated: 2021-07-13
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
7u6Fixed tbdUnresolved
Related Reports
Duplicate :  
JDK-7124506 - [macosx] Dual screen failure java/awt/Multiscreen/LocationRelativeToTest/LocationRelativeToTest.java
Description
http://java.net/jira/browse/MACOSX_PORT-744 submitted 2011/11/22 by Yuri Nesterenko
Build: b218
java/awt/Multiscreen/LocationRelativeToTest/LocationRelativeToTest.java
Right location for the window center: java.awt.Point<span class=&quot;error&quot;>&#91;x=300,y=250&#93;</span>
Actual location for the window center: java.awt.Point<span class=&quot;error&quot;>&#91;x=-200,y=250&#93;</span>
java.lang.RuntimeException: Test FAILED: setLocationRelativeTo() operates incorrectly
at LocationRelativeToTest.checkLocation(LocationRelativeToTest.java:107)
at LocationRelativeToTest.main(LocationRelativeToTest.java:89)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at com.sun.javatest.regtest.MainWrapper.run(MainWrapper.java:94)
at java.lang.Thread.run(Thread.java:722)
Comments
- this is an issue reported against 7(7u), - there are now affected version 9 filed for this issue - 7u issues are transferred to Sustaining Nevertheless if someone have a report against 9 - please reopen and add affectedVersion 9 or 7u specific escalations might be reopen to Sustaining
10-08-2014
- this is an issue reported against 7(7u), - there are now affected version 9 filed for this issue - 7u issues are transferred to Sustaining Nevertheless if someone have a report against 9 - please reopen and add affectedVersion 9 or 7u specific escalations might be reopen to Sustaining
10-08-2014
We've reviewed your bulk request (120 bugs) and are OK with deferring them to JDK 9. You can go ahead and update these to: - Set label to 8-defer-approved - FixVersion to 9 Thanks for doing a great job of summarizing the details for the bulk deferral for us! Kind regards, Mathias
19-09-2013
The criteria for deferral bulk request bugs: - Not P2 - Not tck-red or conformance labeled - Not regressions reported/labeled against jdk8 - Not findbugs, parfait, eht, fuzzing labeled - Not netbeans, licbug, cap, cap-8 labeled against jdk8
18-09-2013
The criteria for deferral bulk request bugs: - Not P2 - Not tck-red or conformance labeled - Not regressions reported/labeled against jdk8 - Not findbugs, parfait, eht, fuzzing labeled - Not netbeans, licbug, cap, cap-8 labeled against jdk8
18-09-2013
The criteria for deferral bulk request bugs: - Not P2 - Not tck-red or conformance labeled - Not regressions reported/labeled against jdk8 - Not findbugs, parfait, eht, fuzzing labeled - Not netbeans, licbug, cap, cap-8 labeled against jdk8
18-09-2013
The criteria for deferral bulk request bugs: - Not P2 - Not tck-red or conformance labeled - Not regressions reported/labeled against jdk8 - Not findbugs, parfait, eht, fuzzing labeled - Not netbeans, licbug, cap, cap-8 labeled against jdk8
18-09-2013
jdk8: SQE ok to defer!
17-09-2013
Reassigning to AWT engineer.
22-01-2013