[tahoe-lafs-trac-stream] [Tahoe-LAFS] #2034: Update for mutable files is sensitive to the number of servers

[Tahoe-LAFS]

#2034: Update for mutable files is sensitive to the number of servers
------------------------------+-------------------------------------------
     Reporter:  markberger    |      Owner:  warner
         Type:  defect        |     Status:  assigned
     Priority:  normal        |  Milestone:  1.10.1
    Component:  code-mutable  |    Version:  1.10.0
   Resolution:                |   Keywords:  mutable publish review-needed
Launchpad Bug:                |
------------------------------+-------------------------------------------
Changes (by warner):

 * keywords:  mutable publish => mutable publish review-needed
 * owner:  markberger => warner
 * status:  new => assigned


Comment:

 I tried Mark's original advice (increasing the number of servers in
 `allmydata.test.test_mutable.Update` from the default of 10 to 13). Both
 10 and 13 pass with current trunk (including the db12f1c fix). If I back
 out db12f1c, then `num_servers=13` causes the original failure listed
 above, and `num_servers=10` does not.

 So I think that simply changing num_servers to 13 is enough to test this.
 https://github.com/tahoe-lafs/tahoe-lafs/pull/149 does that.

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