Re: [Zope-dev] Zope Tests: 72 OK, 15 Failed
On 18 February 2011 00:55, Simon Elbaz elbazsim...@gmail.com wrote:
Hi,
I have tried this code on Python 2.7.1 (r271:86832, Nov 27 2010, 18:30:46)
[MSC v.1500 32 bit (Intel)] on win32. It seems that it is possible to have
no milliseconds returned by datetime.now.
while 1:
... datetime.now(pytz.utc)
datetime.datetime(2011, 2, 17, 23, 48, 17, 984000, tzinfo=UTC)
datetime.datetime(2011, 2, 17, 23, 48, 17, 984000, tzinfo=UTC)
datetime.datetime(2011, 2, 17, 23, 48, 18, tzinfo=UTC)
datetime.datetime(2011, 2, 17, 23, 48, 18, tzinfo=UTC)
datetime.datetime(2011, 2, 17, 23, 48, 18, tzinfo=UTC)
...
datetime.datetime(2011, 2, 17, 23, 48, 18, tzinfo=UTC)
datetime.datetime(2011, 2, 17, 23, 48, 18, tzinfo=UTC)
...
datetime.datetime(2011, 2, 17, 23, 48, 18, 15000, tzinfo=UTC)
datetime.datetime(2011, 2, 17, 23, 48, 18, 15000, tzinfo=UTC)
datetime.datetime(2011, 2, 17, 23, 48, 18, 15000, tzinfo=UTC)
datetime.datetime(2011, 2, 17, 23, 48, 18, 125000, tzinfo=UTC)
Traceback (most recent call last):
File stdin, line 2, in module
File
C:\Python27\lib\site-packages\pytz-2011b-py2.7.egg\pytz\__init__.py, li
ne 186, in utcoffset
KeyboardInterrupt
Simon
On Thu, Feb 17, 2011 at 4:58 PM, Tres Seaver tsea...@palladion.com 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.
Tres.
Simon,
Thank you for looking into this. I am kind of happy that the error can
be reproduced on a different windows machine.
Tres,
It is indeed 'special' that this error occurs only now. The windows
builds for zope.dublincore trunk have not shown this error:
http://dev.thehealthagency.com/buildbot/builders/zope.dublincore_3%20slave-win
http://dev.thehealthagency.com/buildbot/builders/zope.dublincore_5%20slave-win
http://dev.thehealthagency.com/buildbot/builders/zope.dublincore_trunk%20slave-win
How to proceed? Make the regex in
zope.dublincore.tests.test_timeannotators less strict?
I am not a pypi owner of zope.dublincore, so Tres, could you do the honors?
Jan-Jaap
___
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: 72 OK, 15 Failed
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 )
Re: [Zope-dev] Zope Tests: 72 OK, 15 Failed
On Fri, Feb 18, 2011 at 10:39, Adam GROSZER agroszer...@gmail.com wrote: Windowze... We also have such a failure 1 in 50 buildbot runs. Tho very misterious how it could happen 3x in a row. If the failure is random, with a chance of 1 in 50, 3 times in a row is no mystery. It shows the failure is truly random! :-) -- Martijn Pieters ___ 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 )
[Zope-dev] Zope Tests: 84 OK, 14 Failed, 1 Unknown
Summary of messages to the zope-tests list. Period Thu Feb 17 12:00:00 2011 UTC to Fri Feb 18 12:00:00 2011 UTC. There were 99 messages: 8 from Zope Tests, 4 from buildbot at pov.lt, 31 from buildbot at winbot.zope.org, 11 from ccomb at free.fr, 45 from jdriessen at thehealthagency.com. Test failures - Subject: FAILED : Zope Buildbot / zope2.13_win-py2.7 slave-win From: jdriessen at thehealthagency.com Date: Thu Feb 17 15:30:30 EST 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-February/032320.html Subject: FAILED : winbot / ztk_10 py_244_win32 From: buildbot at winbot.zope.org Date: Thu Feb 17 16:04:12 EST 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-February/032326.html Subject: FAILED : winbot / z3c.form_py_265_32 From: buildbot at winbot.zope.org Date: Thu Feb 17 23:23:04 EST 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-February/032370.html Subject: FAILED : winbot / z3c.rml_py_265_32 From: buildbot at winbot.zope.org Date: Thu Feb 17 23:48:22 EST 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-February/032371.html Subject: FAILED : winbot / z3c.template_py_265_32 From: buildbot at winbot.zope.org Date: Thu Feb 17 23:57:06 EST 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-February/032372.html Subject: FAILED : winbot / z3c.layer.ready2go_py_265_32 From: buildbot at winbot.zope.org Date: Fri Feb 18 00:02:34 EST 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-February/032373.html Subject: FAILED : winbot / z3c.formui_py_265_32 From: buildbot at winbot.zope.org Date: Fri Feb 18 00:03:54 EST 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-February/032374.html Subject: FAILED : winbot / z3c.tabular_py_265_32 From: buildbot at winbot.zope.org Date: Fri Feb 18 00:06:05 EST 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-February/032375.html Subject: FAILED : winbot / z3c.contents_py_265_32 From: buildbot at winbot.zope.org Date: Fri Feb 18 00:07:02 EST 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-February/032376.html Subject: FAILED : winbot / z3c.ptcompat_py_265_32 From: buildbot at winbot.zope.org Date: Fri Feb 18 01:25:02 EST 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-February/032387.html Subject: FAILED : winbot / z3c.pdftemplate_py_265_32 From: buildbot at winbot.zope.org Date: Fri Feb 18 01:29:17 EST 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-February/032388.html Subject: FAILED : winbot / z3c.coverage_py_265_32 From: buildbot at winbot.zope.org Date: Fri Feb 18 01:30:47 EST 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-February/032389.html Subject: FAILED : winbot / z3c.macro_py_265_32 From: buildbot at winbot.zope.org Date: Fri Feb 18 01:31:33 EST 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-February/032390.html Subject: FAILED : winbot / z3c.pagelet_py_265_32 From: buildbot at winbot.zope.org Date: Fri Feb 18 01:36:30 EST 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-February/032391.html Unknown --- Subject: UNKNOWN : Zope Buildbot / zope2.14-py2.6 slave-ubuntu32 From: jdriessen at thehealthagency.com Date: Thu Feb 17 18:15:56 EST 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-February/032343.html Tests passed OK --- Subject: OK : Zope Buildbot / zope2.12-py2.6 slave-osx From: jdriessen at thehealthagency.com Date: Thu Feb 17 12:56:46 EST 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-February/032293.html Subject: OK : Zope Buildbot / zope2.13-py2.6 slave-osx From: jdriessen at thehealthagency.com Date: Thu Feb 17 12:59:17 EST 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-February/032294.html Subject: OK : Zope Buildbot / zope2.13-py2.7 slave-osx From: jdriessen at thehealthagency.com Date: Thu Feb 17 13:01:41 EST 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-February/032295.html Subject: OK : Zope Buildbot / zope2.14-py2.6 slave-osx From: jdriessen at thehealthagency.com Date: Thu Feb 17 13:04:14 EST 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-February/032296.html Subject: OK : Zope Buildbot / zope2.14-py2.7 slave-osx From: jdriessen at thehealthagency.com Date: Thu Feb 17 13:06:39 EST 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-February/032297.html Subject: OK : Zope Buildbot / zopetoolkit-1.0-py2.4 slave-osx From: jdriessen at thehealthagency.com Date: Thu Feb 17 13:22:01 EST 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-February/032298.html Subject: OK : Zope Buildbot / zope2.12-py2.6 slave-ubuntu64 From: jdriessen at thehealthagency.com Date: Thu Feb 17 13:37:07 EST 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-February/032299.html Subject: OK : Zope Buildbot / zopetoolkit-1.0-py2.5 slave-osx From: jdriessen at thehealthagency.com Date: Thu Feb 17 13:37:21 EST 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-February/032300.html Subject: OK : Zope Buildbot / zope2.13-py2.6 slave-ubuntu64
Re: [Zope-dev] Zope Tests: 72 OK, 15 Failed
On Fri, Feb 18, 2011 at 09:21:12AM +0100, Jan-Jaap Driessen wrote: Thank you for looking into this. I am kind of happy that the error can be reproduced on a different windows machine. Tres, It is indeed 'special' that this error occurs only now. The windows builds for zope.dublincore trunk have not shown this error: http://dev.thehealthagency.com/buildbot/builders/zope.dublincore_3%20slave-win http://dev.thehealthagency.com/buildbot/builders/zope.dublincore_5%20slave-win http://dev.thehealthagency.com/buildbot/builders/zope.dublincore_trunk%20slave-win How to proceed? Make the regex in zope.dublincore.tests.test_timeannotators less strict? That sounds like the right solution to me. I am not a pypi owner of zope.dublincore, I am. Would you like to be too? 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 )
[Zope-dev] PAS, AuthEncoding and zope.password
I was looking into bcrypt[1] support for PAS I found z3c.bcrypt, which implements zope.password compontents (named utilities). PAS, however, uses Zope2's AccessControl.AuthEncoding module to handle password encryption / hashing schemes. Now, while AuthEncoding certainly supports extending the available schemes, it does need additional glue-code to be able to reuse zope.password components. Moreover, we now have two places to maintain the various hashing and encryption schemes. We should at the very least convert PAS to use zope.password instead of AccessControl.AuthEncoding. With that change it is then at least trivial to support bcrypt as well, you simply install the additional z3c.bcrypt egg and be done with it. But would it make sense to convert Zope2 itself as well? We could make the AuthEncodings module simply a proxy (with deprecation warnings if need be) for zope.password components. Any objections to reworking both AuthEncoding and PAS? -- Martijn Pieters [1] see http://codahale.com/how-to-safely-store-a-password/ and http://stackoverflow.com/questions/1561174/sha512-vs-blowfish-and-bcrypt ___ 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: 72 OK, 15 Failed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/18/2011 03:21 AM, Jan-Jaap Driessen wrote:
On 18 February 2011 00:55, Simon Elbaz elbazsim...@gmail.com wrote:
Hi,
I have tried this code on Python 2.7.1 (r271:86832, Nov 27 2010, 18:30:46)
[MSC v.1500 32 bit (Intel)] on win32. It seems that it is possible to have
no milliseconds returned by datetime.now.
while 1:
... datetime.now(pytz.utc)
datetime.datetime(2011, 2, 17, 23, 48, 17, 984000, tzinfo=UTC)
datetime.datetime(2011, 2, 17, 23, 48, 17, 984000, tzinfo=UTC)
datetime.datetime(2011, 2, 17, 23, 48, 18, tzinfo=UTC)
datetime.datetime(2011, 2, 17, 23, 48, 18, tzinfo=UTC)
datetime.datetime(2011, 2, 17, 23, 48, 18, tzinfo=UTC)
...
datetime.datetime(2011, 2, 17, 23, 48, 18, tzinfo=UTC)
datetime.datetime(2011, 2, 17, 23, 48, 18, tzinfo=UTC)
...
datetime.datetime(2011, 2, 17, 23, 48, 18, 15000, tzinfo=UTC)
datetime.datetime(2011, 2, 17, 23, 48, 18, 15000, tzinfo=UTC)
datetime.datetime(2011, 2, 17, 23, 48, 18, 15000, tzinfo=UTC)
datetime.datetime(2011, 2, 17, 23, 48, 18, 125000, tzinfo=UTC)
Traceback (most recent call last):
File stdin, line 2, in module
File
C:\Python27\lib\site-packages\pytz-2011b-py2.7.egg\pytz\__init__.py, li
ne 186, in utcoffset
KeyboardInterrupt
Simon
On Thu, Feb 17, 2011 at 4:58 PM, Tres Seaver tsea...@palladion.com 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.
Tres.
Simon,
Thank you for looking into this. I am kind of happy that the error can
be reproduced on a different windows machine.
Tres,
It is indeed 'special' that this error occurs only now. The windows
builds for zope.dublincore trunk have not shown this error:
http://dev.thehealthagency.com/buildbot/builders/zope.dublincore_3%20slave-win
http://dev.thehealthagency.com/buildbot/builders/zope.dublincore_5%20slave-win
http://dev.thehealthagency.com/buildbot/builders/zope.dublincore_trunk%20slave-win
How to proceed? Make the regex in
zope.dublincore.tests.test_timeannotators less strict?
I am not a pypi owner of zope.dublincore, so Tres, could you do the honors?
I made a stab at fixing the regex. If the dev checkouts start
passing, then we can do a release.
Tres.
- --
===
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software Excellence by Designhttp://palladion.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk1e6PsACgkQ+gerLs4ltQ4ovgCeKYvKv+DfKGtkBB4aTiaXbBe4
Ec0AoMDWuEXSZ9ZwzQJrQH5gMQtemC5n
=1xra
-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] PAS, AuthEncoding and zope.password
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/18/2011 04:19 PM, Martijn Pieters wrote: I was looking into bcrypt[1] support for PAS I found z3c.bcrypt, which implements zope.password compontents (named utilities). PAS, however, uses Zope2's AccessControl.AuthEncoding module to handle password encryption / hashing schemes. Now, while AuthEncoding certainly supports extending the available schemes, it does need additional glue-code to be able to reuse zope.password components. Moreover, we now have two places to maintain the various hashing and encryption schemes. We should at the very least convert PAS to use zope.password instead of AccessControl.AuthEncoding. With that change it is then at least trivial to support bcrypt as well, you simply install the additional z3c.bcrypt egg and be done with it. But would it make sense to convert Zope2 itself as well? We could make the AuthEncodings module simply a proxy (with deprecation warnings if need be) for zope.password components. Any objections to reworking both AuthEncoding and PAS? - -1 to any deprecation warnings; +0 otherwise. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk1e6TUACgkQ+gerLs4ltQ7M6ACgpYmHdAFTuTb8M+aoGQFuIzza waIAn2AHG4xx/0wAe2ZE2Q2izgXPFPrK =7sQ8 -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 )
