[tahoe-lafs-trac-stream] [Tahoe-LAFS] #3481: The introducer fixture in the integration tests is generated with bogus configuration when local neither ip nor ifconfig are found in the usual locations

[Tahoe-LAFS]

#3481: The introducer fixture in the integration tests is generated with bogus
configuration when local neither ip nor ifconfig are found in the usual
locations
---------------------+---------------------------
 Reporter:  exarkun  |          Owner:
     Type:  defect   |         Status:  new
 Priority:  normal   |      Milestone:  undecided
Component:  unknown  |        Version:  n/a
 Keywords:           |  Launchpad Bug:
---------------------+---------------------------
 `_synchronously_find_addresses_via_config` will return an empty list if it
 cannot find one of the tools it wants to use.  It mostly looks at some
 hard-coded locations but it will try to search PATH for ifconfig.
 However, the integration tests launch the introducer process with PATH
 unset so this case never works.

 https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3480 is about the problem in
 general.  This ticket is about the mistake of leaving PATH unset for the
 child processes and then continuing to try to run the integration tests
 even if the introducer has an unusable configuration.

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