8257487: Include configuration name in summary

[magicus]

According to the enhancement request:

It would be nice and convenient to include the configuration name in the configuration summary, for example ("Name" being new):

Configuration summary:
* Name: my-conf
* Debug level: release
* HS debug level: product
* JVM variants: server
...

---

Progress

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

Issue

• JDK-8257487: Include configuration name in summary

Reviewers

• Aleksey Shipilev (@shipilev - Reviewer)

Download

$ git fetch https://git.openjdk.java.net/jdk pull/1534/head:pull/1534
$ git checkout pull/1534

[bridgekeeper]

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

@magicus The following label will be automatically applied to this pull request:

• build

When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command.

[mlbridge]

Webrevs

• 00: Full (25b31bf)

[shipilev]

I was under impression it was printed already, but it is not! Current build only prints the configuration path in build, which you can derive the config name from it. Printing the configuration name explicitly would be a nice touch for sure. Looks good.

[openjdk]

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

8257487: Include configuration name in summary

Reviewed-by: shade

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:

• aa2d36f: 8256807: C2: Not marking stores correctly as mismatched in string opts

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.

[magicus]

/integrate

[openjdk]

@magicus Since your change was applied there have been 2 commits pushed to the master branch:

• 021dced: 8257415: ZGC: Fix barrier_data types
• aa2d36f: 8256807: C2: Not marking stores correctly as mismatched in string opts

Your commit was automatically rebased without conflicts.

Pushed as commit 60f2ba9.

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