Re: [Zope-dev] KGS buildbot news (zope.server failure almost explained)
On Aug 15, 2008, at 02:35 , Christophe Combelles wrote: We should also probably consider waiting a bit more for the new site (new.zope.org) to come up, but I don't know when it will be finished. It only needs some content for zope2, grok, and some other pages. I don't see the connection here. The site has nothing to do with these specific issues. jens ___ 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] KGS buildbot news (zope.server failure almost explained)
Jens Vagelpohl a écrit : On Aug 15, 2008, at 02:35 , Christophe Combelles wrote: We should also probably consider waiting a bit more for the new site (new.zope.org) to come up, but I don't know when it will be finished. It only needs some content for zope2, grok, and some other pages. I don't see the connection here. The site has nothing to do with these specific issues. What I mean, is that releasing zope 3.4 along with a new web site is much much better than releasing it alone. jens ___ 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 ) ___ 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 )
[Zope-dev] Zope Tests: 4 OK, 1 Unknown
Summary of messages to the zope-tests list. Period Thu Aug 14 11:00:00 2008 UTC to Fri Aug 15 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: Thu Aug 14 20:39:01 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-August/010010.html Tests passed OK --- Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Tests Date: Thu Aug 14 20:40:32 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-August/010011.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Tests Date: Thu Aug 14 20:42:02 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-August/010012.html Subject: OK : Zope-2.11 Python-2.4.4 : Linux From: Zope Tests Date: Thu Aug 14 20:43:32 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-August/010013.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Tests Date: Thu Aug 14 20:45:02 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-August/010014.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.app.authentication 3.4.3 + download.zope.org/simple == broken
On Thu, 2008-08-14 at 16:00 -0400, Gary Poster wrote: If you use the http://download.zope.org/ppix or http://download.zope.org/simple indexes and try to get zope.app.authentication 3.4.3 (the newest), you will get a 404 error. Looking at PyPI and the zope.org index, it is evident why. http://pypi.python.org/pypi/zope.app.authentication/3.4.3 only lists one release, the source release http://download.zope.org/simple/zope.app.authentication/ lists 3.4.3 eggs as well. I strongly suspect that someone uploaded the zope.app.authentication eggs to PyPI; the zope.org index saw them and recorded them; and then someone removed the eggs from PyPI. The same happened for a lot of files from zope.security. :( The simple index has 3.4.1 as a zip and a tarball, but pypi only has the tarball left. -- Christian Theune · [EMAIL PROTECTED] gocept gmbh co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 7 · fax +49 345 1229889 1 Zope and Plone consulting and development signature.asc Description: This is a digitally signed message part ___ 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.app.authentication 3.4.3 + download.zope.org/simple == broken
On Thu, Aug 14, 2008 at 04:00:22PM -0400, Gary Poster wrote: If you use the http://download.zope.org/ppix or http://download.zope.org/simple indexes and try to get zope.app.authentication 3.4.3 (the newest), you will get a 404 error. Looking at PyPI and the zope.org index, it is evident why. http://pypi.python.org/pypi/zope.app.authentication/3.4.3 only lists one release, the source release http://download.zope.org/simple/zope.app.authentication/ lists 3.4.3 eggs as well. I strongly suspect that someone uploaded the zope.app.authentication eggs to PyPI; the zope.org index saw them and recorded them; and then someone removed the eggs from PyPI. My fault. The eggs in question were (a) broken (doctests with inconsistent line endings causing test module import failures) and (b) unnecessrary (the eggs had no extension modules inside). I asked on IRC whether removing binary eggs from PyPI would be bad, given that there's a source distribution for the same version, and nobody brought up zope.org's index. It would be great if someone could re-upload the eggs to PyPI. More importantly, this is a reminder to please not remove eggs. The behavior or download.zope.org/simple is reasonable. Removing eggs isn't. :-) Well, now I know. Previously I thought only removing whole released versions from PyPI was bad. Marius Gedminas -- It is easier to optimize correct code than to correct optimized code. -- Bill Harlan signature.asc Description: Digital 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 on windows
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... Anyway, running zope.testrunner's trunk's tests on windows seems to have some problems. These don't occur when running them on Linux. I'm vaguely interested in fixing these, but I don't do Windows. 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: try: module = import_name(module_name) except KeyboardInterrupt: raise except: -- suite = StartUpFailure( options, module_name, sys.exc_info()[:2] + (sys.exc_info()[2].tb_next.tb_next,), ) It would appear that the traceback is shallower than the code expects. I don't know why it is trying to strip the first two frames of the stack, either. 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(). It would be good if someone who has Windows and Linux could compare the tracebacks in question. 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) ) (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: Failure in test zope.testing\src\zope\testing\testrunner\testrunner- coverage-win32.txt Failed doctest test for testrunner-coverage-win32.txt File zope.testing\src\zope\testing\testrunner\testrunner-coverage -win32.txt, line 0 The name of this test suggests it's only run under Win32, so any refactoring done on Linux is likely to break it without anyone noticing. -- File zope.testing\src\zope\testing\testrunner\testrunner-coverage-w in32.txt, line 14, in testrunner-coverage-win32.txt Failed example: ignore = testrunner.TestIgnore(WinOptions()) Exception raised: Traceback (most recent call last): File zope.testing\src\zope\testing\doctest.py, line 1356, in __run compileflags, 1) in test.globs File doctest testrunner-coverage-win32.txt[2], line 1, in ? AttributeError: 'module' object has no attribute 'TestIgnore' TestIgnore moved from zope.testing.testrunner to zope.testing.testrunner.coverage. It should be simple to fix the test. Ran 183 tests with 2 failures and 0 errors in 43.094 seconds. Tearing down left over layers: Tear down zope.testing.testrunner.layer.UnitTests in 0.000 seconds. Marius Gedminas -- An NT server can be run by an idiot, and usually is. signature.asc Description: Digital 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 )
