[tahoe-lafs-trac-stream] [Tahoe-LAFS] #3025: Sometimes the test suite hangs in/around allmydata.test.test_runner.RunNode.test_introducer

[Tahoe-LAFS]

#3025: Sometimes the test suite hangs in/around
allmydata.test.test_runner.RunNode.test_introducer
-------------------------+-----------------------
     Reporter:  exarkun  |      Owner:
         Type:  defect   |     Status:  new
     Priority:  normal   |  Milestone:  undecided
    Component:  unknown  |    Version:  1.12.1
   Resolution:           |   Keywords:
Launchpad Bug:           |
-------------------------+-----------------------

Comment (by exarkun):

 With some more logging added, a failed CI run had this to say:

 {{{
 2019-04-09 16:19:12.155Z [-] -->
 allmydata.test.test_runner.RunNode.test_baddir <--
 2019-04-09 16:19:15.241Z [-] Main loop terminated.
 2019-04-09 16:19:15.242Z [-] -->
 allmydata.test.test_runner.RunNode.test_client <--
 2019-04-09 16:19:19.160Z [-] Polling <function _node_has_started at
 0x7f6d596cd410>
 2019-04-09 16:19:19.160Z [-] Polling completed successfully
 2019-04-09 16:21:15.256Z [-] Main loop terminated.
 2019-04-09 16:21:15.257Z [-] -->
 allmydata.test.test_runner.RunNode.test_client_no_noise <--
 2019-04-09 16:21:19.093Z [-] Polling <function _node_has_started at
 0x7f6d5aa02e60>
 2019-04-09 16:21:19.094Z [-] Polling completed successfully
 }}}

 This is a hang in the _third_ test on the test case, not the fourth.
 Unfortunately the logging in that test is not as comprehensive (heh) as in
 `test_introducer` so all I can really surmise is that the hang happened
 after "tahoe start" completed and before "tahoe stop" completed.

 This is somewhat similar to the `test_introducer` behavior, I suppose,
 since in that case it's "tahoe restart" that doesn't complete and
 "restart" implies "stop".

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3025#comment:2>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage