RFR: 8266130: convert Thread-SMR stress tests from counter based to time based

Daniel D.Daugherty dcubed at openjdk.java.net
Sat May 29 13:46:22 UTC 2021


On Fri, 28 May 2021 00:13:25 GMT, Daniel D. Daugherty <dcubed at openjdk.org> wrote:

> The Thread-SMR project added counter based tests for various APIs.
> See "JDK-8167108 inconsistent handling of SR_lock can lead to crashes".
> 
> Time based tests are more appropriate for stress kits so I'm
> updating the counter based tests to be time based instead.
> 
> Two of the updated tests have shaken out failures that are tracked by:
> 
>     JDK-8264605 vmTestbase/nsk/jvmti/SuspendThread/suspendthrd003/TestDescription.java failed with "agent_tools.cpp, 471: (foundThread = (jthread) jni_env->NewGlobalRef(foundThread)) != NULL"
> 
>     JDK-8266593 vmTestbase/nsk/jvmti/PopFrame/popframe011 fails with "assert(java_thread == _state->get_thread()) failed: Must be"
> 
> These updated tests are tested via Mach5 Tier[134567].
> They have also been test by my Stress Kit runs for jdk-17+2[0-4].

Here are my Mach5 Tier[1-7] results:

Mach5 Tier1:
- no failures
- 25 runs of the updated tests in Tier1

Mach5 Tier2:
- 1 known, unrelated failure
- The updated tests don't run in Tier2.

Mach5 Tier3:
- 5 known, unrelated test failures
- 70 runs of the updated tests

Mach5 Tier4:
- 17 runs of the updated tests
- 2 known, unrelated test failures

Mach5 Tier5:
- 56 runs of the updated tests
- 1 known, unrelated failure, 3 failures of the updated tests linked to the known bugs

Mach5 Tier6:
- 122 runs of the updated tests
- 2 failures of the updated tests, linked to the known bugs

Mach5 Tier7:
- 151 runs of the updated tests
- 1 failure of the updated tests, linked to the known bug 

Because of the failures in the upper tiers, when this PR is integrated I will be ProblemListing:

vmTestbase/nsk/jvmti/SuspendThread/suspendthrd003/TestDescription.java 8264605
vmTestbase/nsk/jvmti/PopFrame/popframe011/TestDescription.java 8266593

The suspendthrd003/8264605 failure had been seen one time in the CI on 2021.04.01
(April Fools Day!) and is now much more reproducible with the updated version. The
popframe011/8266593 failure had never been seen before being updated.

-------------

PR: https://git.openjdk.java.net/jdk/pull/4237


More information about the hotspot-runtime-dev mailing list