osmith has uploaded this change for review.

View Change

testenv: podman-main: set watchdog timer to 60s

Increase the timer from 10s to 60s, as with 10s I see jobs failing with:

  ERROR: /tmp/watchdog was not created, exiting

In theory 10s should already be enough, my guess is that if a jenkins
node is currently under a lot of load then the feed command may take
several seconds and so we hit the previous timer. Even if this is not
the cause, I think it is good to rule it out.

Exiting after 60s if the jenkins job was (manually / with connection
loss) aborted is still relatively quick.

Related: OS#6607
Change-Id: Ide7a9d5bc395106cdaa47cec3aa746a978674c9e
---
M _testenv/data/scripts/testenv-podman-main.sh
1 file changed, 3 insertions(+), 3 deletions(-)

git pull ssh://gerrit.osmocom.org:29418/osmo-ttcn3-hacks refs/changes/21/38621/1

diff --git a/_testenv/data/scripts/testenv-podman-main.sh b/_testenv/data/scripts/testenv-podman-main.sh
index 4b080a6..7f1c16e 100755
--- a/_testenv/data/scripts/testenv-podman-main.sh
+++ b/_testenv/data/scripts/testenv-podman-main.sh
@@ -1,8 +1,8 @@
 #!/bin/sh -e
 # Simple watchdog script that exits if either:
-# * testenv doesn't create /tmp/watchdog every 10s
+# * testenv doesn't create /tmp/watchdog every 60s
 # * 4 hours have passed
-# This ensures the podman container stops a few seconds after a jenkins job was
+# This ensures the podman container stops a soon after a jenkins job was
 # aborted, or if a test is stuck in a loop for hours.
 
 echo "Running testenv-podman-main.sh"
@@ -10,7 +10,7 @@
 stop_time=$(($(date +%s) + 3600 * 4))
 
 while [ $(date +%s) -lt $stop_time ]; do
-	sleep 10
+	sleep 60
 
 	if ! [ -e /tmp/watchdog ]; then
 		echo "ERROR: /tmp/watchdog was not created, exiting"

To view, visit change 38621. To unsubscribe, or for help writing mail filters, visit settings.