From f3b96e63dbce9a1f3e824f4330347e4063164329 Mon Sep 17 00:00:00 2001
From: egahlin <unknown>
Date: Sat, 8 Dec 2018 17:41:17 +0100
Subject: [PATCH] 8213617: JFR should record the PID of the recorded process
 Reviewed-by: mgronlun

---
 test/jdk/jfr/event/runtime/TestVMInfoEvent.java | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/test/jdk/jfr/event/runtime/TestVMInfoEvent.java b/test/jdk/jfr/event/runtime/TestVMInfoEvent.java
index 0ae1a7736..175ff603c 100644
--- a/test/jdk/jfr/event/runtime/TestVMInfoEvent.java
+++ b/test/jdk/jfr/event/runtime/TestVMInfoEvent.java
@@ -37,6 +37,7 @@ import jdk.jfr.consumer.RecordedEvent;
 import jdk.test.lib.Asserts;
 import jdk.test.lib.jfr.EventNames;
 import jdk.test.lib.jfr.Events;
+import jdk.test.lib.process.ProcessTools;
 
 /**
  * The test will verify that JVM Information event values are delivered
@@ -64,6 +65,8 @@ public class TestVMInfoEvent {
 
             String jvmArgs = Events.assertField(event, "jvmArguments").notNull().getValue();
             String jvmFlags = Events.assertField(event, "jvmFlags").notNull().getValue();
+            Long pid = Events.assertField(event, "pid").atLeast(0L).getValue();
+            Asserts.assertEquals(pid, ProcessTools.getProcessId());
             String eventArgs = (jvmFlags.trim() + " " + jvmArgs).trim();
             String beanArgs = mbean.getInputArguments().stream().collect(Collectors.joining(" "));
             Asserts.assertEquals(eventArgs, beanArgs, "Wrong inputArgs");
-- 
GitLab