From: Zooko O'Whielacronx Date: Tue, 10 Feb 2009 06:53:48 +0000 (-0700) Subject: immutable: tests: the real WRITE_LEEWAY is 35 (it was a mistake to move it from 10... X-Git-Tag: allmydata-tahoe-1.3.0~50 X-Git-Url: https://git.rkrishnan.org/pf/content?a=commitdiff_plain;h=d436c6235dbabad0ad7f33ef6c559cc48a336e5a;p=tahoe-lafs%2Ftahoe-lafs.git immutable: tests: the real WRITE_LEEWAY is 35 (it was a mistake to move it from 10 to 35 earlier -- I had seen a failure in which it took 35 times as many writes as I thought were optimal, but I misread and thought it took only 20 times as many) --- diff --git a/src/allmydata/test/test_repairer.py b/src/allmydata/test/test_repairer.py index 8e9ac0a9..f303aa5d 100644 --- a/src/allmydata/test/test_repairer.py +++ b/src/allmydata/test/test_repairer.py @@ -331,9 +331,9 @@ class Verifier(common.ShareManglingMixin, unittest.TestCase): ], judge) test_verify_server_invisible_corruption_share_hash_tree_TODO.todo = "Verifier doesn't yet properly detect this kind of corruption." -# We'll allow you to pass this test even if you trigger twenty times as many -# block sends and disk writes as would be optimal. -WRITE_LEEWAY = 20 +# We'll allow you to pass this test even if you trigger thirty-five times as many block sends +# and disk writes as would be optimal. +WRITE_LEEWAY = 35 # Optimally, you could repair one of these (small) files in a single write. DELTA_WRITES_PER_SHARE = 1 * WRITE_LEEWAY