Kami commented on PR #1807:
URL: https://github.com/apache/libcloud/pull/1807#issuecomment-1343488221

   And there is yet another issue related to re-using the same port each time 
which causes issues when running multiple tests in parallel using multiple 
processes - 
https://github.com/apache/libcloud/actions/runs/3652800376/jobs/6171593038.
   
   ```bash
   Exception in thread Thread-3:
   Traceback (most recent call last):
     File "/opt/hostedtoolcache/PyPy/3.7.13/x64/lib-python/3/threading.py", 
line 926, in _bootstrap_inner
       self.run()
     File "/opt/hostedtoolcache/PyPy/3.7.13/x64/lib-python/3/threading.py", 
line 870, in run
       self._target(*self._args, **self._kwargs)
     File 
"/home/runner/work/libcloud/libcloud/libcloud/test/common/test_google.py", line 
311, in _get_code
       received_code = self.conn.get_code()
     File "/home/runner/work/libcloud/libcloud/libcloud/common/google.py", line 
439, in get_code
       code = self._receive_code_through_local_loopback()
     File "/home/runner/work/libcloud/libcloud/libcloud/common/google.py", line 
533, in _receive_code_through_local_loopback
       server = HTTPServer(server_address=server_address, 
RequestHandlerClass=AccessCodeReceiver)
     File "/opt/hostedtoolcache/PyPy/3.7.13/x64/lib-python/3/socketserver.py", 
line 452, in __init__
       self.server_bind()
     File "/opt/hostedtoolcache/PyPy/3.7.13/x64/lib-python/3/http/server.py", 
line 137, in server_bind
       socketserver.TCPServer.server_bind(self)
     File "/opt/hostedtoolcache/PyPy/3.7.13/x64/lib-python/3/socketserver.py", 
line 466, in server_bind
       self.socket.bind(self.server_address)
   OSError: [Errno 98] Address already in use
   ```
   
   Pushed a quick fix in ea0bf7c3cb740f26eb107df80a13c374065b30e2, but it may 
require more work (will need to dig in to see if any other tests exercise that 
code as well, since those would be also affected).


-- 
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