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

cmdLineTester_jfrEvents_0 Required condition was not found: [Output match: jdk.JavaMonitorEnter] #21429

Open
JasonFengJ9 opened this issue Mar 19, 2025 · 1 comment

Comments

@JasonFengJ9
Copy link
Member

JasonFengJ9 commented Mar 19, 2025

Failure link

From internal Test_openjdk24_j9_sanity.functional_aarch64_linux_testList_1 (rtj-rhel10aarch64-svl-test-2)

openjdk version "24" 2025-03-18
IBM Semeru Runtime Open Edition 24.0-m1 (build 24+36)
Eclipse OpenJ9 VM 24.0-m1 (build v0.51.0-release-70f26c921d, JRE 24 Linux aarch64-64-Bit Compressed References 20250318_16 (JIT enabled, AOT enabled)
OpenJ9   - 70f26c921d
OMR      - 20241356e
JCL      - c8ca8c74788 based on jdk-24+36)

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

Optional info

Failure output (captured from console output)

[2025-03-17T18:23:01.243Z] variation: NoOptions
[2025-03-17T18:23:01.243Z] JVM_OPTIONS:  

[2025-03-17T18:30:43.623Z] Testing: test jfr monitor enter - approx 30seconds
[2025-03-17T18:30:43.623Z] Test start time: 2025/03/17 14:30:35 Eastern Standard Time
[2025-03-17T18:30:43.623Z] Running command: /home/jenkins/workspace/Test_openjdk24_j9_sanity.functional_aarch64_linux_testList_1/jdkbinary/j2sdk-image/bin/jfr print --xml --events "JavaMonitorEnter" --stack-depth 1 defaultJ9recording.jfr
[2025-03-17T18:30:43.623Z] Time spent starting: 4 milliseconds
[2025-03-17T18:30:43.623Z] Time spent executing: 798 milliseconds
[2025-03-17T18:30:43.623Z] Test result: FAILED
[2025-03-17T18:30:43.623Z] Output from test:
[2025-03-17T18:30:43.623Z]  [OUT] <?xml version="1.0" encoding="UTF-8"?>
[2025-03-17T18:30:43.623Z]  [OUT] <recording xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
[2025-03-17T18:30:43.623Z]  [OUT]   <events>
[2025-03-17T18:30:43.623Z]  [OUT]   </events>
[2025-03-17T18:30:43.623Z]  [OUT] </recording>
[2025-03-17T18:30:43.623Z] >> Required condition was found: [Output match: http://www.w3.org/2001/XMLSchema-instance]
[2025-03-17T18:30:43.623Z] >> Required condition was not found: [Output match: jdk.JavaMonitorEnter]
[2025-03-17T18:30:43.623Z] >> Required condition was not found: [Output match: eventThread]
[2025-03-17T18:30:43.624Z] >> Required condition was not found: [Output match: osName]
[2025-03-17T18:30:43.624Z] >> Required condition was not found: [Output match: osThreadId]
[2025-03-17T18:30:43.624Z] >> Required condition was not found: [Output match: javaName]
[2025-03-17T18:30:43.624Z] >> Success condition was not found: [Output match: stackTrace]
[2025-03-17T18:30:43.624Z] >> Failure condition was not found: [Output match: jfr print: could not read recording]
[2025-03-17T18:30:43.624Z] 
[2025-03-17T18:30:43.624Z] 
[2025-03-17T18:30:43.624Z] ---TEST RESULTS---
[2025-03-17T18:30:43.624Z] Number of PASSED tests: 4 out of 5
[2025-03-17T18:30:43.624Z] Number of FAILED tests: 1 out of 5
[2025-03-17T18:30:43.624Z] 
[2025-03-17T18:30:43.624Z] ---SUMMARY OF FAILED TESTS---
[2025-03-17T18:30:43.624Z] test jfr monitor enter - approx 30seconds
[2025-03-17T18:30:43.624Z] -----------------------------
[2025-03-17T18:30:43.624Z] 
[2025-03-17T18:30:43.624Z] -----------------------------------
[2025-03-17T18:30:43.624Z] cmdLineTester_jfrEvents_0_FAILED

50x internal Grinder - all failed

FYI @tajila

@thallium
Copy link
Contributor

I think this has been fixed by a later PR as this is no longer reproducible with latest branches.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants