Re: [Zope-dev] zope-tests - FAILED: 8, OK: 8
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/11/2013 09:00 PM, Zope tests summarizer wrote:
[1]FAILED Still Failing - zopetoolkit_trunk - Build # 264
https://mail.zope.org/pipermail/zope-tests/2013-May/074326.html
I fixed an unpinned version for a new downstream dependency today. I
think that will get us back to failing due to persistent / BTrees
mismatches. :(
[2]FAILED winbot / ZEO_py_265_32
https://mail.zope.org/pipermail/zope-tests/2013-May/074325.html
These tests are so slow and hard to work with that I lose patience with
them. It looks like the ZEO tests are re-using some ZODB doctests, but
without benefit of the renormalizers / checkers ZODB uses. I will look
at exposing those items in ZODB, and have the ZEO tests reuse them.
[3]FAILED winbot / ZODB_dev py_265_win32
https://mail.zope.org/pipermail/zope-tests/2013-May/074335.html
[4]FAILED winbot / ZODB_dev py_265_win64
https://mail.zope.org/pipermail/zope-tests/2013-May/074336.html
[5]FAILED winbot / ZODB_dev py_270_win32
https://mail.zope.org/pipermail/zope-tests/2013-May/074337.html
[6]FAILED winbot / ZODB_dev py_270_win64
https://mail.zope.org/pipermail/zope-tests/2013-May/074338.html
I whacked another couple of Windows-only moles this weekend
('ZODB.utils.u64' returning a 'long', some file-not-closed bugs I
introduced while trying to remove 'tempfile.mktemp'). I think I need
keys to the winbot, or at least the ability to kick off a test run
proactively.
[7]FAILED winbot / zope.app.content_py_265_32
https://mail.zope.org/pipermail/zope-tests/2013-May/074339.html
[8]FAILED winbot / zope.interface_py_265_32
https://mail.zope.org/pipermail/zope-tests/2013-May/074340.html
Github was offline.
Tres.
- --
===
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software Excellence by Designhttp://palladion.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/
iEYEARECAAYFAlGO8LkACgkQ+gerLs4ltQ70RQCfap+HV93JBbFNNGy3M44NFZws
PXoAoNNTSrd+KhMzSo+p61Wnw7ozkrC1
=Oc7Q
-END PGP SIGNATURE-
___
Zope-Dev maillist - Zope-Dev@zope.org
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 )
Re: [Zope-dev] zope-tests - FAILED: 8, OK: 8
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/03/2013 09:00 PM, Zope tests summarizer wrote: [1]FAILED Still Failing - zopetoolkit_trunk - Build # 222 https://mail.zope.org/pipermail/zope-tests/2013-April/073673.html Ugh. I think Marius had some clue to this one, but I'm baffled. [2]FAILED winbot / ZODB_dev py_265_win32 https://mail.zope.org/pipermail/zope-tests/2013-April/073684.html [3]FAILED winbot / ZODB_dev py_265_win64 https://mail.zope.org/pipermail/zope-tests/2013-April/073685.html [4]FAILED winbot / ZODB_dev py_270_win32 https://mail.zope.org/pipermail/zope-tests/2013-April/073686.html [5]FAILED winbot / ZODB_dev py_270_win64 https://mail.zope.org/pipermail/zope-tests/2013-April/073687.html Looks like more renormalizer fun. [8]FAILED winbot / zope.security_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-April/073675.html Network failure during 'git pull'. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlFdvFgACgkQ+gerLs4ltQ50KACeI7zMeX6JqKFBVjhfzH+r9l0b piMAoNVY+Mf+dAF1HvVDAHhvqRxISaj7 =O1Bu -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org 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 )
Re: [Zope-dev] zope-tests - FAILED: 8, OK: 8
On Thu, Apr 04, 2013 at 01:46:00PM -0400, Tres Seaver wrote: On 04/03/2013 09:00 PM, Zope tests summarizer wrote: [1]FAILED Still Failing - zopetoolkit_trunk - Build # 222 https://mail.zope.org/pipermail/zope-tests/2013-April/073673.html Ugh. I think Marius had some clue to this one, but I'm baffled. I suspected https://bugs.launchpad.net/zc.buildout/+bug/257555 IIRC BTrees setup_requires=['persistent'] in setup.py. When mr.developer instructs buildout to develop BTrees, setuptools end up downloading persistent-*.egg in the source directory, outside buildout's jurisdiction, and then, somehow, buildout assumes that persistent is installed system-wide and doesn't add the persistent egg to the sys.path of the generated bin/test-ztk-whatever script. That's just a guess, I haven't spent any appreciable time debugging this. [2]FAILED winbot / ZODB_dev py_265_win32 https://mail.zope.org/pipermail/zope-tests/2013-April/073684.html [3]FAILED winbot / ZODB_dev py_265_win64 https://mail.zope.org/pipermail/zope-tests/2013-April/073685.html [4]FAILED winbot / ZODB_dev py_270_win32 https://mail.zope.org/pipermail/zope-tests/2013-April/073686.html [5]FAILED winbot / ZODB_dev py_270_win64 https://mail.zope.org/pipermail/zope-tests/2013-April/073687.html Looks like more renormalizer fun. Yes. I think I got it this time. But I thought so the previous two times too. ;-) [8]FAILED winbot / zope.security_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-April/073675.html Network failure during 'git pull'. Last zope.security build was successful. Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development signature.asc Description: Digital signature ___ Zope-Dev maillist - Zope-Dev@zope.org 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 )
