8317834: java/lang/Thread/IsAlive.java timed out

[DarraghClarke]

Currently the IsAlive test occasionally times out.

This PR changes the timeout from 10 to 25 which I think is an adequate increase based on the failures I've seen. Though I'd be happy to change it to another value if someone thinks 25 isn't ideal.

---

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-8317834: java/lang/Thread/IsAlive.java timed out (Bug - P4)

Reviewers

• Daniel Fuchs (@dfuch - Reviewer) ⚠️ Review applies to cd13a00c
• Alan Bateman (@AlanBateman - Reviewer)
• David Holmes (@dholmes-ora - Reviewer)
• Aleksey Shipilev (@shipilev - Reviewer)

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 16659

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

Using diff file

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

Webrev

Link to Webrev Comment

[bridgekeeper]

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

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

• 01: Full - Incremental (d3ac2694)
• 00: Full (cd13a00c)

[AlanBateman]

Can it just run with the default timeout, meaning drop /timeout=N ? Also does this test need really need to run in othervm mode?

[dfuch]

Looks reasonable to me. Let's give it at least 48 hours before integrating though, to let folks who might have an opinion (@dholmes-ora ?) to chime in.

[openjdk]

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

8317834: java/lang/Thread/IsAlive.java timed out

Reviewed-by: dfuchs, alanb, dholmes, 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 40 new commits pushed to the master branch:

• 9faead1: 8319927: Log that IEEE rounding mode was corrupted by loading a library
• f33c874: 8319764: C2 compilation asserts during incremental inlining because Phi input is out of bounds
• 6868b37: 8318826: C2: "Bad graph detected in build_loop_late" with incremental inlining
• 1d96886: 8319531: FileServerHandler::discardRequestBody could be improved
• 73e19f6: 8319825: jdk.net/jdk.net.ExtendedSocketOptions::IP_DONTFRAGMENT is missing @SInCE 19
• faeea07: 8319747: galoisCounterMode_AESCrypt stack walking broken
• b4c2d1c: 8319542: Fix boundaries of region to be tested with os::is_readable_range
• c36ec2c: 8316653: Large NMethodSizeLimit triggers assert during C1 code buffer allocation
• 2db9ea9: 8317723: C2: CountedLoopEndNodes and Zero Trip Guards are wrongly treated as Runtime Predicate
• eaa4417: 8319301: Static analysis warnings after JDK-8318016
• ... and 30 more: https://git.openjdk.org/jdk/compare/9c98270737cd2019f230e9359bb9298f8df2ca35...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.

[dholmes-ora]

Seems fine. If it ever times out again then we know we have a real problem. :)

I suspect, as Alan suggested, the othervm could be dropped, but I'm not concerned about it staying.

Thanks

[shipilev]

Yeah, OK. IIRC, we did the /timeout=10 initially so that the eventual bug case would take less than 240*TIMEOUT_FACTOR seconds to complete and fail. But given the non-buggy execution should actually pass, and on overloaded machines it could take a while to get to termination, just using the default is fine.

[DarraghClarke]

/integrate

[openjdk]

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

• 9194d2c: 8317357: Update links in building.md to use https rather than http
• 368e4f6: 8315801: [PPC64] JNI code should be more similar to the Panama implementation
• 8ec6b8d: 8319876: Reduce memory consumption of VM_ThreadDump::doit
• bbf52e0: 8319897: Move StackWatermark handling out of LockStack::contains
• 129c470: 8311932: Suboptimal compiled code of nested loop over memory segment
• 369bbec: 8319896: Remove monitor deflation from final audit
• 1588dd9: 8319567: Update java/lang/invoke tests to support vm flags
• 9727f4b: 8320199: Fix HTML 5 errors in java.math.BigInteger
• d6aa7c8: 8314621: ClassNotFoundException due to lambda reference to elided anonymous inner class
• 52e2878: 8319987: compilation of sealed classes leads to infinite recursion
• ... and 44 more: https://git.openjdk.org/jdk/compare/9c98270737cd2019f230e9359bb9298f8df2ca35...master

Your commit was automatically rebased without conflicts.

[openjdk]

@DarraghClarke Pushed as commit 5522656.

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