RFR: 8288912: vmTestbase/nsk/stress/strace/strace002.java fails with Unexpected method name: currentCarrierThread [v3]
Leonid Mesnik
lmesnik at openjdk.org
Wed Feb 22 00:16:25 UTC 2023
On Tue, 21 Feb 2023 20:57:54 GMT, Leonid Mesnik <lmesnik at openjdk.org> wrote:
>> The fix simplifies stack verification. It doesn't check the method name for system classes.
>> The StraceBase is used as a base class, not a utility class, to simplify future refactoring.
>
> Leonid Mesnik has updated the pull request incrementally with one additional commit since the last revision:
>
> doc updated
The test calls different chains of method invocations of java and native methods in different states (alive, blocked) and verifies that getStackFrames looks correct. The stack might contain test classes with 3 different methods and some system classes. The test relies on system classes and their internal implementations. So it might start intermittently failing again if the implementation is changed. So it doesn't make sense to test method names for system classes at least.
So the test makes now only a sanity check that all classes and names are valid. Just to ensure that they are not corrupted.
-------------
PR: https://git.openjdk.org/jdk/pull/12638
More information about the hotspot-runtime-dev
mailing list