From 68ff152517cc9578b1695ed236833df5c38a2ffb Mon Sep 17 00:00:00 2001
From: Babneet Singh <sbabneet@ca.ibm.com>
Date: Mon, 23 Dec 2024 12:11:07 -0500
Subject: [PATCH] Increase JFR test suite timeout to 30 mins

The increased timeout should provide sufficient time for the JFR tests
to complete.

Related: #20865

Signed-off-by: Babneet Singh <sbabneet@ca.ibm.com>
---
 test/functional/cmdLineTests/jfr/jfr.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/test/functional/cmdLineTests/jfr/jfr.xml b/test/functional/cmdLineTests/jfr/jfr.xml
index 1f8f93c2891..b6a11fafe0a 100644
--- a/test/functional/cmdLineTests/jfr/jfr.xml
+++ b/test/functional/cmdLineTests/jfr/jfr.xml
@@ -24,7 +24,7 @@ SPDX-License-Identifier: EPL-2.0 OR Apache-2.0 OR GPL-2.0-only WITH Classpath-ex
 
 <!DOCTYPE suite SYSTEM "cmdlinetester.dtd">
 
-<suite id="JFR Tests" timeout="300">
+<suite id="JFR Tests" timeout="1800">
 	<envvar name="OPENJ9_METADATA_BLOB_FILE_PATH" value="$METADATA_BLOB_PATH$" />
 	<test id="triggerExecutionSample">
 		<command>$EXE$ -XX:StartFlightRecording --add-exports java.base/com.ibm.oti.vm=ALL-UNNAMED -cp $RESJAR$ org.openj9.test.TriggerExecutionSample</command>