8226933: [TEST_BUG]GTK L&F: There is no swatches or RGB tab in JColorChooser

[GoeLin]

I backport this for parity with 17.0.15-oracle.

---

Progress

• Change must not contain extraneous whitespace
• Commit message must refer to an issue
• JDK-8226933 needs maintainer approval

Issue

• JDK-8226933: [TEST_BUG]GTK L&F: There is no swatches or RGB tab in JColorChooser (Bug - P4 - Approved)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk17u-dev.git pull/3198/head:pull/3198
$ git checkout pull/3198

Update a local copy of the PR:
$ git checkout pull/3198
$ git pull https://git.openjdk.org/jdk17u-dev.git pull/3198/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 3198

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk17u-dev/pull/3198.diff

Using Webrev

Link to Webrev Comment

[bridgekeeper]

👋 Welcome back goetz! 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]

@GoeLin 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:

8226933: [TEST_BUG]GTK L&F: There is no swatches or RGB tab in JColorChooser

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 1 new commit pushed to the master branch:

• 53d7539: 8336942: Improve test coverage for class loading elements with annotations of different retentions

Please see this link for an up-to-date comparison between the source branch of this pull request and the master branch.
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.

[openjdk]

This backport pull request has now been updated with issue from the original commit.

[openjdk]

⚠️ @GoeLin This change is now ready for you to apply for maintainer approval. This can be done directly in each associated issue or by using the /approval command.

[mlbridge]

Webrevs

• 00: Full (843da6b3)

[GoeLin]

/integrate

[openjdk]

Going to push as commit 59f98c1.
Since your change was applied there have been 13 commits pushed to the master branch:

• 7c825dd: 8314225: SIGSEGV in JavaThread::is_lock_owned
• 06c8242: 8198237: [macos] Test java/awt/Frame/ExceptionOnSetExtendedStateTest/ExceptionOnSetExtendedStateTest.java fails
• b0286b3: 8327505: Test com/sun/jmx/remote/NotificationMarshalVersions/TestSerializationMismatch.java fails
• 6a1576d: 8317636: Improve heap walking API tests to verify correctness of field indexes
• 0228f7c: 8208565: [TEST_BUG] javax\swing\PopupFactory\6276087\NonOpaquePopupMenuTest.java throws NPE
• c93489b: 8314610: hotspot can't compile with the latest of gtest because of
• 36481dd: 8328368: Convert java/awt/image/multiresolution/MultiDisplayTest/MultiDisplayTest.java applet test to main
• 4dab8ba: 8311306: Test com/sun/management/ThreadMXBean/ThreadCpuTimeArray.java failed: out of expected range
• fe3e985: 8292704: sun/security/tools/jarsigner/compatibility/Compatibility.java use wrong key size for EC
• ce49efd: 8292588: [macos] Multiscreen/MultiScreenLocationTest/MultiScreenLocationTest.java: Robot.mouseMove test failed on Screen #0
• ... and 3 more: https://git.openjdk.org/jdk17u-dev/compare/96100ad2f4c71d924468c1feed37f323eebf91dc...master

Your commit was automatically rebased without conflicts.

[openjdk]

@GoeLin Pushed as commit 59f98c1.

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