From: Brian Warner Date: Tue, 17 Feb 2009 01:06:43 +0000 (-0700) Subject: test/no_network: update comments with setup timing: no_network takes 50ms, SystemTest... X-Git-Tag: allmydata-tahoe-1.4.0~207 X-Git-Url: https://git.rkrishnan.org/components/com_hotproperty/%22doc.html/readonly?a=commitdiff_plain;h=f2f8ede11fc4c5985c155da45937c53ad3acfc88;p=tahoe-lafs%2Ftahoe-lafs.git test/no_network: update comments with setup timing: no_network takes 50ms, SystemTestMixin takes 2s (on my laptop) --- diff --git a/src/allmydata/test/no_network.py b/src/allmydata/test/no_network.py index dbc361fc..2b075883 100644 --- a/src/allmydata/test/no_network.py +++ b/src/allmydata/test/no_network.py @@ -5,10 +5,13 @@ # server puts real shares on disk, but is accessed through loopback # RemoteReferences instead of over serialized SSL. It is not as complete as # the common.SystemTestMixin framework (which does use the network), but -# should be considerably faster. It should be useful for tests which want to -# examine and/or manipulate the uploaded shares, checker/verifier/repairer -# tests, etc. The clients have no Tubs, so it is not useful for tests that -# involve a Helper, a KeyGenerator, or the control.furl . +# should be considerably faster: on my laptop, it takes 50-80ms to start up, +# whereas SystemTestMixin takes close to 2s. + +# This should be useful for tests which want to examine and/or manipulate the +# uploaded shares, checker/verifier/repairer tests, etc. The clients have no +# Tubs, so it is not useful for tests that involve a Helper, a KeyGenerator, +# or the control.furl . import os.path import sha