[CalendarServer-changes] [10225] CalendarServer/branches/users/glyph/queue-locking-and-timing
source_changes at macosforge.org
source_changes at macosforge.org
Fri Jan 4 16:38:36 PST 2013
Revision: 10225
http://trac.calendarserver.org//changeset/10225
Author: glyph at apple.com
Date: 2013-01-04 16:38:36 -0800 (Fri, 04 Jan 2013)
Log Message:
-----------
Make sure that workers actually exist too.
Modified Paths:
--------------
CalendarServer/branches/users/glyph/queue-locking-and-timing/twext/enterprise/test/test_queue.py
Property Changed:
----------------
CalendarServer/branches/users/glyph/queue-locking-and-timing/
Modified: CalendarServer/branches/users/glyph/queue-locking-and-timing/twext/enterprise/test/test_queue.py
===================================================================
--- CalendarServer/branches/users/glyph/queue-locking-and-timing/twext/enterprise/test/test_queue.py 2013-01-05 00:38:35 UTC (rev 10224)
+++ CalendarServer/branches/users/glyph/queue-locking-and-timing/twext/enterprise/test/test_queue.py 2013-01-05 00:38:36 UTC (rev 10225)
@@ -173,6 +173,7 @@
proto = wlf.buildProtocol(None)
proto.makeConnection(StringTransport())
# Sanity check.
+ self.assertEqual(len(self.pcp.workerPool.workers), 1)
self.assertEqual(self.pcp.workerPool.hasAvailableCapacity(), True)
# Now it has some capacity.
self.checkPerformer(WorkerConnectionPool)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/calendarserver-changes/attachments/20130104/05869236/attachment-0001.html>
More information about the calendarserver-changes
mailing list