From f2f8ede11fc4c5985c155da45937c53ad3acfc88 Mon Sep 17 00:00:00 2001 From: Brian Warner Date: Mon, 16 Feb 2009 18:06:43 -0700 Subject: [PATCH] test/no_network: update comments with setup timing: no_network takes 50ms, SystemTestMixin takes 2s (on my laptop) --- src/allmydata/test/no_network.py | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/src/allmydata/test/no_network.py b/src/allmydata/test/no_network.py index dbc361fc3..2b075883b 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