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)

This commit is contained in:
Zooko O'Whielacronx 2009-02-09 23:53:48 -07:00
parent c59940852b
commit d436c6235d

View File

@ -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