ywkaras opened a new issue, #9289:
URL: https://github.com/apache/trafficserver/issues/9289

   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:
   ```
   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:  
https://github.com/apache/trafficserver/blob/931e9ac5332e8d9085d93e43f9c0ca6344de65c3/tests/gold_tests/pluginTest/TSVConnFd/TSVConnFd.cc#L835
 .


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to