Bug ID: JDK-8287699 jdk/jfr/api/consumer/TestRecordingFileWrite.java fails with exception: java.lang.Exception: Found event that should not be there.

Versions (Unresolved/Resolved/Fixed)

The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.

JDK 20	JDK 21
20 b29Fixed	21Fixed

jdk/jfr/api/consumer/TestRecordingFileWrite.java fails with exception:
java.lang.Exception: Found event that should not be there. See log
	at jdk.jfr.api.consumer.TestRecordingFileWrite.verify(TestRecordingFileWrite.java:79)
	at jdk.jfr.api.consumer.TestRecordingFileWrite.main(TestRecordingFileWrite.java:66)
	at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:104)
	at java.base/java.lang.reflect.Method.invoke(Method.java:578)
	at com.sun.javatest.regtest.agent.MainWrapper$MainThread.run(MainWrapper.java:127)
	at java.base/java.lang.Thread.run(Thread.java:1585)

JavaTest Message: Test threw exception: java.lang.Exception: Found event that should not be there. See log
JavaTest Message: shutting down test

STATUS:Failed.`main' threw exception: java.lang.Exception: Found event that should not be there. See log

Changeset: 0ba47348 Author: Markus Grönlund <mgronlun@openjdk.org> Date: 2022-12-16 10:46:37 +0000 URL: https://git.openjdk.org/jdk20/commit/0ba473489151d74c8a15b75ff4964ac480fecb28
16-12-2022
A pull request was submitted for review. URL: https://git.openjdk.org/jdk20/pull/41 Date: 2022-12-15 14:48:17 +0000
15-12-2022
A pull request was submitted for review. URL: https://git.openjdk.org/jdk/pull/11692 Date: 2022-12-15 12:58:11 +0000
15-12-2022
A pull request was submitted for review. URL: https://git.openjdk.org/jdk/pull/11588 Date: 2022-12-08 12:21:40 +0000
08-12-2022
While debugging this, incorrect recording data were found before scrubbing even happens. See JDK-8288482. As of today, it looks like a separate issue, but it makes debugging harder if the original recording is incorrect.
15-06-2022
Looks like the parser is not able to resolve the compiler thread (becomes null) after the file has been scrubbed. With the original and scrubbed recording file attached, it should not be too hard to see where things go wrong. This is a product bug.
02-06-2022
Found: jdk.ThreadCPULoad { startTime = 21:13:52.889 (2022-06-01) user = 1.95% system = 0.17% } Expected: jdk.ThreadCPULoad { startTime = 21:13:52.889 (2022-06-01) user = 1.95% system = 0.17% eventThread = "C2 CompilerThread2" (javaThreadId = 15, virtual = false) }
02-06-2022

Duplicate :	JDK-8293864 - Kitchensink24HStress.java fails with SIGSEGV in JfrCheckpointManager::lease
Relates :	JDK-8289692 - JFR: Thread checkpoint no longer enforce mutual exclusion post Loom integration
Relates :	JDK-8277131 - JEP 425: Virtual Threads (Preview)
Relates :	JDK-8288482 - JFR: Cannot resolve method

JDK-8289951 :	ProblemList jdk/jfr/api/consumer/TestRecordingFileWrite.java on linux-x64 and macosx-x64 - Resolved
JDK-8296822 :	ProblemList jdk/jfr/api/consumer/TestRecordingFileWrite.java - Resolved