JDK-6829250 : Reg test: java/awt/Toolkit/ScreenInsetsTest/ScreenInsetsTest.java fails in Windows
  • Type: Bug
  • Component: client-libs
  • Sub-Component: java.awt
  • Affected Version: 7,8,9,16
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: windows_xp
  • CPU: x86
  • Submitted: 2009-04-13
  • Updated: 2022-12-05
  • Resolved: 2022-05-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 11 JDK 17 JDK 19 JDK 8 Other
11.0.18-oracleFixed 17.0.6-oracleFixed 19 b23Fixed 8u361Fixed openjdk8u372Fixed
Related Reports
Duplicate :  
JDK-8253398 - Toolkit.getScreenInsets() returns wrong value for some screens
Duplicate :  
JDK-6983430 - test/java/awt/Toolkit/ScreenInsetsTest/ScreenInsetsTest.java fails
Relates :  
JDK-8176359 - Frame#setMaximizedbounds not working properly in multi screen environments
Relates :  
JDK-4737788 - jframe undecorated cover taskbar when maximized
Description
The regression test java/awt/Toolkit/ScreenInsetsTest/ScreenInsetsTest.java fails in windows with jdk7b55 pit build. Also tested with jdk7b51 build where it fails.
It fails with the following output:

java.lang.RuntimeException: TEST FAILED: Toolkit.getScreenInsets() returns wrong value for some screensut:

Attached is the .jtr file.
Comments
Fix Request (8u). On behalf of Josh Cao joshcao@amazon.com. Oracle parity test-only fix, test passes.
21-10-2022
A pull request was submitted for review. URL: https://git.openjdk.org/jdk8u-dev/pull/145 Date: 2022-10-20 19:33:00 +0000
20-10-2022
Fix request [11u] Had to manually merge test/jdk/ProblemList.txt The test test/jdk/java/awt/Toolkit/ScreenInsetsTest/ScreenInsetsTest.java cherry-pick clean. Trivial test fix, parity with 11.0.18-oracle Checked manually on Windows, test passes. Pipelines with tier1, tier2 ok.
07-10-2022
Fix request [17u] Clean backport, parity with 17.0.6-oracle Trivial test fix. Checked manually on Windows, test passes. Pipelines with tier1, tier2 ok.
07-10-2022
A pull request was submitted for review. URL: https://git.openjdk.org/jdk11u-dev/pull/1396 Date: 2022-10-07 03:02:37 +0000
07-10-2022
A pull request was submitted for review. URL: https://git.openjdk.org/jdk17u-dev/pull/774 Date: 2022-10-07 02:59:14 +0000
07-10-2022
Changeset: f56396f1 Author: Alexander Zuev <kizune@openjdk.org> Date: 2022-05-13 22:08:44 +0000 URL: https://git.openjdk.java.net/jdk/commit/f56396f1689ea7e13dea78dcb1d14dcce94da898
13-05-2022
A pull request was submitted for review. URL: https://git.openjdk.java.net/jdk/pull/8314 Date: 2022-04-20 05:10:23 +0000
20-04-2022
Assuming that this bug will be solved by updating the test, the Label should be "noreg-self". An alternative to using a Label is to add this bugid to the affected tests.
08-10-2014
RULE java/awt/Toolkit/ScreenInsetsTest/ScreenInsetsTest.java Exception java.lang.RuntimeException: TEST FAILED: Toolkit.getScreenInsets() returns wrong value for some screens
17-09-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
- 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
EVALUATION The problematic test is the regression test for the bug: 4737732 Toolkit.getScreenInsets() doesn't work on Linux/GNOME The test expects that the screen's insets equals to the "difference" between the bounds of the screen and the bounds of the undecorated window in the maximized mode. On Windows, the undecorated window in the maximized mode covers all the screen (including the taskbar area) for some reason (this is a known issue - CR 4737788). So, the test expects that the getScreenInsets returns the zero insets but the getScreenInsets but the getScreenInsets returns the correct insets of the screen and therefore the test fails. Obviously, the failure is not a regression, I'm removing the keyword.
16-04-2009