This is the summary for test reports received on the zope-tests list between 2014-01-05 00:00:00 UTC and 2014-01-06 00:00:00 UTC: See the footnotes for test reports of unsuccessful builds. An up-to date view of the builders is also available in our buildbot documentation: http://docs.zope.org/zopetoolkit/process/buildbots.html#the-nightly-builds Reports received ---------------- Successful - zopetoolkit_trunk - Build # 506 winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 [1] winbot / zope.security_py_265_32 winbot / ztk_10 py_254_win32 winbot / ztk_10 py_265_win32 winbot / ztk_10 py_265_win64 winbot / ztk_11 py_254_win32 winbot / ztk_11 py_265_win32 winbot / ztk_11 py_265_win64 winbot / ztk_11 py_270_win32 winbot / ztk_11 py_270_win64 Non-OK results -------------- [1] FAILED winbot / zope.security_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-January/080355.html
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 01/06/2014 07:00 PM, Zope tests summarizer wrote:
[1] FAILED winbot / zope.security_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-January/080355.html
Beautiful! Who knows what the real failure is, but theerror message shows case sensitivity for hexits. And on my machine, the tests fail differently, because '_tkinter' is not importable. Aaaargh! Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlLLSegACgkQ+gerLs4ltQ5GjACfZPjz625NwnlvF0htU2KAIHEW c9IAoMFfAhSJdzWw4EX0kIgcpPdtxXbP =1glA -----END PGP SIGNATURE-----
On Mon, Jan 06, 2014 at 07:27:34PM -0500, Tres Seaver wrote:
On 01/06/2014 07:00 PM, Zope tests summarizer wrote:
[1] FAILED winbot / zope.security_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-January/080355.html
Beautiful! Who knows what the real failure is, but theerror message shows case sensitivity for hexits. And on my machine, the tests fail differently, because '_tkinter' is not importable. Aaaargh!
Not just _tkinter. I especially love the tox failures due to ImportError: No module named _winreg on my Linux laptop. OTOH tox -e coverage passes. And Travis CI is happy: https://travis-ci.org/zopefoundation/zope.security (And last commit to the code base was 6 months ago, so this is clearly a non-deterministic something.) Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development
On Tue, Jan 07, 2014 at 02:26:04PM +0200, Marius Gedminas wrote:
On Mon, Jan 06, 2014 at 07:27:34PM -0500, Tres Seaver wrote:
On 01/06/2014 07:00 PM, Zope tests summarizer wrote:
[1] FAILED winbot / zope.security_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-January/080355.html
Beautiful! Who knows what the real failure is, but theerror message shows case sensitivity for hexits. And on my machine, the tests fail differently, because '_tkinter' is not importable. Aaaargh!
Not just _tkinter. I especially love the tox failures due to
ImportError: No module named _winreg
on my Linux laptop.
Solved it: https://github.com/zopefoundation/zope.security/commit/dceaae23490a5cb2c3052... Now I just can't reproduce the hex address difference. Something to do with Windows? Platform-specific %p formatting? Why did it only start showing up now? Semi-deterministic memory addresses that just happened to never contain any hex digits above 0x9 until now? Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 01/08/2014 09:16 AM, Marius Gedminas wrote:
On Tue, Jan 07, 2014 at 02:26:04PM +0200, Marius Gedminas wrote:
On Mon, Jan 06, 2014 at 07:27:34PM -0500, Tres Seaver wrote:
On 01/06/2014 07:00 PM, Zope tests summarizer wrote:
[1] FAILED winbot / zope.security_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-January/080355.html
Beautiful! Who knows what the real failure is, but theerror message shows case sensitivity for hexits. And on my machine, the tests fail differently, because '_tkinter' is not importable. Aaaargh!
Not just _tkinter. I especially love the tox failures due to
ImportError: No module named _winreg
on my Linux laptop.
Solved it: https://github.com/zopefoundation/zope.security/commit/dceaae23490a5cb2c3052...
Good
on you for fixing it, but holy crap, that is insane!
Now I just can't reproduce the hex address difference. Something to do with Windows? Platform-specific %p formatting?
Why did it only start showing up now? Semi-deterministic memory addresses that just happened to never contain any hex digits above 0x9 until now?
Hellifiknow. I see zero value to spelling that comparison that way, anyhow. Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlLNna8ACgkQ+gerLs4ltQ73aQCdG3t5uxliuoTYnSaitGMWF0Ub 9h8AoKXn9vVOTB1lj2KWXbLV+kYFAIKs =8eJ9 -----END PGP SIGNATURE-----
On Wed, Jan 08, 2014 at 01:49:19PM -0500, Tres Seaver wrote:
On 01/08/2014 09:16 AM, Marius Gedminas wrote:
On Tue, Jan 07, 2014 at 02:26:04PM +0200, Marius Gedminas wrote:
On Mon, Jan 06, 2014 at 07:27:34PM -0500, Tres Seaver wrote:
On 01/06/2014 07:00 PM, Zope tests summarizer wrote:
[1] FAILED winbot / zope.security_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-January/080355.html
Beautiful! Who knows what the real failure is, but theerror message shows case sensitivity for hexits. And on my machine, the tests fail differently, because '_tkinter' is not importable. Aaaargh!
Not just _tkinter. I especially love the tox failures due to
ImportError: No module named _winreg
on my Linux laptop.
Solved it: https://github.com/zopefoundation/zope.security/commit/dceaae23490a5cb2c3052...
Good
on you for fixing it, but holy crap, that is insane!
Now I just can't reproduce the hex address difference. Something to do with Windows? Platform-specific %p formatting?
Why did it only start showing up now? Semi-deterministic memory addresses that just happened to never contain any hex digits above 0x9 until now?
Hellifiknow. I see zero value to spelling that comparison that way, anyhow.
Fun fact: it *is* platform-specific %p formatting, and it came into my mind because *I'd already figured out and fixed it (incompletely) once before*: https://github.com/zopefoundation/zope.security/commit/e1d5f7cf375ccdfb8f620... So https://github.com/zopefoundation/zope.security/commit/45e8a8563dcbc82c615fb... fixes the problem for now, and I'll be very happy if anyone can come up with a saner unit test, but I don't want to even think about this any more right now. Except, I just remembered one thing: I was a Very Bad Person and duplicated[*] the _fmt_address() function in proxy.py and in test_proxy.py. And now I changed only one of them. [*] don't remember why, maybe I thought that the pure-Python module couldn't always be imported due to name clashes with the C module? *sigh* BRB, fixing. (While tired and hungry at the end of a long day, best time for such fixes, to ensure more fixes will be necessary in the future.) Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development
participants (3)
-
Marius Gedminas -
Tres Seaver -
Zope tests summarizer