aboutsummaryrefslogtreecommitdiff
path: root/scripts/testing
diff options
context:
space:
mode:
authorCraig Jennings <c@cjennings.net>2026-06-25 08:35:28 -0400
committerCraig Jennings <c@cjennings.net>2026-06-25 08:35:28 -0400
commitfe84b71ce4f0476d485257410e90f3621d6c5dbe (patch)
tree44362e8f828639eda7dfc89591c3306fa83015ba /scripts/testing
parentce83e4aac50055bdb7926fca1448a9864d122715 (diff)
downloadarchsetup-fe84b71ce4f0476d485257410e90f3621d6c5dbe.tar.gz
archsetup-fe84b71ce4f0476d485257410e90f3621d6c5dbe.zip
fix(testing): raise the install monitor timeout to 150 minutes
A full archsetup install with heavy AUR builds (vagrant and its git-cloned installers) can run past the old 90-minute monitor cap on a slow mirror. When that happened the run stopped monitoring mid-install and validated a half-installed system, producing spurious late-step failures. Raise MAX_POLLS from 180 to 300 (90 -> 150 minutes) so a slow-but-healthy install completes.
Diffstat (limited to 'scripts/testing')
-rwxr-xr-xscripts/testing/run-test.sh5
1 files changed, 3 insertions, 2 deletions
diff --git a/scripts/testing/run-test.sh b/scripts/testing/run-test.sh
index 6e51fc2..a22ae98 100755
--- a/scripts/testing/run-test.sh
+++ b/scripts/testing/run-test.sh
@@ -249,7 +249,8 @@ fi
# Poll for completion
step "Monitoring archsetup progress (polling every 30 seconds)..."
POLL_COUNT=0
-MAX_POLLS=180 # 90 minutes max (180 * 30 seconds)
+MAX_POLLS=300 # 150 minutes max (300 * 30 seconds); a full install with heavy
+ # AUR builds (e.g. vagrant) can exceed 90 min on a slow mirror
while [ $POLL_COUNT -lt $MAX_POLLS ]; do
# Check if archsetup process is still running
@@ -270,7 +271,7 @@ while [ $POLL_COUNT -lt $MAX_POLLS ]; do
done
if [ $POLL_COUNT -ge $MAX_POLLS ]; then
- error "ArchSetup timed out after 90 minutes"
+ error "ArchSetup timed out after 150 minutes"
ARCHSETUP_EXIT_CODE=124
else
# Get exit code from the remote log