From: Zooko O'Whielacronx <zooko@zooko.com>
Date: Wed, 30 Jul 2008 22:35:36 +0000 (-0700)
Subject: tests: don't use SignalMixin
X-Git-Url: https://git.rkrishnan.org/vdrive/components/com_hotproperty/provisioning?a=commitdiff_plain;h=6aabaa0797b1f2c8fe553351f4ca3e5cd26ff39a;p=tahoe-lafs%2Ftahoe-lafs.git

tests: don't use SignalMixin
It seems like we no longer need it, and it screws up something internal in
trial which causes trial's TestCase.mktemp() method to exhibit wrong behavior
(always using a certain test method name instead of using the current test
method name), and I wish to use TestCase.mktemp().

Of course, it is possible that the buildbot is about to tell me that we do
still require SignalMixin on some of our platforms...
---

diff --git a/src/allmydata/test/common.py b/src/allmydata/test/common.py
index 9f737273..1f6a91d6 100644
--- a/src/allmydata/test/common.py
+++ b/src/allmydata/test/common.py
@@ -194,8 +194,7 @@ class LoggingServiceParent(service.MultiService):
         return log.msg(*args, **kwargs)
 
 
-class SystemTestMixin(testutil.SignalMixin, testutil.PollMixin,
-                      testutil.StallMixin):
+class SystemTestMixin(testutil.PollMixin, testutil.StallMixin):
 
     def setUp(self):
         self.sparent = service.MultiService()