[Checkins] SVN: lovely.remotetask/branches/gotcha-z3c-taskqueue/src/lovely/remotetask/processor.txt fix processor tests
Godefroid Chapelle
gotcha at bubblenet.be
Thu Apr 22 06:43:37 EDT 2010
Log message for revision 111257:
fix processor tests
Changed:
U lovely.remotetask/branches/gotcha-z3c-taskqueue/src/lovely/remotetask/processor.txt
-=-
Modified: lovely.remotetask/branches/gotcha-z3c-taskqueue/src/lovely/remotetask/processor.txt
===================================================================
--- lovely.remotetask/branches/gotcha-z3c-taskqueue/src/lovely/remotetask/processor.txt 2010-04-22 10:37:11 UTC (rev 111256)
+++ lovely.remotetask/branches/gotcha-z3c-taskqueue/src/lovely/remotetask/processor.txt 2010-04-22 10:43:36 UTC (rev 111257)
@@ -91,7 +91,7 @@
constructors also accept additional arguments, they are specified as well:
>>> tasks.processorFactory
- <class 'lovely.remotetask.processor.SimpleProcessor'>
+ <class 'z3c.taskqueue.processor.SimpleProcessor'>
>>> tasks.processorArguments
{'waitTime': 0.0}
@@ -113,13 +113,18 @@
>>> print log_info
lovely.remotetask INFO
Job: 1
+ z3c.taskqueue INFO
+ starting service tasks
lovely.remotetask INFO
Job: 2
lovely.remotetask INFO
Job: 3
lovely.remotetask INFO
Job: 4
+ z3c.taskqueue INFO
+ stopping service tasks
+
Transactions in jobs
--------------------
@@ -236,12 +241,16 @@
all need different time to execute:
>>> print log_info
+ z3c.taskqueue INFO
+ starting service tasks
lovely.remotetask INFO
Job: 3
lovely.remotetask INFO
Job: 4
lovely.remotetask INFO
Job: 2
+ z3c.taskqueue INFO
+ stopping service tasks
Let's now set the thread limit to two and construct a new set of tasks that
demonstrate that not more than two threads run at the same time:
@@ -269,6 +278,8 @@
>>> transaction.commit()
>>> print log_info
+ z3c.taskqueue INFO
+ starting service tasks
lovely.remotetask INFO
Job: 1
lovely.remotetask INFO
@@ -277,6 +288,8 @@
Job: 3
lovely.remotetask INFO
Job: 4
+ z3c.taskqueue INFO
+ stopping service tasks
Note: Sometimes (about 20% of the time in this test) the log will contain a
conflict error. As long as the error is *not* produced by ``processNext()``,
More information about the checkins
mailing list