tests/gold_tests/autest-site/ports.py isn't very reliable

[ywkaras]

ports.py is used by tests/gold_tests/autest-site/trafficserver.text.ext and other Au Test extensions to find available TCP ports. But, when I ran this script, which run 5 concurrent instances of Au Test:

umask 0
for N in $( seq 1 5 )
do
  mkdir -p $N/TS/tests
  cd $N/TS/tests
  for F in ~/REPOS/TS/tests/*
  do
      ln -s $F
  done

  ./autest.sh --ats-bin ~/TSX/TS/bin -f basic &

  cd ../../..
done

I get these errors:

wkaras ~/LINK_TS
O$ grep -F ERROR: */TS/tests/_sandbox/basic/ts/log/diags.log
1/TS/tests/_sandbox/basic/ts/log/diags.log:[Jan  7 18:38:54.721] [ET_NET 7] ERROR: Could not bind or listen to port 61000 (error: -1)
1/TS/tests/_sandbox/basic/ts/log/diags.log:[Jan  7 18:38:54.721] [ET_NET 7] ERROR: Could not bind or listen to port 61001 (error: -1)
3/TS/tests/_sandbox/basic/ts/log/diags.log:[Jan  7 18:38:54.732] [ET_NET 7] ERROR: Could not bind or listen to port 61000 (error: -1)
3/TS/tests/_sandbox/basic/ts/log/diags.log:[Jan  7 18:38:54.733] [ET_NET 7] ERROR: Could not bind or listen to port 61001 (error: -1)
4/TS/tests/_sandbox/basic/ts/log/diags.log:[Jan  7 18:38:54.706] [ET_NET 7] ERROR: Could not bind or listen to port 61000 (error: -1)
4/TS/tests/_sandbox/basic/ts/log/diags.log:[Jan  7 18:38:54.706] [ET_NET 7] ERROR: Could not bind or listen to port 61001 (error: -1)
wkaras ~/LINK_TS
O$

Perhaps there is no clean solution to this issue. As a work-around, in the dedicated plugin for the TSVConnFd Au Test, I had to use this retry loop:

trafficserver/tests/gold_tests/pluginTest/TSVConnFd/TSVConnFd.cc

Line 835 in 931e9ac

for (int i{0}; ; ++i) {

.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. Marking it stale to flag it for further consideration by the community.

[zwoop]

Closing — addressed by #12867, which added the AUTEST_PORT_OFFSET mechanism to ports.py so concurrent autest runs get non-overlapping port ranges. The new tests/autest-parallel.py runner is the intended way to run tests concurrently and avoids the collisions described here. Please reopen if you still hit port binding errors with the new runner.