8278119: ProblemList few headful test failing in macosx12-aarch64 system

[prsadhuk]

Few tests are failing on macos12-aarch64 systems due to mismatch in color value obtained from robot.getPixelColor and expected color.
More details on the failures can be seen in JDK-8277816. Till the root cause is investigated, it is better to problemlist it as it causing failures in CI run.

---

Progress

• Change must not contain extraneous whitespace
• Commit message must refer to an issue
• Change must be properly reviewed

Issue

• JDK-8278119: ProblemList few headful test failing in macosx12-aarch64 system

Reviewers

• Daniel D. Daugherty (@dcubed-ojdk - Reviewer)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/6663/head:pull/6663
$ git checkout pull/6663

Update a local copy of the PR:
$ git checkout pull/6663
$ git pull https://git.openjdk.java.net/jdk pull/6663/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 6663

View PR using the GUI difftool:
$ git pr show -t 6663

Using diff file

Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/6663.diff

[bridgekeeper]

👋 Welcome back psadhukhan! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

[openjdk]

@prsadhuk To determine the appropriate audience for reviewing this pull request, one or more labels corresponding to different subsystems will normally be applied automatically. However, no automatic labelling rule matches the changes in this pull request. In order to have an "RFR" email sent to the correct mailing list, you will need to add one or more applicable labels manually using the /label pull request command.

Applicable Labels

• build
• client
• compiler
• core-libs
• hotspot
• hotspot-compiler
• hotspot-gc
• hotspot-jfr
• hotspot-runtime
• i18n
• ide-support
• javadoc
• jdk
• jmx
• kulla
• net
• nio
• security
• serviceability
• shenandoah

[prsadhuk]

/label add client

[openjdk]

@prsadhuk
The client label was successfully added.

[mlbridge]

Webrevs

• 00: Full (edcc194e)

[dcubed-ojdk]

javax/swing/JTree/4908142/bug4908142.java has
also shown up in some of the sightings on these
machines. You should add that one also.

java/awt/GraphicsDevice/CheckDisplayModes.java has also been
showing up recently, but it has a different failure "exit code 133".
I don't know if you want to include that one.

So there are 8 pretty much solid failures and 2 others that also
show up, but not in every run.

[prsadhuk]

javax/swing/JTree/4908142/bug4908142.java I have a separate review going on for that #6661 has different issue and not color related..
java/awt/GraphicsDevice/CheckDisplayModes.java also has different root cause unlike present in JDK-8277816 so I would like it to be not here..

[dcubed-ojdk]

Thanks for the clarifications!

[openjdk]

@prsadhuk This change now passes all automated pre-integration checks.

ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details.

After integration, the commit message for the final commit will be:

8278119: ProblemList few headful test failing in macosx12-aarch64 system

Reviewed-by: dcubed

You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed.

At the time when this comment was updated there had been 206 new commits pushed to the master branch:

• fbf096e: 8251400: Fix incorrect addition of library to test in JDK-8237858
• 0a09092: 8268288: jdk/jfr/api/consumer/streaming/TestOutOfProcessMigration.java fails with "Error: ShouldNotReachHere()"
• 0d938ce: 8278172: java/nio/channels/FileChannel/BlockDeviceSize.java should only run on Linux
• 0e7b6bc: 8278141: LIR_OpLoadKlass::_info shadows the field of the same name from LIR_Op
• 53a4342: 8278137: JFR: PrettyWriter uses incorrect year specifier
• f723779: 8278079: C2: expand_dtrace_alloc_probe doesn't take effect in macro.cpp
• 3f28a21: 8278144: Javadoc for MemorySegment::set/MemorySegment::setAtIndex is missing throws tag
• ba2a8e5: 8278205: jlink plugins should dump .class file in debug mode
• 18c54b4: 8274640: Cleanup unnecessary null comparison before instanceof check in java.desktop
• dda8f26: 8278139: G1: Refactor G1BlockOffsetTablePart::block_at_or_preceding
• ... and 196 more: https://git.openjdk.java.net/jdk/compare/2f0bde1a658b0910304c110920a2e8ccbe4557f8...master

As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details.

➡️ To integrate this PR with the above commit message to the master branch, type /integrate in a new comment.

[prsadhuk]

/integrate

[openjdk]

Going to push as commit 660f21a.
Since your change was applied there have been 207 commits pushed to the master branch:

• 2e30fa9: 8278171: [vectorapi] Mask incorrectly computed for zero extending cast
• fbf096e: 8251400: Fix incorrect addition of library to test in JDK-8237858
• 0a09092: 8268288: jdk/jfr/api/consumer/streaming/TestOutOfProcessMigration.java fails with "Error: ShouldNotReachHere()"
• 0d938ce: 8278172: java/nio/channels/FileChannel/BlockDeviceSize.java should only run on Linux
• 0e7b6bc: 8278141: LIR_OpLoadKlass::_info shadows the field of the same name from LIR_Op
• 53a4342: 8278137: JFR: PrettyWriter uses incorrect year specifier
• f723779: 8278079: C2: expand_dtrace_alloc_probe doesn't take effect in macro.cpp
• 3f28a21: 8278144: Javadoc for MemorySegment::set/MemorySegment::setAtIndex is missing throws tag
• ba2a8e5: 8278205: jlink plugins should dump .class file in debug mode
• 18c54b4: 8274640: Cleanup unnecessary null comparison before instanceof check in java.desktop
• ... and 197 more: https://git.openjdk.java.net/jdk/compare/2f0bde1a658b0910304c110920a2e8ccbe4557f8...master

Your commit was automatically rebased without conflicts.

[openjdk]

@prsadhuk Pushed as commit 660f21a.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.