[tahoe-lafs-trac-stream] [Tahoe-LAFS] #3302: When a test fails because Foolscap cannot bind a port, the failure doesn't include enough information

[Tahoe-LAFS]

#3302: When a test fails because Foolscap cannot bind a port, the failure doesn't
include enough information
---------------------+---------------------------
 Reporter:  exarkun  |          Owner:
     Type:  defect   |         Status:  new
 Priority:  normal   |      Milestone:  undecided
Component:  unknown  |        Version:  n/a
 Keywords:           |  Launchpad Bug:
---------------------+---------------------------
 Sometimes the test suite has failures like:

 {{{
 Traceback (most recent call last):
   File "/tmp/tahoe-lafs.tox/py27-coverage/lib/python2.7/site-
 packages/twisted/internet/defer.py", line 122, in execute
     result = callable(*args, **kw)
   File "/tmp/tahoe-lafs.tox/py27-coverage/lib/python2.7/site-
 packages/twisted/internet/posixbase.py", line 495, in listenTCP
     p.startListening()
   File "/tmp/tahoe-lafs.tox/py27-coverage/lib/python2.7/site-
 packages/twisted/internet/tcp.py", line 1363, in startListening
     raise CannotListenError(self.interface, self.port, le)
 twisted.internet.error.CannotListenError: Couldn't listen on any:38205:
 [Errno 98] Address already in use.
 }}}

 This shows that some TCP server has failed to start because EADDRINUSE.
 This makes debugging such failures infuriating.

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3302>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage