Newly enabled jvmti tests should be renamed (remove extended from name)

[smlambert]

Some jvmti tests are named jvmti_extended but are tagged as "sanity" level. In general, we should avoid using the level in the name of a test, as it is confusing when it doesn't match the level its in, and it makes for more changes if we wish to move a test into a different level.

[llxia]

https://github.com/eclipse/openj9/blob/ef9a7abd00e1b27888e79645ba1a8723707e5155/test/functional/cmdLineTests/jvmtitests/playlist.xml#L165

[llxia]

This file already has a test named cmdLineTester_jvmtitests. We cannot simply remove _extended as our current infrastructure does not support test with same name and subsets. I will update the level to extended, so it matches with the name.

Please let me know if there is any other suggestion for the name.

[pshipton]

We should keep the tests as sanity as they have been traditionally run in sanity.

The group seems to only consist of 2 tests, rc015 and rc016. rc016 mentions HCR extended mode so perhaps that could exlain the name. These tests run in modes with jdwp enabled, so perhaps call them "_debug".

[pshipton]

@gacholio any suggestions how we can rename cmdLineTester_jvmtitests_extended so its not confused with extended (vs sanity) testing? See the last 2 comments.

[gacholio]

I'd agree to rename them to debug, or just roll them into one of the other buckets.

[llxia]

Thanks. I will change the name to cmdLineTester_jvmtitests_debug and disable the test until #2129 is resolved. We can roll this test into one of the other buckets when it is all clear.