From 88c73362cebd370c6473c9aa10a9599c0eaa724f Mon Sep 17 00:00:00 2001
From: Craig Comstock <craig.comstock@northern.tech>
Date: Wed, 25 Jun 2025 10:33:14 -0500
Subject: [PATCH] Adjusted valgrind-check auto_destruct timeout from 30m to 40m

Some build hosts weren't finishing in 30 minutes so see if 40 is enough.

Ticket: ENT-13080
Changelog: none
---
 tests/valgrind-check/valgrind.sh | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tests/valgrind-check/valgrind.sh b/tests/valgrind-check/valgrind.sh
index d5d7ed84f3..34716fec64 100644
--- a/tests/valgrind-check/valgrind.sh
+++ b/tests/valgrind-check/valgrind.sh
@@ -62,7 +62,7 @@ set -x
 # cleaned up from here rather than relying on the outer environment doing the
 # cleanup. In case this runs in a container, it could be a big
 # difference. Especially in a case of an SPC.
-{ sleep 30m && kill -9 $$; } &
+{ sleep 40m && kill -9 $$; } &
 auto_destruct_pid=$!
 trap "kill $auto_destruct_pid" EXIT