Brian Warner
3b1c8ceb86
tests: increase the default timeout for SystemTestMixin -based tests to 300 seconds, since our slower buildslaves sometimes take longer than the default 120s
2009-02-10 14:44:12 -07:00
Zooko O'Whielacronx
ef1bfdd2bf
immutable: repairer: add a simple test to exercise the "leftover" code path, fix the bug (and rename the variable "leftover" to "extra")
2009-02-10 12:12:45 -07:00
Zooko O'Whielacronx
3fa19973e4
docs: not-quite-final version of relnotes.txt for tahoe-1.3.0
2009-02-10 11:02:27 -07:00
Zooko O'Whielacronx
2dcadfaa1b
docs: small edit to about.html
2009-02-10 11:02:19 -07:00
Zooko O'Whielacronx
b09b81894b
docs: NEWS: move the most exciting items to the top, break them out of less exciting categories, update a couple of stale bits, and a touch of editing
2009-02-10 02:48:43 -07:00
Zooko O'Whielacronx
390de8aaa4
docs: edit about.html
2009-02-10 02:01:02 -07:00
Zooko O'Whielacronx
75e4e67ed7
immutable: tighten preconditions -- you can write empty strings or read zero bytes, and add the first simple unit test of DownUpConnector
2009-02-10 00:56:47 -07:00
Zooko O'Whielacronx
d436c6235d
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)
2009-02-09 23:53:48 -07:00
Zooko O'Whielacronx
c59940852b
immutable: defensive programming: assert that the encrypted readable gave you no more than the number of bytes you asked for
...
(There is a bug in the current DownUpConnector which can cause it to give more bytes than you asked for on one request, and then less on the next, effectively shifting some of the bytes to an earlier request, but I think this bug never gets triggered in practice.)
2009-02-09 23:46:05 -07:00
Zooko O'Whielacronx
1d13be3701
docs: suggest Python 2.5 -- Python 2.6 is not as well tested yet
2009-02-09 23:44:21 -07:00
Zooko O'Whielacronx
65c12b24b8
immutable: tests: sigh, raise, again the limit of how many extra writes you can do and still pass this test
...
Obviously requiring the code under test to perform within some limit isn't very meaningful if we raise the limit whenever the test goes outside of it.
But I still don't want to remove the test code which measures how many writes (and, elsewhere, how many reads) a client does in order to fulfill these duties.
Let this number -- now 20 -- stand as an approximation of the inefficiency of our code divided by my mental model of how many operations are actually optimal for these duties.
2009-02-09 20:09:31 -07:00
Zooko O'Whielacronx
5738d94ccd
immutable: tests: assert that verifier gives a clean bill of health after corruption and repair (the previous patch mistakenly did this only after deletion and repair), and also test whether deleting seven other shares and then downloading works. Also count the number of shares stored in the local filesystem.
2009-02-09 20:08:41 -07:00
Zooko O'Whielacronx
bbf48f4a88
immutable: test: add a test after attempting to repair from corruption: does a full verify run give the file a clean bill of health? If not, the you haven't successfully repaired it.
...
This will make the repairer tests more consistent -- less accidentally passing due to getting lucky.
2009-02-09 19:01:49 -07:00
Zooko O'Whielacronx
4091f73f34
immutable: tests: put shares back to their pristine condition in between each test of corrupting-and-repairing them
...
This is important, because if the repairer doesn't completely repair all kinds of corruption (as the current one doesn't), then the successive tests get messed up by assuming that the shares were uncorrupted when the test first set about to corrupt them.
2009-02-09 18:29:56 -07:00
Brian Warner
a9a3b509df
upload: add a think-of-the-compatibility note to UploadResults
2009-02-09 14:50:04 -07:00
Brian Warner
a5ab6c060d
helper #609 : uploading client should ignore old helper's UploadResults, which were in a different format
2009-02-09 14:45:43 -07:00
Brian Warner
b197c5bb8c
test_runner: skip all spawnProcess-using tests on cygwin, since spawnProcess just hangs forever
2009-02-09 02:34:00 -07:00
Brian Warner
19902a0f16
test_runner.py: revert the CreateNode section to using runner() inline, rather than spawning a process, to get more precise coverage
2009-02-09 02:26:17 -07:00
Brian Warner
0b29aae7cf
storage #596 : announce 'tolerates-immutable-read-overrun' to the version announcement, to indicate that a read() on an immutable share where offset+length is beyond the end of the file will return a truncated string instead of raising an exception
2009-02-08 19:56:02 -07:00
Brian Warner
89683a3906
test_upload: add test of maximum-immutable-share-size, to complete the last item of #538
2009-02-08 19:41:27 -07:00
Brian Warner
bbef104315
docs/specifications: add an outline of the spec documents we'd like to have some day
2009-02-08 17:47:48 -07:00
Brian Warner
d8e00c37b5
test_cli.Backup: capture stderr when sqlite is unavailable
2009-02-07 15:14:40 -07:00
Zooko O'Whielacronx
96774fba6b
docs: add mac/README.txt to explain the first few basic facts about what the files are in this directory
2009-02-07 16:33:21 -07:00
Brian Warner
213ef3d64b
test_repairer: wrap comments to 80cols, my laptop does not have a wide screen. No functional changes.
2009-02-07 14:06:26 -07:00
Brian Warner
38ee95fec4
immutable/checker: wrap comments to 80cols, my laptop does not have a wide screen. No functional changes.
2009-02-07 14:04:39 -07:00
Brian Warner
50886ea494
test/common.py: in share-layout-reading code, use '>L' consistently, since '>l' doesn't specify the signedness and the windows tests appear to be failing with an endianness-like problem (version==0x01000000). Also use binary mode when editing sharefiles
2009-02-07 13:38:17 -07:00
Brian Warner
1fd8f023ab
test_cli: increase timeout on test_backup, since our dapper buildslave is really slow
2009-02-06 02:17:53 -07:00
Brian Warner
5bc0ef7ffe
backupdb.py: catch OperationalError on duplicate-insert too, since pysqlite2 on dapper raises it instead of IntegrityError
2009-02-06 01:34:01 -07:00
Brian Warner
9933aa0d49
test_backupdb.py: reset the check-timers after one step, otherwise a slow host can false-fail
2009-02-06 01:33:05 -07:00
Brian Warner
806f6ab426
NEWS: announce the #598 'tahoe backup' command
2009-02-05 23:44:16 -07:00
Brian Warner
177ffa0870
docs/CLI: document 'tahoe backup'
2009-02-05 22:14:45 -07:00
Brian Warner
814fec5495
test_cli.backup: oops, fix test to work even when sqlite is unavailable
2009-02-05 22:10:42 -07:00
Brian Warner
ca32db5b39
#598 : add cli+backupdb tests, improve user display, update docs, move docs out of proposed/
2009-02-05 22:07:01 -07:00
Brian Warner
add0e1f2f8
#598 : add backupdb to 'tahoe backup' command, enable it by default
2009-02-05 19:56:40 -07:00
Brian Warner
4be2e11d11
add sqlite-based backupdb, for #598 and others (including 'tahoe cp'). Not enabled yet.
2009-02-05 18:17:56 -07:00
Zooko O'Whielacronx
9ce226b4d8
setup: require new bundled setuptools-0.6c12dev
2009-02-05 09:29:23 -07:00
Zooko O'Whielacronx
4d785cfe30
setup: bundle setuptools-0.6c12dev (our own toothpick of setuptools) this version completes my patch to fix http://bugs.python.org/setuptools/issue54 , which is necessary for tahoe to build with --prefix=support without doing a lot of PYTHONPATH gymnastics around the call to setup.py
2009-02-05 09:28:18 -07:00
Zooko O'Whielacronx
c900ed8e69
setup: remove old bundled setuptools-0.6c11dev (our own toothpick of setuptools)
2009-02-05 09:27:58 -07:00
Zooko O'Whielacronx
9ba5f9347d
setup: add a case to execute "python .../twistd.py" if "twistd" is not found
2009-02-04 18:06:20 -07:00
Zooko O'Whielacronx
23fd9680cc
doc: specify Python >= 2.4.2
2009-02-04 15:38:40 -07:00
Zooko O'Whielacronx
40179a0ed8
setup: merge recent patches that change the set of bundled tools in misc/dependencies/
2009-02-04 13:32:22 -07:00
Zooko O'Whielacronx
7d22cd4547
setup: bundle new setuptools_trial
2009-02-04 13:24:54 -07:00
Zooko O'Whielacronx
4df4efbaf0
setup: remove old bundled setuptools_trial
2009-02-04 13:24:42 -07:00
Zooko O'Whielacronx
944aa25709
setup: bundle new setuptools_darcs
2009-02-04 13:24:29 -07:00
Zooko O'Whielacronx
a2c1a93822
setup: remove old bundled setuptools_darcs
2009-02-04 13:24:18 -07:00
Zooko O'Whielacronx
759698224a
roll back the upgrade of the bundled setuptools_trial from 0.5 to 0.5.1
...
Upgrading setuptools trial in that way leads to a very tricky problem in setuptools's handling of recursive installation of the build-time dependencies of build-time dependencies...
rolling back:
Tue Feb 3 22:17:18 MST 2009 zooko@zooko.com
* setup: bundle new setuptools_trial-0.5.1
A ./misc/dependencies/setuptools_trial-0.5.1.tar
Tue Feb 3 22:17:32 MST 2009 zooko@zooko.com
* setup: remove old bundled setuptools_trial
R ./misc/dependencies/setuptools_trial-0.5.tar
2009-02-04 01:38:36 -07:00
Zooko O'Whielacronx
b952ed6741
setup: remove a couple of horrible work-arounds in setup.py now that we rely on our own toothpick of setuptools which fixes those issues
...
also specify that we need our latest revision (11dev) of our toothpick of setuptools
also *always* setup_require setuptools_darcs at module import time. Formerly we added setup_require setuptools_darcs only if the PKG-INFO file were not already created. There is some weird, irreproducible bug to do with setuptool_darcs, and I guess that the fact that whether it is required or not depends on that autogenerated file might have something to do with it. Anyway, this is simpler.
2009-02-03 23:24:05 -07:00
Zooko O'Whielacronx
05030112e8
setup: remove old bundled setuptools_trial
2009-02-03 23:17:32 -07:00
Zooko O'Whielacronx
313080fbf0
setup: bundle new setuptools_trial-0.5.1
2009-02-03 23:17:18 -07:00
Zooko O'Whielacronx
4af8c8cd24
setup: bundle new setuptools_darcs-1.2.5
2009-02-03 23:17:04 -07:00
