Hash: SHA1

Jonathan Lange wrote:
> On Sun, Jul 18, 2010 at 5:56 PM, Hanno Schlichting <ha...@hannosch.eu> wrote:
>> Hi.
>> On Sun, Jul 18, 2010 at 5:50 PM, Jonathan Lange <j...@mumak.net> wrote:
>>> When running zope.testing's tests on my laptop, I get many failures.
>>> I've run the tests plenty of times before and haven't got these
>>> failures. Am a bit mystified, so I'd appreciate any help.
>> Looks like the tests assume to be run under the zope.testing.testrunner:
>> -    runTest (zope.testing.testrunner.runner.SetUpLayerFailure)
>> ?                 --------
>> +    runTest (zope.testrunner.runner.SetUpLayerFailure)
>> but you end up with the one from zope.testrunner. If you pin
>> zc.recipe.testrunner to version 1.2.0, that should do the trick for
>> now.
>> Someone should look into making the tests compatible with both
>> testrunners or requiring the new zope.testrunner.
> Thanks.
> Actually, it turned out to be something of a pebkac. I was getting
> trunk from the old Launchpad branch
> (lp:~vcs-imports/zope.testing/trunk) rather than the new Launchpad
> branch (lp:zope.testing).
> With the new branch, everything works out of the box. Sorry for the noise.
> While we're here, if I want to patch the Zope testrunner, should I
> submit patches against zope.testing or zope.testrunner?

Good question.  We intend to remove all the real code in
zope.testing.testrunner at some point, leaving only backward-
compatibility imports in its place.  At this point, if you are still
using the one from zope.testing in your projects, I would say to submit
the patch against that:  we should be able to use 'patch -pN' to get it
merged, likely.

- --
Tres Seaver          +1 540-429-0999          tsea...@palladion.com
Palladion Software   "Excellence by Design"    http://palladion.com
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org


Zope-Dev maillist  -  Zope-Dev@zope.org
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope )

Reply via email to