[tahoe-dev] [tahoe-lafs] #819: allmydata.test.test_repairer.Verifier.test_corrupt_crypttext_hashtree failed

[tahoe-lafs]

#819: allmydata.test.test_repairer.Verifier.test_corrupt_crypttext_hashtree
failed
-----------------------+----------------------------------------------------
 Reporter:  zooko      |           Owner:  zooko    
     Type:  defect     |          Status:  new      
 Priority:  major      |       Milestone:  undecided
Component:  code       |         Version:  1.5.0    
 Keywords:  integrity  |   Launchpad_bug:           
-----------------------+----------------------------------------------------
 http://allmydata.org/buildbot/builders/hardy-
 amd64/builds/295/steps/test/logs/stdio

 The unit test corrupted a share and the verifier failed to notice that the
 share was corrupted.

 That test corrupts the share in a random way each time -- it invokes
 [source:src/allmydata/test/common.py?rev=20091013052154-66853-783ac1c5b3a31f082184e0ad2060ecb4a65e2d92#L1347
 _corrupt_crypttext_hash_tree()] which calls
 [source:src/allmydata/test/common.py?rev=20091013052154-66853-783ac1c5b3a31f082184e0ad2060ecb4a65e2d92#L1156
 corrupt_field()] which corrupts the ciphertext hash tree in a randomly
 chosen way.  Unfortunately it doesn't log the way that it chose to corrupt
 it or the random seed that it used so to reproduce this we'll probably
 have to run with the trial {{{--until-failure}}} option or something.  Hm,
 I see that there is a {{{debug}}} flag that you can pass to
 {{{corrupt_field()}}} to get it to log what it is doing.  I'll try that.

-- 
Ticket URL: <http://allmydata.org/trac/tahoe/ticket/819>
tahoe-lafs <http://allmydata.org>
secure decentralized file storage grid