Commit e77765f2d2 for bind

commit e77765f2d2a041ff3856f10fff8a0a196c8064d1
Author: Michal Nowak <mnowak@isc.org>
Date:   Tue Sep 15 08:22:36 2026 +0000

    Use sequential run ids in the pairwise testing script

    The pairwise job names each per-configuration directory after
    ${RANDOM}, a 15-bit value.  With two dozen configurations per run the
    chance that two of them draw the same number is close to 1%, and when
    that happens "mkdir" fails on the duplicate name and "set -e" aborts
    the whole job.  Number the runs sequentially instead, which also makes
    the uploaded pairwise-output.*.txt artifacts easy to map back to the
    order in pairwise-commands.txt.

    Assisted-by: Claude:claude-fable-5-1

diff --git a/util/pairwise-testing.sh b/util/pairwise-testing.sh
index 7ab00b52a8..9c5a9e58a5 100755
--- a/util/pairwise-testing.sh
+++ b/util/pairwise-testing.sh
@@ -53,8 +53,9 @@ pict pairwise-model.txt | tr "\t" " " | sed "1d" >pairwise-commands.txt

 rm -rf build-pairwire-default

+runid=0
 while read -r -a configure_switches; do
-  runid=${RANDOM}
+  runid=$((runid + 1))
   mkdir "pairwise-${runid}"
   cd "pairwise-${runid}"
   echo "Configuration:" "${configure_switches[@]}" | tee "../pairwise-output.${runid}.txt"
@@ -75,8 +76,8 @@ while read -r -a configure_switches; do
     echo "Unexpected exit code from the 'timeout' utility (${ret})"
     exit 1
   fi
-  rm -rf build
   # "timeout" is unable to report a crash on shutdown via its exit
   # code.
   cd ..
+  rm -rf "pairwise-${runid}"
 done <pairwise-commands.txt