-
Notifications
You must be signed in to change notification settings - Fork 4
Closed
Description
In CI we see new JFR tests fail with JDK 25+26 based builds:
Error: JFRTest.jfrOptionsSmokeTest:784->jfrOptionsSmoke:922 build-and-run.log log should not contain error or warning lines that are not whitelisted. See /home/runner/work/mandrel/mandrel/mandrel-integration-tests/testsuite/target/archived-logs/org.graalvm.tests.integration.JFRTest/jfrOptionsSmokeTest/build-and-run.log and check these offending 2 lines:
[warn][jfr,system ] Exception occurred during execution of event jdk.MethodTiming(13364). jdk.jfr.internal.JVM.drainStaleMethodTracerIds()[J [symbol: Java_jdk_jfr_internal_JVM_drainStaleMethodTracerIds or Java_jdk_jfr_internal_JVM_drainStaleMethodTracerIds__]
[warn][jfr,setting] Exception occurred when setting value "false". jdk.jfr.internal.JVM.setCPUThrottle(DZ)V [symbol: Java_jdk_jfr_internal_JVM_setCPUThrottle or Java_jdk_jfr_internal_JVM_setCPUThrottle__DZ] ==> expected: <true> but was: <false>
This is likely related to the integration of the following JEPs in JDK 25:
JEP 518: JFR Cooperative Sampling
JEP 520: JFR Method Timing & Tracing
JEP 509: JFR CPU-Time Profiling (Experimental)
For example this implementation bug got added in JDK 25+26. Similar this bug: https://bugs.openjdk.org/browse/JDK-8352738 from JEP 520.
See this failure from a CI run:
https://github.com/graalvm/mandrel/actions/runs/15598778230/job/43936113803#step:11:10009
Metadata
Metadata
Assignees
Labels
No labels