]> git.rkrishnan.org Git - tahoe-lafs/tahoe-lafs.git/commit
immutable: further loosen the performance-regression test to allow up to 45 reads
authorZooko O'Whielacronx <zooko@zooko.com>
Sat, 3 Jan 2009 18:41:09 +0000 (11:41 -0700)
committerZooko O'Whielacronx <zooko@zooko.com>
Sat, 3 Jan 2009 18:41:09 +0000 (11:41 -0700)
commit7adf905b9f468b8e71599fbbc2097e77cb61cb0c
treed5458ebaaab730378d5fa2b350c042b1b9354373
parent2788c80496faee799051a6beff70cbcacd4cb9b2
immutable: further loosen the performance-regression test to allow up to 45 reads
This does raise the question of if there is any point to this test, since I apparently don't know what the answer *should* be, and whenever one of the buildbots fails then I redefine success.

But, I'm about to commit a bunch of patches to implement checker, verifier, and repairer as well as to refactor downloader, and I would really like to know if these patches *increase* the number of reads required even higher than it currently is.
src/allmydata/test/test_immutable.py