Re: [Zope-dev] Hanno, please update the ZTK
On Sun, May 2, 2010 at 10:52 PM, Martijn Faassen wrote: > Hi there, > > Of course what applies to Hanno should apply to others making releases > of packages maintained by the Zope Toolkit project as well. I think the > ZTK leadership should figure out some kind of guidelines for this that > people can follow. Maybe someone can write a tool too to check up how > far a toolkit is out of sync with the latest releases. Just some ideas. For the tool, I think I did it already. I modified one of Hanno's script some times ago: cd zopetoolkit/trunk bin/buildout -c checknew.cfg bin/python checknew.py Vincent ___ 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] Hanno, please update the ZTK
Good evening :) If you have a specific issue with me, you might contact me in private. But with your follow-ups this turned into a more general issue. On Sun, May 2, 2010 at 10:59 PM, Martijn Faassen wrote: > Martijn Faassen wrote: >> Of course what applies to Hanno should apply to others making releases >> of packages maintained by the Zope Toolkit project as well. I think the >> ZTK leadership should figure out some kind of guidelines for this that >> people can follow. Maybe someone can write a tool too to check up how >> far a toolkit is out of sync with the latest releases. Just some ideas. > > Don't think you're off the hook with me though, Hanno. :) > > Hanno is special as he's maintaining a fork of the ZTK and was > maintaining the ZTK already in the past before he forked it. If I were > the ZTK leadership such a thing would probably frustrate me a lot, so > it's a good thing I'm not. Instead I can just express my displeasure out > loud. The "ZTK" is on my list of things to look into and I'm committed to the idea. Jan-Wijbrand, Christophe and me started an off-list discussion on the specifics of the "ZTK release team". I expect us to define the process around package releases and updating the ZTK. It's not entirely clear to me who should and who is allowed to update the ZTK definition. We'll figure things out and once we have I'll stick to the rules. Hanno ___ 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] Hanno, please update the ZTK
On Sun, May 2, 2010 at 22:52, Martijn Faassen wrote: > Of course what applies to Hanno should apply to others making releases > of packages maintained by the Zope Toolkit project as well. I think the > ZTK leadership should figure out some kind of guidelines for this that > people can follow. That would be great. This sounds like something to discuss on Tuesday. -- Lennart Regebro: Python, Zope, Plone, Grok http://regebro.wordpress.com/ +33 661 58 14 64 ___ 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.exceptiosn release has no relaese date
On Sun, May 2, 2010 at 22:34, Martijn Faassen wrote: > I saw a zope.exceptions release on pypi, but it has no release date is > marked in its change log: Meh! > http://docs.zope.org/zopetoolkit/process/releasing-software.html Oh, I follow the process, I just miss parts. :) I don't know how I didn't see that. I even used that showdocs command somebody made to render the docs to HTML (since I fudged the ReST syntax of zope.interface) and I didn't see it. > I highly recommend the use of zest.releaser to make releasing pretty > painless. I thought it was painless already, but maybe I was wrong. :) ___ 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] Test fixture failure zope.interface under Python 3.1
On Sun, May 2, 2010 at 22:35, Jens Vagelpohl wrote: > locale.getpreferredencoding() 'UTF-8' on Ubuntu. And I think Windows has something else as well, but then again Hanno was able to release Windows binaries. Strange that it didn't fail there. Tres got rid of some warnings when compiling as well, so it'll be a more polished release all around. :) -- Lennart Regebro: Python, Zope, Plone, Grok http://regebro.wordpress.com/ +33 661 58 14 64 ___ 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.exceptiosn release has no relaese date
Hi there, Two typos in the title, maybe I'm turning into Jim. :) Regards, Martijn ___ 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] Hanno, please update the ZTK
Hi there, Martijn Faassen wrote: > Of course what applies to Hanno should apply to others making releases > of packages maintained by the Zope Toolkit project as well. I think the > ZTK leadership should figure out some kind of guidelines for this that > people can follow. Maybe someone can write a tool too to check up how > far a toolkit is out of sync with the latest releases. Just some ideas. Don't think you're off the hook with me though, Hanno. :) Hanno is special as he's maintaining a fork of the ZTK and was maintaining the ZTK already in the past before he forked it. If I were the ZTK leadership such a thing would probably frustrate me a lot, so it's a good thing I'm not. Instead I can just express my displeasure out loud. Regards, Martijn ___ 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] Hanno, please update the ZTK
Hi there, Of course what applies to Hanno should apply to others making releases of packages maintained by the Zope Toolkit project as well. I think the ZTK leadership should figure out some kind of guidelines for this that people can follow. Maybe someone can write a tool too to check up how far a toolkit is out of sync with the latest releases. Just some ideas. Regards, Martijn ___ 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] Hanno, please update the ZTK
Hi there, Hanno, can you please update the zopetoolkit and do tests there as well when you make releases of packages maintained by the Zope Toolkit project? Because otherwise you're just wasting my time trying to sync things up again, and that's annoying. Not annoying me is one good reason, but there are other good reasons why you should be updating the ZTK but I'm sure the people in charge of the ZTK can express those. They haven't done so probably because they figured you already knew the reasons. Regards, Martijn ___ 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] Test fixture failure zope.interface under Python 3.1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 5/2/10 21:30 , Lennart Regebro wrote: > On Sun, May 2, 2010 at 18:37, Jens Vagelpohl wrote: >> The issue is a non-ASCII character in the Changelog: >> >> >> - - Added support for Python 3.1. Contributors: >> >>Lennart Regebro >>Martin v Löwis >>Thomas Lotze >>Wolfgang Schnerring >> >> >> Removing the "ö" I can run the tests and buildout. Question: Is this an >> issue with my particular sandbox? The Python 3.1 I use is a fresh build >> and I don't manipulate the default encoding anywhere. > > Hmm, I do not get that issue, but maybe the default encoding is > different on different systems? What are you using? This is on OS X 10.6.3 and sys.getdefaultencoding says UTF-8. It seems that the call opening the file ends up with a file handle that assumes the file contains ASCII: (Pdb) p open(os.path.join(os.path.dirname(__file__), *rnames)) <_io.TextIOWrapper name='CHANGES.txt' encoding='US-ASCII'> A little digging[1] tells me the determining factor for this assumed encoding is the return value of locale.getpreferredencoding, which for me is ASCII: >>> locale.getpreferredencoding() 'US-ASCII' What does your system say? jens [1] http://docs.python.org/py3k/library/functions.html#open -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkvd4foACgkQRAx5nvEhZLKmgACfR97RYPAk5bL8AHDUOrkZoZZO AFUAoIeXrs2DvQ4cusPOOYjFeTckujbS =m2pV -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 )
[Zope-dev] zope.exceptiosn release has no relaese date
Hi there, I saw a zope.exceptions release on pypi, but it has no release date is marked in its change log: http://pypi.python.org/pypi/zope.exceptions/3.6.0 I recommend following the procedure to avoid such issues: http://docs.zope.org/zopetoolkit/process/releasing-software.html I highly recommend the use of zest.releaser to make releasing pretty painless. Regards, Martijn ___ 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] Test fixture failure zope.interface under Python 3.1
On Sun, May 2, 2010 at 18:37, Jens Vagelpohl wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi all (and especially Lennart),
>
> I need a quick sanity check. Trying to test a package of mine for Python
> 3 compatibility I built Python 3.1.2 and installed distribute into it.
> My package depends on zope.interface. I am executing...
>
> $ python3.1 setup.py test
>
> It tries to install zope.interface, but fails with this traceback:
>
> Running zope.interface-3.6.0/setup.py -q bdist_egg --dist-dir
> /var/folders/ZD/ZDGPtbYeGkqB4K7rOkPK4U+++TI/-Tmp-/easy_install-8LJGXC/zope.interface-3.6.0/egg-dist-tmp-xVkH07
> Traceback (most recent call last):
> File "setup.py", line 58, in
>
> File
> "/usr/local/lib/python3.1/site-packages/distribute-0.6.10-py3.1.egg/setuptools/sandbox.py",
> line 33, in
> {'__file__':setup_script, '__name__':'__main__'})
> File "setup.py", line 80, in
>
> That's not very informative at all. Trying to debug this further I
> download zope.interface 3.6.0 and attempt to run its tests using
> "setup.py test", which gives a little more information:
>
> Traceback (most recent call last):
> File "setup.py", line 80, in
> + '\n' +
> File "setup.py", line 65, in read
> return open(os.path.join(os.path.dirname(__file__), *rnames)).read()
> File "/usr/local/lib/python3.1/encodings/ascii.py", line 26, in decode
> return codecs.ascii_decode(input, self.errors)[0]
> UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position
> 290: ordinal not in range(128)
>
> The issue is a non-ASCII character in the Changelog:
>
>
> - - Added support for Python 3.1. Contributors:
>
> Lennart Regebro
> Martin v Löwis
> Thomas Lotze
> Wolfgang Schnerring
>
>
> Removing the "ö" I can run the tests and buildout. Question: Is this an
> issue with my particular sandbox? The Python 3.1 I use is a fresh build
> and I don't manipulate the default encoding anywhere.
Hmm, I do not get that issue, but maybe the default encoding is
different on different systems? What are you using?
I'll change that to Loewis in any case, having non-ascii test like
that is definitely a no-no. You would think that after 30 years of
these kinds of problems I would have learnt, but apparently not. :)
--
Lennart Regebro: Python, Zope, Plone, Grok
http://regebro.wordpress.com/
+33 661 58 14 64
___
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: 10 OK, 6 Failed
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Christophe Combelles wrote: > Christophe Combelles a écrit : >> Tres Seaver a écrit : > Zope Tests Summarizer wrote: > > Subject: FAILED : ZTK 1.0dev / Python2.5.2 Linux 32bit > From: ccomb at free.fr > Date: Wed Apr 28 23:00:24 EDT 2010 > URL: http://mail.zope.org/pipermail/zope-tests/2010-April/014174.html > > Subject: FAILED : ZTK 1.0dev / Python2.6.4 Linux 32bit > From: ccomb at free.fr > Date: Wed Apr 28 23:00:25 EDT 2010 > URL: http://mail.zope.org/pipermail/zope-tests/2010-April/014173.html > > Subject: FAILED : ZTK 1.0dev / Python2.4.6 Linux 32bit > From: ccomb at free.fr > Date: Wed Apr 28 23:00:25 EDT 2010 > URL: http://mail.zope.org/pipermail/zope-tests/2010-April/014172.html > Christophe, > > These failures appear to be due to a merge conflict in your local ZTK > checkout. E.g., from [1]: > > > An internal error occured due to a bug in either zc.buildout or in a > recipe being used: > Traceback (most recent call last): > File > "/tmp/tmp_wjCee/zc.buildout-1.4.3-py2.6.egg/zc/buildout/buildout.py", > line 1659, in main > user_defaults, windows_restart, command) > File > "/tmp/tmp_wjCee/zc.buildout-1.4.3-py2.6.egg/zc/buildout/buildout.py", > line 182, in __init__ > data['buildout'].copy(), override)) > File > "/tmp/tmp_wjCee/zc.buildout-1.4.3-py2.6.egg/zc/buildout/buildout.py", > line 1333, in _open > eresult = _open(base, extends.pop(0), seen, dl_options, override) > File > "/tmp/tmp_wjCee/zc.buildout-1.4.3-py2.6.egg/zc/buildout/buildout.py", > line 1313, in _open > parser.readfp(fp) > File "/usr/local/Python2.6.4/lib/python2.6/ConfigParser.py", line 305, > in readfp > self._read(fp, filename) > File "/usr/local/Python2.6.4/lib/python2.6/ConfigParser.py", line 510, > in _read > raise e > ParsingError: File contains parsing errors: > /home/ccomb/slave3/Python2.6.4-Linux-32bit/build/ztk.cfg > [line 206]: '<<< .mine\n' > [line 278]: '===\n' > [line 350]: '>>> .r111557\n' > Seems like you had local, uncommitted changes there, which kind of hurts > our ability to reproduce failures elsewhere. >>> Ok there is something wrong, I'll clean eveything >>> >>> Before the buildout, I'm doing a >>> sed -i s/svn+ssh/svn/ ztk.cfg zopeapp.cfg >>> because the buildbot is not supposed to have a ssh key. >>> Then I'm doing a svn revert of these two files. >>> But if the buildout fails, the revert is not done. > >> I've recreated the slave, then reordered the commands. It should be better. > >> Yesterday there was a single failure on zope.app.container because of >> dublincore >> permissions. Today there are another one on the apidoc. I fixed those two today. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software "Excellence by Design"http://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkvdrAUACgkQ+gerLs4ltQ4CJgCgrVmKciw4UUOOd8ykGXEnvRus 4LoAoLwUuwqYAjsd1Yphg9jPtDOeu3Tq =CDjo -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 )
[Zope-dev] Test fixture failure zope.interface under Python 3.1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all (and especially Lennart),
I need a quick sanity check. Trying to test a package of mine for Python
3 compatibility I built Python 3.1.2 and installed distribute into it.
My package depends on zope.interface. I am executing...
$ python3.1 setup.py test
It tries to install zope.interface, but fails with this traceback:
Running zope.interface-3.6.0/setup.py -q bdist_egg --dist-dir
/var/folders/ZD/ZDGPtbYeGkqB4K7rOkPK4U+++TI/-Tmp-/easy_install-8LJGXC/zope.interface-3.6.0/egg-dist-tmp-xVkH07
Traceback (most recent call last):
File "setup.py", line 58, in
File
"/usr/local/lib/python3.1/site-packages/distribute-0.6.10-py3.1.egg/setuptools/sandbox.py",
line 33, in
{'__file__':setup_script, '__name__':'__main__'})
File "setup.py", line 80, in
That's not very informative at all. Trying to debug this further I
download zope.interface 3.6.0 and attempt to run its tests using
"setup.py test", which gives a little more information:
Traceback (most recent call last):
File "setup.py", line 80, in
+ '\n' +
File "setup.py", line 65, in read
return open(os.path.join(os.path.dirname(__file__), *rnames)).read()
File "/usr/local/lib/python3.1/encodings/ascii.py", line 26, in decode
return codecs.ascii_decode(input, self.errors)[0]
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position
290: ordinal not in range(128)
The issue is a non-ASCII character in the Changelog:
- - Added support for Python 3.1. Contributors:
Lennart Regebro
Martin v Löwis
Thomas Lotze
Wolfgang Schnerring
Removing the "ö" I can run the tests and buildout. Question: Is this an
issue with my particular sandbox? The Python 3.1 I use is a fresh build
and I don't manipulate the default encoding anywhere.
Thanks!
jens
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.8 (Darwin)
iEYEARECAAYFAkvdqjgACgkQRAx5nvEhZLJhpACgunVHthigpkiLO9K4JIskMEYC
MGUAn3ocaSIgdrMJG10szA+Ji/48OLO2
=Vfi3
-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] Zope Tests: 10 OK, 6 Failed
Christophe Combelles a écrit : > Tres Seaver a écrit : >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> Zope Tests Summarizer wrote: >> >>> Subject: FAILED : ZTK 1.0dev / Python2.5.2 Linux 32bit >>> From: ccomb at free.fr >>> Date: Wed Apr 28 23:00:24 EDT 2010 >>> URL: http://mail.zope.org/pipermail/zope-tests/2010-April/014174.html >>> >>> Subject: FAILED : ZTK 1.0dev / Python2.6.4 Linux 32bit >>> From: ccomb at free.fr >>> Date: Wed Apr 28 23:00:25 EDT 2010 >>> URL: http://mail.zope.org/pipermail/zope-tests/2010-April/014173.html >>> >>> Subject: FAILED : ZTK 1.0dev / Python2.4.6 Linux 32bit >>> From: ccomb at free.fr >>> Date: Wed Apr 28 23:00:25 EDT 2010 >>> URL: http://mail.zope.org/pipermail/zope-tests/2010-April/014172.html >> Christophe, >> >> These failures appear to be due to a merge conflict in your local ZTK >> checkout. E.g., from [1]: >> >> >>> An internal error occured due to a bug in either zc.buildout or in a >>> recipe being used: >>> Traceback (most recent call last): >>> File >>> "/tmp/tmp_wjCee/zc.buildout-1.4.3-py2.6.egg/zc/buildout/buildout.py", line >>> 1659, in main >>> user_defaults, windows_restart, command) >>> File >>> "/tmp/tmp_wjCee/zc.buildout-1.4.3-py2.6.egg/zc/buildout/buildout.py", line >>> 182, in __init__ >>> data['buildout'].copy(), override)) >>> File >>> "/tmp/tmp_wjCee/zc.buildout-1.4.3-py2.6.egg/zc/buildout/buildout.py", line >>> 1333, in _open >>> eresult = _open(base, extends.pop(0), seen, dl_options, override) >>> File >>> "/tmp/tmp_wjCee/zc.buildout-1.4.3-py2.6.egg/zc/buildout/buildout.py", line >>> 1313, in _open >>> parser.readfp(fp) >>> File "/usr/local/Python2.6.4/lib/python2.6/ConfigParser.py", line 305, in >>> readfp >>> self._read(fp, filename) >>> File "/usr/local/Python2.6.4/lib/python2.6/ConfigParser.py", line 510, in >>> _read >>> raise e >>> ParsingError: File contains parsing errors: >>> /home/ccomb/slave3/Python2.6.4-Linux-32bit/build/ztk.cfg >>> [line 206]: '<<< .mine\n' >>> [line 278]: '===\n' >>> [line 350]: '>>> .r111557\n' >> Seems like you had local, uncommitted changes there, which kind of hurts >> our ability to reproduce failures elsewhere. > > Ok there is something wrong, I'll clean eveything > > Before the buildout, I'm doing a > sed -i s/svn+ssh/svn/ ztk.cfg zopeapp.cfg > because the buildbot is not supposed to have a ssh key. > Then I'm doing a svn revert of these two files. > But if the buildout fails, the revert is not done. I've recreated the slave, then reordered the commands. It should be better. Yesterday there was a single failure on zope.app.container because of dublincore permissions. Today there are another one on the apidoc. Christophe > > Is there another way to disable ssh? > > > >> [1]http://buildbot.afpy.org/ztk1.0dev/builders/Python2.6.4%20Linux%2032bit/builds/61/steps/bootstrap/logs/stdio >> >> >> Tres. >> - -- >> === >> Tres Seaver +1 540-429-0999 tsea...@palladion.com >> Palladion Software "Excellence by Design"http://palladion.com >> -BEGIN PGP SIGNATURE- >> Version: GnuPG v1.4.9 (GNU/Linux) >> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org >> >> iEYEARECAAYFAkvZkPoACgkQ+gerLs4ltQ5GPACfV0/JsnOJj8t/axiii8OcJ1Hv >> yusAoILNm4Y1oYa9UTJ2Yy2s9xYWdxyt >> =xNdK >> -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 ) >> >> > > ___ > 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 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: 10 OK, 6 Failed
Summary of messages to the zope-tests list. Period Sat May 1 12:00:00 2010 UTC to Sun May 2 12:00:00 2010 UTC. There were 16 messages: 6 from Zope Tests, 9 from ccomb at free.fr, 1 from ct at gocept.com. Test failures - Subject: FAILED: Repository policy check found errors in 671 projects From: ct at gocept.com Date: Sat May 1 21:18:13 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-May/014216.html Subject: FAILED : ZTK 1.0dev / Python2.4.6 Linux 32bit From: ccomb at free.fr Date: Sat May 1 23:59:45 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-May/014227.html Subject: FAILED : ZTK 1.0dev / Python2.5.2 Linux 32bit From: ccomb at free.fr Date: Sun May 2 00:01:31 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-May/014228.html Subject: FAILED : ZTK 1.0dev / Python2.6.4 Linux 32bit From: ccomb at free.fr Date: Sun May 2 00:01:40 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-May/014229.html Subject: FAILED : Zope 3.4.1 KGS / Python2.4.6 32bit linux From: ccomb at free.fr Date: Sun May 2 00:23:16 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-May/014230.html Subject: FAILED : Zope 3.4.1 KGS / Python2.5.2 32bit linux From: ccomb at free.fr Date: Sun May 2 00:46:48 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-May/014231.html Tests passed OK --- Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Sat May 1 21:29:51 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-May/014217.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Sat May 1 21:31:51 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-May/014218.html Subject: OK : Zope-2.12 Python-2.6.4 : Linux From: Zope Tests Date: Sat May 1 21:33:51 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-May/014219.html Subject: OK : Zope-2.12-alltests Python-2.6.4 : Linux From: Zope Tests Date: Sat May 1 21:35:51 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-May/014220.html Subject: OK : Zope-trunk Python-2.6.4 : Linux From: Zope Tests Date: Sat May 1 21:37:51 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-May/014221.html Subject: OK : Zope-trunk-alltests Python-2.6.4 : Linux From: Zope Tests Date: Sat May 1 21:39:51 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-May/014222.html Subject: OK : BlueBream template / Python2.4.6 32bit linux From: ccomb at free.fr Date: Sat May 1 22:00:46 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-May/014223.html Subject: OK : BlueBream template / Python2.7b1 32bit linux From: ccomb at free.fr Date: Sat May 1 22:00:51 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-May/014225.html Subject: OK : BlueBream template / Python2.5.2 32bit linux From: ccomb at free.fr Date: Sat May 1 22:00:52 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-May/014224.html Subject: OK : BlueBream template / Python2.6.4 32bit linux From: ccomb at free.fr Date: Sat May 1 22:00:52 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-May/014226.html ___ 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 )
