[Zope-dev] Zope Tests: 4 OK, 1 Unknown
Summary of messages to the zope-tests list. Period Fri Aug 15 11:00:00 2008 UTC to Sat Aug 16 11:00:00 2008 UTC. There were 5 messages: 5 from Zope Tests. Unknown --- Subject: UNKNOWN : Zope-2.8 Python-2.3.6 : Linux From: Zope Tests Date: Fri Aug 15 20:40:07 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-August/010015.html Tests passed OK --- Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Tests Date: Fri Aug 15 20:41:37 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-August/010016.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Tests Date: Fri Aug 15 20:43:07 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-August/010017.html Subject: OK : Zope-2.11 Python-2.4.4 : Linux From: Zope Tests Date: Fri Aug 15 20:44:37 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-August/010018.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Tests Date: Fri Aug 15 20:46:08 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-August/010019.html ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Tests: 4 OK, 1 Unknown
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Zope Tests Summarizer wrote: Summary of messages to the zope-tests list. Period Fri Aug 15 11:00:00 2008 UTC to Sat Aug 16 11:00:00 2008 UTC. There were 5 messages: 5 from Zope Tests. Unknown --- Subject: UNKNOWN : Zope-2.8 Python-2.3.6 : Linux From: Zope Tests Date: Fri Aug 15 20:40:07 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-August/010015.html I can't reproduce this failure on my box (self-compiled Python 2.3.5, Ubuntu). Does anyone have a clue why the 'encodings.aliases' module would be different? Tres. - -- === Tres Seaver +1 540-429-0999 [EMAIL PROTECTED] Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIpuoO+gerLs4ltQ4RAiOoAJ9x0BeDmvfR+QbnQ7omDJcKZTEKpgCdG3YD Y+afeOahqXiHoepAa6C6298= =fqC2 -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Tests: 4 OK, 1 Unknown
Tres Seaver wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Zope Tests Summarizer wrote: Summary of messages to the zope-tests list. Period Fri Aug 15 11:00:00 2008 UTC to Sat Aug 16 11:00:00 2008 UTC. There were 5 messages: 5 from Zope Tests. Unknown --- Subject: UNKNOWN : Zope-2.8 Python-2.3.6 : Linux From: Zope Tests Date: Fri Aug 15 20:40:07 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-August/010015.html I can't reproduce this failure on my box (self-compiled Python 2.3.5, Ubuntu). Does anyone have a clue why the 'encodings.aliases' module would be different? I certainly don't, but apparently there was a bug report [1] which caused Andreas to fix it in Hotfix (see r89881), but not the Zope 2.8 branch. [1] https://bugs.edge.launchpad.net/zope2/+bug/258154 ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Tests: 4 OK, 1 Unknown
--On 16. August 2008 17:18:56 +0200 Philipp von Weitershausen [EMAIL PROTECTED] wrote: Tres Seaver wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Zope Tests Summarizer wrote: Summary of messages to the zope-tests list. Period Fri Aug 15 11:00:00 2008 UTC to Sat Aug 16 11:00:00 2008 UTC. There were 5 messages: 5 from Zope Tests. Unknown --- Subject: UNKNOWN : Zope-2.8 Python-2.3.6 : Linux From: Zope Tests Date: Fri Aug 15 20:40:07 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-August/010015.html I can't reproduce this failure on my box (self-compiled Python 2.3.5, Ubuntu). Does anyone have a clue why the 'encodings.aliases' module would be different? I certainly don't, but apparently there was a bug report [1] which caused Andreas to fix it in Hotfix (see r89881), but not the Zope 2.8 branch. hmm? The 2.8 branch contains the original code of the Hotfix + Tres' fix for the _aliases problem. I also can not reproduce this failure with Python 2.3 + Zope 2.8. The fix for https://bugs.edge.launchpad.net/zope2/+bug/258154 was to include Tres' fix for Python 2.3 with the hotfix - but only for Python 2.3 interpreters (based on sys.version_info). Andreas pgp4vO6zzYfea.pgp Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.testrunner test failures, remaining ones not windows specific ; -)
Marius Gedminas wrote: On Tue, Aug 12, 2008 at 09:17:39PM +0100, Chris Withers wrote: I could have sworn I reported this before but couldn't find anything in the archives so apologies if I have posted this before... I have a feeling of deja vu about this... Indeed ;-) File zope.testing\src\zope\testing\testrunner\testrunner-debugging- layer-setup.test, line 45, in testrunner-debugging-layer-setup.test ... File zope.testing\src\zope\testing\testrunner\find.py, line 103, in find_suites suite = StartUpFailure( Let's look at this statement closer: Wrong statement ;-) The offending chunk was further down in the file, and the reasons for the failure are manyfold :-( 1. StartUpFailure there gets called with the exception traceback explicitly set to None. That means if you enable postmortem debugging and a StartUpFailure gets created without full exc_info, you get the AttributeError on tb_next. I've added a doctest and code to StartUpFailure to raise a more explicit error in this case. 2. It appears the traceback is explicitly filtered out of exc_info in the second place StartUpFailures are instantiated purely to make the output a bit nicer. What would people feel about providing the traceback here to enable postmortem debugging to work properly? I've started adding test cases for this to testrunner-edge-cases.txt but want to know what to do before finishing them off :-S 3. testrunner-debugging-layer-setup.test appears to be running the testrunner with insuffient parameters to only find the tests it has set up. In my case, it's for some reason trying to find tests within eggs in my base python installation (yay! for setuptools for breaking my base setup, but that's another issue entirely ;-)) What parameters do we need to change in that test to make it work as intended? The module where find_suites is failing to find a test_suite function in question is: module 'tests' from 'Python24/lib/site-packages/mailinglogger-3.1.0-py2.4.egg/tests/__init__.pyc' 4. I don't understand why find_suites would be unhappy to not find a test_suite method in a __init__.py. 'tests' is a package in mailinglogger. That said, looking at that 'egg', it looks pretty broken so the tests package is probably ending up actually being on sys.path. Still, why would find_tests try and find tests in it? Unfortunately, when Christian did his refactoring he did so without doing an svn-cp-then-edit, so I don't even know who wrote the offending code :-S File zope.testing\src\zope\testing\testrunner\find.py, line 36, in __init__ post_mortem(exc_info) File zope.testing\src\zope\testing\testrunner\runner.py, lin e 717, in post_mortem pdb.post_mortem(exc_info[2]) File Python24\lib\pdb.py, line 1016, in post_mortem while t.tb_next is not None: Apparently the traceback was exactly two frames deep, and with those stripped, the code passed None to pdb.post_mortem(). Yes, although I'll note that the code has changed since I ran these, as Michael Howitz added a test for StartUpFailure at my request. I'd also suggest extracting the stack frame stripping into a function that would be a bit more defensive: def strip_tb_frames((exc_type, exc_value, tb), count): while tb.tb_next is not None and count 0: tb = tb.tb_next count -= 1 return (exc_type, exc_value, tb) and call it like this suite = StartUpFailure( options, module_name, strip_tb_frames(sys.exc_info(), 2) ) I have a sneaking suspiction the stripping of two levels is purely to remove the frames that are actually inside find.py. If this is the case, a comment would likely suffice as to why it's there... (Why oh why does Guido want to take away my beloved implicit argument tuple unpacking in Python 3.0?) AttributeError: 'NoneType' object has no attribute 'tb_next' Next error: TestIgnore moved from zope.testing.testrunner to zope.testing.testrunner.coverage. It should be simple to fix the test. Well, correcting the import revealed some other massaging that needed to be done but this is now fixed :-) *multi-sigh* Chris -- Simplistix - Content Management, Zope Python Consulting - http://www.simplistix.co.uk ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
