8262416: ProblemList TestHeapDumpForLargeArray.java due to JDK-8262386

[plummercj]

Although the test is technically in :hotspot_resourcehogs, I put it in the :hotspot_serviceability section since I don't expect it to be problem listed for long, and didn't think it was worth adding a new problem list section for it,

---

Progress

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

Issue

• JDK-8262416: ProblemList TestHeapDumpForLargeArray.java due to JDK-8262386

Reviewers

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

Download

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

[bridgekeeper]

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

@plummercj 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

• 2d
• awt
• beans
• build
• compiler
• core-libs
• hotspot
• hotspot-compiler
• hotspot-gc
• hotspot-jfr
• hotspot-runtime
• i18n
• javadoc
• jdk
• jmx
• kulla
• net
• nio
• security
• serviceability
• shenandoah
• sound
• swing

[dcubed-ojdk]

Thumbs up. This is a trivial fix.

[openjdk]

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

8262416: ProblemList TestHeapDumpForLargeArray.java due to JDK-8262386

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

• 228c285: 8261170: Upgrade to freetype 2.10.4

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.

[plummercj]

/integrate

[openjdk]

@plummercj Since your change was applied there has been 1 commit pushed to the master branch:

• 228c285: 8261170: Upgrade to freetype 2.10.4

Your commit was automatically rebased without conflicts.

Pushed as commit 35c0a69.

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