zope.testing gives UnboundLocalError on nfail
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Zope 3 |
Fix Released
|
Undecided
|
Unassigned | ||
collective.buildout |
Fix Released
|
Undecided
|
Unassigned | ||
zope.testing |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
I'm running the plone.z3cform tests in a Zope 2.10 instance with
zope.testing 3.8 installed.
All other tests seem to work OK, but with plone.z3cform's tests, I get:
$ ./bin/instance test -s plone.z3cform
Running tests at level 1
Running plone.z3cform.
Set up plone.z3cform.
Running:
.......
Ran 26 tests with 0 failures and 0 errors in 0.219 seconds.
Running zope.testing.
Tear down plone.z3cform.
Exception in thread Thread-1:
Traceback (most recent call last):
File
"/opt/local/
line 442, in __bootstrap
self.run()
File
"/opt/local/
line 422, in run
self.
File
"/Users/
line 418, in spawn_layer_
while nfail > 0:
UnboundLocalError: local variable 'nfail' referenced before assignment
Total: 26 tests, 0 failures, 0 errors in 5.626 seconds.
The tests are here:
http://
Changed in zope3: | |
status: | New → Fix Released |
Changed in collective.buildout: | |
status: | New → Fix Released |
Changed in zope.testing: | |
status: | New → Fix Released |
That bug is supposedly fixed by
http:// mail.zope. org/pipermail/ checkins/ 2009-July/ 036586. html
It is triggered by other bug :
The test runner is trying to spawn a subprocess with the --resume-layer
argument. However, the --resume-layer argument is not accepted by the
subprocess.
This produces an error in a format not foreseen by the error parser.
(which then triggered the UnboundLocalError).