Re: Zope Tests: 70 OK, 10 Failed
Marius Gedminas <[email protected]>
| Newsgroups | gmane.comp.web.zope.devel |
|---|---|
| Message-ID | <20101023230613.GA9249@platonas> |
On Sun, Oct 24, 2010 at 12:15:29AM +0300, Marius Gedminas wrote: > On Sat, Oct 23, 2010 at 11:15:14PM +0300, Marius Gedminas wrote: > > > Subject: FAILED : winbot / ztk_10 py_244_win32 > > > From: buildbot at winbot.zope.org > > > Date: Fri Oct 22 17:05:07 EDT 2010 > > > URL: http://mail.zope.org/pipermail/zope-tests/2010-October/022057.html > > > > One zope.testing (3.9.5) failure on Windows. I can't shake the feeling > > that it's just a matter of backporting the right zope.testrunner fixes, > > but I don't see anything relevant in its svn logs. > > > > When I try to reproduce under wine, I get four failures instead of one. > > > > The failure in testrunner-layers.txt happens because the test runner > > skips the unit test layer altogether, when run with -j2. > > I think I got this. > > zope.testing 3.9.5 uses zope.testing.testrunner to run its own tests. I meant "uses zope.testrunner" here. > -j2 forces the tests to run in the subprocess. > > The subprocess executes bin\test-script.py, which is zope.testrunner, > and has a different name for the unit test name. > > Any ideas for a fix? Should we force zope.testing to use itself to test > itself? > > Why doesn't this happen on Linux? > > *checks* > > Oh. It does. Have we no buildbots testing ZTK 1.0 then? > > Confused, > Marius Gedminas > -- > http://pov.lt/ -- Zope 3/BlueBream consulting and development Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development _______________________________________________ Zope-Dev maillist - [email protected] https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
signature.asc
(application/pgp-signature, 198 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkzDamUACgkQkVdEXeem14+hWgCeOtI1OJZ0L90COHFzDDQidzkm BowAn1cN/JnABc+MdKUCr2EVkg0l84fC =Pjq9 -----END PGP SIGNATURE-----