Hello, On Thu, 17 Feb 2011 10:58:35 -0500 you wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 02/17/2011 06:58 AM, Zope Tests Summarizer wrote: > >> Subject: FAILED : Zope Buildbot / zopetoolkit-1.1_win-py2.5 slave-win >> From: jdriessen at thehealthagency.com >> Date: Wed Feb 16 15:03:12 EST 2011 >> URL: http://mail.zope.org/pipermail/zope-tests/2011-February/032218.html >> >> Subject: FAILED : Zope Buildbot / zopetoolkit_win-py2.5 slave-win >> From: jdriessen at thehealthagency.com >> Date: Wed Feb 16 15:18:08 EST 2011 >> URL: http://mail.zope.org/pipermail/zope-tests/2011-February/032223.html >> >> Subject: FAILED : Zope Buildbot / zopetoolkit_win-py2.6 slave-win >> From: jdriessen at thehealthagency.com >> Date: Wed Feb 16 15:25:31 EST 2011 >> URL: http://mail.zope.org/pipermail/zope-tests/2011-February/032226.html > > These three failures are due to a quirk in how datetime.datetime repr > works: if the 'microseconds' field happens to be zero, it isn't > printed, e.g.: > > Expected: > datetime.datetime(<DATETIME>, tzinfo=<UTC>) > Got: > datetime.datetime(2011, 2, 16, 20, 0, 43, tzinfo=<UTC>) > > The regex (in zope.dublincore.tests.test_timeannotators), expects the > microseconds value to be present: > > datetime_re = ( > '[0-9]{4}, [0-9]{1,2}, [0-9]{1,2}, [0-9]{1,2}, [0-9]{1,2}, \ > [0-9]{1,2}, ' > '[0-9]{1,6}') > > > I have no idea why that value is suddenly exactly zero for the THA box.
Windowze... We also have such a failure 1 in 50 buildbot runs. Tho very misterious how it could happen 3x in a row. -- Best regards, Adam GROSZER -- Quote of the day: Faith on a full stomach may be simply contentment- but if you have it when you're hungry, it's genuine. - Frank A. Clark _______________________________________________ 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 )