-
-
Notifications
You must be signed in to change notification settings - Fork 317
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for running custom serviceability jvmti test #5357
Comments
FYI @llxia |
On second thought, instead of creating a separate test target for serviceability, maybe we can leverage the existing aqa-tests/openjdk/playlist.xml Line 98 in feb08ca
Remove aqa-tests/openjdk/playlist.xml Lines 118 to 120 in feb08ca
<impl>openj9</impl> via <disables> .
In this way, openj9 dev users can run any hotspot folder target via @LongyuZhang could you take care of this one? Thanks |
Tested running with |
just for the record, usage for openj9
|
Close this issue as fixed by #5370. |
Note per #5370, for openj9, hotspot_custom can only be used for serviceability jvmti test jdk19+ with the -nativepath set as hotspot native path |
I would prefer to add a custom serviceability jvmti test target instead of using hotspot_custom as a hack, which is confusing. |
Updated the usage for openj9 via #5493:
FYI @fengxue-IS |
I'd like to request ability to run custom serviceability jvmti test.
Ideally with new test target:
serviceability_jvmti_custom
where a custom test path can be provided.
default test to run:
serviceability/jvmti/GetSystemProperty/JvmtiGetSystemPropertyTest.java
The text was updated successfully, but these errors were encountered: