Skip to content
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

serviceability_jvmti_j9_1_FAILED serviceability/jvmti/thread/GetStackTrace/getstacktr07/getstacktr07.java Fatal error: SetBreakpoint failed #19691

Closed
JasonFengJ9 opened this issue Jun 12, 2024 · 10 comments · Fixed by adoptium/aqa-tests#5385

Comments

@JasonFengJ9
Copy link
Member

JasonFengJ9 commented Jun 12, 2024

Failure link

From an internal build(macaarch64rt1):

openjdk version "22.0.1-beta" 2024-04-16
IBM Semeru Runtime Open Edition 22.0.1+8-202406120002 (build 22.0.1-beta+8-202406120002)
Eclipse OpenJ9 VM 22.0.1+8-202406120002 (build master-58b586d83e, JRE 22 Mac OS X aarch64-64-Bit 20240612_88 (JIT enabled, AOT enabled)
OpenJ9   - 58b586d83e
OMR      - 873509033
JCL      - ae28e24bf based on jdk-22.0.1+8)

Rerun in Grinder - Change TARGET to run only the failed test targets.

Optional info

Failure output (captured from console output)

[2024-06-12T09:24:22.047Z] variation: Mode650
[2024-06-12T09:24:22.047Z] JVM_OPTIONS:  -XX:-UseCompressedOops -Xverbosegclog 

[2024-06-12T09:25:16.669Z] TEST: serviceability/jvmti/thread/GetStackTrace/getstacktr07/getstacktr07.java

[2024-06-12T09:25:16.671Z] STDERR:
[2024-06-12T09:25:16.671Z] JVMVMUT015W Warning: Extended HCR is disabled, enable with -XX:+EnableExtendedHCR.
[2024-06-12T09:25:16.671Z] 
[2024-06-12T09:25:16.671Z] Fatal error: SetBreakpoint failed.

[2024-06-12T09:26:27.240Z] serviceability_jvmti_j9_1_FAILED

It is related to

FYI @tajila

@tajila
Copy link
Contributor

tajila commented Jun 12, 2024

@JasonFengJ9 @LongyuZhang Do either of you know home to modify the options we run jtreg tests with?

@JasonFengJ9
Copy link
Member Author

Assuming this test needs to run with -XX:+EnableExtendedHCR, @tajila I will add it.

@pshipton
Copy link
Member

Options can be added to individual tests.
https://github.com/ibmruntimes/openj9-openjdk-jdk22/blob/openj9/test/hotspot/jtreg/serviceability/jvmti/thread/GetStackTrace/getstacktr07/getstacktr07.java#L42

Options can be added when we run the entire bucket.
https://github.com/adoptium/aqa-tests/blob/master/openjdk/playlist.xml#L409

Isn't it bad that something which is expected to work isn't working without the option?

@pshipton
Copy link
Member

pshipton commented Jun 12, 2024

Test description

 *     The test exercises JVMTI function GetStackTrace via breakpoint
 *     and consequent class redefinition.
 *     The test starts a new thread, does some nested calls, stops at breakpoint,
 *     redefines the class and checks if the number of frames in the thread's
 *     stack is as expected and the function returns all the expected frames.

@requires vm.continuations

@tajila
Copy link
Contributor

tajila commented Jun 12, 2024

Assuming this test needs to run with -XX:+EnableExtendedHCR, @tajila I will add it.

Thanks

@JasonFengJ9
Copy link
Member Author

@pshipton
Copy link
Member

@tajila pls explain why it's ok to ignore the failing test.

Do we really want to run all the serviceability tests with -XX:+EnableExtendedHCR, which hides any problems caused by turning off the feature by default?

@tajila
Copy link
Contributor

tajila commented Jun 14, 2024

I didn't actually look too closely at the test. I assumed it was doing something that required extended capabilities. Ill take another look at it.

tajila added a commit to tajila/openj9 that referenced this issue Jun 14, 2024
The current implementwation emits a warning message when a JVMTI
operation suceeds.

Also, clear breakpoints unconditionally when a class is redefined.

Fixes: eclipse-openj9#19691

Signed-off-by: tajila <[email protected]>
tajila added a commit to tajila/openj9 that referenced this issue Jun 14, 2024
The current implementwation emits a warning message when a JVMTI
operation suceeds.

Also, clear breakpoints unconditionally when a class is redefined.

Fixes: eclipse-openj9#19691

Signed-off-by: tajila <[email protected]>
@tajila
Copy link
Contributor

tajila commented Jun 14, 2024

@JasonFengJ9 did this only fail in JDK22?

@JasonFengJ9
Copy link
Member Author

did this only fail in JDK22?

@tajila serviceability_jvmti_j9 is enabled for JDK 21+, and it failed at JDK21 aarch64_linux as well

tajila added a commit to tajila/openj9 that referenced this issue Jun 17, 2024
The current implementwation emits a warning message when a JVMTI
operation suceeds.

Also, clear breakpoints unconditionally when a class is redefined as
required by the spec.

Fixes: eclipse-openj9#19691

Signed-off-by: tajila <[email protected]>
tajila added a commit to tajila/openj9 that referenced this issue Jun 18, 2024
The current implementwation emits a warning message when a JVMTI
operation suceeds.

Also, clear breakpoints unconditionally when a class is redefined as
required by the spec.

Fixes: eclipse-openj9#19691

Signed-off-by: tajila <[email protected]>
tajila added a commit to tajila/openj9 that referenced this issue Jun 18, 2024
The current implementwation emits a warning message when a JVMTI
operation suceeds.

Also, clear breakpoints unconditionally when a class is redefined as
required by the spec.

Fixes: eclipse-openj9#19691

Signed-off-by: tajila <[email protected]>
tajila added a commit to tajila/openj9 that referenced this issue Jun 25, 2024
The current implementwation emits a warning message when a JVMTI
operation suceeds.

Also, clear breakpoints unconditionally when a class is redefined as
required by the spec.

Fixes: eclipse-openj9#19691

Signed-off-by: tajila <[email protected]>
tajila added a commit to tajila/openj9 that referenced this issue Jun 25, 2024
The current implementwation emits a warning message when a JVMTI
operation suceeds.

Also, clear breakpoints unconditionally when a class is redefined as
required by the spec.

Fixes: eclipse-openj9#19691

Signed-off-by: tajila <[email protected]>
tajila added a commit to tajila/openj9 that referenced this issue Jun 25, 2024
The current implementwation emits a warning message when a JVMTI
operation suceeds.

Also, clear breakpoints unconditionally when a class is redefined as
required by the spec.

Fixes: eclipse-openj9#19691

Signed-off-by: tajila <[email protected]>
tajila added a commit to tajila/openj9 that referenced this issue Jun 25, 2024
The current implementwation emits a warning message when a JVMTI
operation suceeds.

Also, clear breakpoints unconditionally when a class is redefined as
required by the spec.

Fixes: eclipse-openj9#19691

Signed-off-by: tajila <[email protected]>
tajila added a commit to tajila/openj9 that referenced this issue Jun 25, 2024
The current implementwation emits a warning message when a JVMTI
operation suceeds.

Also, clear breakpoints unconditionally when a class is redefined as
required by the spec.

Fixes: eclipse-openj9#19691

Signed-off-by: tajila <[email protected]>
tajila added a commit to tajila/openj9 that referenced this issue Jun 25, 2024
The current implementwation emits a warning message when a JVMTI
operation suceeds.

Also, clear breakpoints unconditionally when a class is redefined as
required by the spec.

Fixes: eclipse-openj9#19691

Signed-off-by: tajila <[email protected]>
tajila added a commit to tajila/openj9 that referenced this issue Jun 25, 2024
The current implementwation emits a warning message when a JVMTI
operation suceeds.

Also, clear breakpoints unconditionally when a class is redefined as
required by the spec.

Fixes: eclipse-openj9#19691

Signed-off-by: tajila <[email protected]>
tajila added a commit to tajila/openj9 that referenced this issue Jun 25, 2024
The current implementwation emits a warning message when a JVMTI
operation suceeds.

Also, clear breakpoints unconditionally when a class is redefined as
required by the spec.

Fixes: eclipse-openj9#19691

Signed-off-by: tajila <[email protected]>
tajila added a commit to tajila/openj9 that referenced this issue Jun 25, 2024
The current implementwation emits a warning message when a JVMTI
operation suceeds.

Also, clear breakpoints unconditionally when a class is redefined as
required by the spec.

Fixes: eclipse-openj9#19691

Signed-off-by: tajila <[email protected]>
tajila added a commit to tajila/openj9 that referenced this issue Jun 25, 2024
The current implementwation emits a warning message when a JVMTI
operation suceeds.

Also, clear breakpoints unconditionally when a class is redefined as
required by the spec.

Fixes: eclipse-openj9#19691

Signed-off-by: tajila <[email protected]>
tajila added a commit to tajila/openj9 that referenced this issue Jun 25, 2024
The current implementwation emits a warning message when a JVMTI
operation suceeds.

Also, clear breakpoints unconditionally when a class is redefined as
required by the spec.

Fixes: eclipse-openj9#19691

Signed-off-by: tajila <[email protected]>
tajila added a commit to tajila/openj9 that referenced this issue Jun 25, 2024
The current implementwation emits a warning message when a JVMTI
operation suceeds.

Also, clear breakpoints unconditionally when a class is redefined as
required by the spec.

Fixes: eclipse-openj9#19691

Signed-off-by: tajila <[email protected]>
tajila added a commit to tajila/openj9 that referenced this issue Jun 25, 2024
The current implementwation emits a warning message when a JVMTI
operation suceeds.

Also, clear breakpoints unconditionally when a class is redefined as
required by the spec.

Fixes: eclipse-openj9#19691

Signed-off-by: tajila <[email protected]>
tajila added a commit to tajila/openj9 that referenced this issue Jun 25, 2024
The current implementwation emits a warning message when a JVMTI
operation suceeds.

Also, clear breakpoints unconditionally when a class is redefined as
required by the spec.

Fixes: eclipse-openj9#19691

Signed-off-by: tajila <[email protected]>
tajila added a commit to tajila/openj9 that referenced this issue Jun 25, 2024
The current implementwation emits a warning message when a JVMTI
operation suceeds.

Also, clear breakpoints unconditionally when a class is redefined as
required by the spec.

Fixes: eclipse-openj9#19691

Signed-off-by: tajila <[email protected]>
tajila added a commit to tajila/openj9 that referenced this issue Jun 25, 2024
The current implementwation emits a warning message when a JVMTI
operation suceeds.

Also, clear breakpoints unconditionally when a class is redefined as
required by the spec.

Fixes: eclipse-openj9#19691

Signed-off-by: tajila <[email protected]>
tajila added a commit to tajila/openj9 that referenced this issue Jun 27, 2024
The current implementwation emits a warning message when a JVMTI
operation suceeds.

Also, clear breakpoints unconditionally when a class is redefined as
required by the spec.

Fixes: eclipse-openj9#19691

Signed-off-by: tajila <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants