8314835: gtest wrappers should be marked as flagless

[MBaesken]

---

Progress

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

Issue

• JDK-8314835: gtest wrappers should be marked as flagless (Sub-task - P4 - Approved)

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 282

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

Using diff file

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

Webrev

Link to Webrev Comment

[bridgekeeper]

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

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

[openjdk]

⚠️ @MBaesken 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 (4617c7c6)

[GoeLin]

/approve yes

[openjdk]

@GoeLin
8314835: The approval request has been approved.

[openjdk]

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

8314835: gtest wrappers should be marked as flagless

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 no new commits pushed to the master branch. If another commit should be pushed before you perform the /integrate command, your PR will be automatically rebased. If you prefer to avoid any potential 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.

[MBaesken]

/integrate

[openjdk]

Going to push as commit 2c38047.
Since your change was applied there has been 1 commit pushed to the master branch:

• c80bb72: 8325254: CKA_TOKEN private and secret keys are not necessarily sensitive

Your commit was automatically rebased without conflicts.

[openjdk]

@MBaesken Pushed as commit 2c38047.

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