8379551: sun/text/IntHashtable/Bug4705389.java timed out

[naotoj]

Removing the arbitrary time out value from the test case. The time out value seems to have been there for the stop-gap to prevent the infinite loop in the bug case. Without the explicit time out, the jtreg's default time out would kick in, with more detailed thread dumps. (This PR is not intended to fix the intermittent issue described in the bug report which occurred in Valhalla repo, but to better analyse it if the same timeout occurs)

---

Progress

• Change must be properly reviewed (1 review required, with at least 1 Reviewer)
• Change must not contain extraneous whitespace
• Commit message must refer to an issue

Issue

• JDK-8379551: sun/text/IntHashtable/Bug4705389.java timed out (Bug - P4)

Reviewers

• Chen Liang (@liach - Reviewer)
• Jaikiran Pai (@jaikiran - Reviewer)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/30343/head:pull/30343
$ git checkout pull/30343

Update a local copy of the PR:
$ git checkout pull/30343
$ git pull https://git.openjdk.org/jdk.git pull/30343/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 30343

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/30343.diff

Using Webrev

Link to Webrev Comment

[bridgekeeper]

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

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

8379551: sun/text/IntHashtable/Bug4705389.java timed out

Reviewed-by: liach, jpai

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 18 new commits pushed to the master branch:

• d610ace: 8380562: GenShen: GC notification event may see invalid values
• 137d971: 8378935: C2 crash in PhaseOutput::fill_buffer: wrong size of mach node
• d0841c6: 8379688: GenShen: Skip promotions when marking finds enough immediate garbage
• ... and 15 more: https://git.openjdk.org/jdk/compare/9ea893d87749fd87a3d1947e6d71c5899c6380bb...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.

[openjdk]

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

• core-libs

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 (bcf85ae4)

[naotoj]

Thanks for the reviews!
/integrate

[openjdk]

Going to push as commit 0798dd1.
Since your change was applied there have been 44 commits pushed to the master branch:

• 5c2ef74: 8380316: Test runtime/os/AvailableProcessors.java fails Invalid argument
• 60a141c: 8380441: G1: Move G1GCPauseType to G1CollectorState
• 2a64074: 8374706: HttpClient: Ensure that request body publishers support multiple subscriptions
• ... and 41 more: https://git.openjdk.org/jdk/compare/9ea893d87749fd87a3d1947e6d71c5899c6380bb...master

Your commit was automatically rebased without conflicts.

[openjdk]

@naotoj Pushed as commit 0798dd1.

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