[Zope-dev] Re: Zope Tests: 8 OK, 1 Failed
Hi! Andreas Jung wrote: --On 29. Oktober 2006 10:06:42 +0100 yuppie <[EMAIL PROTECTED]> wrote: Oops! Sorry! I did not mean to cause any confusion: - AFAICT the 2.10 branch points already to the 3.3.0 tag. Right. However Philipp pointed out that the Zope 2 trunk uses the Zope 3 trunk right now. I pointed the reasons for using the Zope 3 trunk in a former posting. I guess you mean 3.3 branch HEAD, not Zope 3 trunk HEAD. My argument for using the trunk instead of a fixed revision/tag is: when we develop against the trunk or implement something on the trunk then we want to be sure that the code also works with the latest Zope 3 changes. Otherwise something might break when we update the svn:exernals to latest Zope 3 changes at some time before an upcoming major release. So I would prefer that things break early than late. However as seen this approach has other side-effects..but I am open to let the svn:externals point to tags if you want that... Well. I would prefer if there would be somebody who volunteers to test Zope 2 every now and then with the latest Zope 3 revision. If he or she makes sure all tests pass, the svn:externals can be updated to that revision. In the long run the issues have to be resolved anyway, so doing this step by step would not be much extra work. And we could avoid to do big last minute changes right before the release. Pointing the svn:externals to the HEAD might encourage people to volunteer for fixing the issues, but I'm afraid a broken HEAD also discourages people to contribute other changes. Just my 2 cents. Cheers, Yuppie ___ 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] Re: Zope Tests: 8 OK, 1 Failed
--On 29. Oktober 2006 10:06:42 +0100 yuppie <[EMAIL PROTECTED]> wrote: Oops! Sorry! I did not mean to cause any confusion: - AFAICT the 2.10 branch points already to the 3.3.0 tag. Right. However Philipp pointed out that the Zope 2 trunk uses the Zope 3 trunk right now. I pointed the reasons for using the Zope 3 trunk in a former posting. My argument for using the trunk instead of a fixed revision/tag is: when we develop against the trunk or implement something on the trunk then we want to be sure that the code also works with the latest Zope 3 changes. Otherwise something might break when we update the svn:exernals to latest Zope 3 changes at some time before an upcoming major release. So I would prefer that things break early than late. However as seen this approach has other side-effects..but I am open to let the svn:externals point to tags if you want that... Andreas pgp8Cdtm8XryA.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] Re: Zope Tests: 8 OK, 1 Failed
Hi Andreas! Hi Philipp! Andreas Jung wrote: --On 28. Oktober 2006 23:50:36 +0200 Philipp von Weitershausen <[EMAIL PROTECTED]> wrote: OMG, why are we using the 3.3 branch HEAD on the 2.10 branch??? This is how Stephan's fix got pulled into Zope 2 automatically and *automatically broke* Zope 2. It also broke Five trunk for some reason (the formlib stuff). Obviously, this is bad. We should stick to specific revisions or tags when pointing to externals. Pointing to HEAD of a branch or trunk is insane as it's an uncontrollable risk. As discussed with you: I will change the externals on the 2.10 branch to the related 3.3 tag. Oops! Sorry! I did not mean to cause any confusion: - AFAICT the 2.10 branch points already to the 3.3.0 tag. - The test failure is on Zope trunk which points to the 3.3 branch HEAD. - The collector issue I opened mentions an unsupported combination (Zope 2.10 branch with Five trunk and Zope 3.3 branch). I hope there will be a Zope 3.3.1 release that will be included in Zope 2.10.1. The person who will stitch in the Zope 3.3.1 tag will see this failure and http://www.zope.org/Collectors/Zope/2198 might give a hint what the problem is. Cheers, Yuppie ___ 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] Re: Zope Tests: 8 OK, 1 Failed
--On 28. Oktober 2006 23:50:36 +0200 Philipp von Weitershausen <[EMAIL PROTECTED]> wrote: OMG, why are we using the 3.3 branch HEAD on the 2.10 branch??? This is how Stephan's fix got pulled into Zope 2 automatically and *automatically broke* Zope 2. It also broke Five trunk for some reason (the formlib stuff). Obviously, this is bad. We should stick to specific revisions or tags when pointing to externals. Pointing to HEAD of a branch or trunk is insane as it's an uncontrollable risk. As discussed with you: I will change the externals on the 2.10 branch to the related 3.3 tag. Andreas pgpYJI9YlhzE5.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 )
[Zope-dev] Re: Zope Tests: 8 OK, 1 Failed
yuppie wrote: Tres Seaver wrote: Test failures - Subject: FAILED (errors=1) : Zope-trunk Python-2.4.3 : Linux From: Zope Unit Tests Date: Mon Oct 23 21:35:18 EDT 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-October/006371.html First, thanks for resuming this collected report. I would much rather have links directly to the broken test run than to the buildbot page. Second, I can reproduce the failure on my machine, at least after an 'svn up' this morning, but have no obvious clue why it would be broken: the code for local site stuff in Five hasn't changed since May. The failure showed up after this checkin: http://svn.zope.org/?rev=70383&view=rev But I didn't have time to track it down, so I opened this collector issue: http://www.zope.org/Collectors/Zope/2198 OMG, why are we using the 3.3 branch HEAD on the 2.10 branch??? This is how Stephan's fix got pulled into Zope 2 automatically and *automatically broke* Zope 2. It also broke Five trunk for some reason (the formlib stuff). Obviously, this is bad. We should stick to specific revisions or tags when pointing to externals. Pointing to HEAD of a branch or trunk is insane as it's an uncontrollable risk. Philipp ___ 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] Re: Zope Tests: 8 OK, 1 Failed
Tres Seaver wrote: Test failures - Subject: FAILED (errors=1) : Zope-trunk Python-2.4.3 : Linux From: Zope Unit Tests Date: Mon Oct 23 21:35:18 EDT 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-October/006371.html First, thanks for resuming this collected report. I would much rather have links directly to the broken test run than to the buildbot page. Second, I can reproduce the failure on my machine, at least after an 'svn up' this morning, but have no obvious clue why it would be broken: the code for local site stuff in Five hasn't changed since May. The failure showed up after this checkin: http://svn.zope.org/?rev=70383&view=rev But I didn't have time to track it down, so I opened this collector issue: http://www.zope.org/Collectors/Zope/2198 Cheers, Yuppie ___ 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] Re: Zope Tests: 8 OK, 1 Failed
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Zope Tests Summarizer wrote: > Test failures > - > > Subject: FAILED (errors=1) : Zope-trunk Python-2.4.3 : Linux > From: Zope Unit Tests > Date: Mon Oct 23 21:35:18 EDT 2006 > URL: http://mail.zope.org/pipermail/zope-tests/2006-October/006371.html First, thanks for resuming this collected report. I would much rather have links directly to the broken test run than to the buildbot page. Second, I can reproduce the failure on my machine, at least after an 'svn up' this morning, but have no obvious clue why it would be broken: the code for local site stuff in Five hasn't changed since May. Tres. - -- === Tres Seaver +1 202-558-7113 [EMAIL PROTECTED] Palladion Software "Excellence by Design"http://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFPfkR+gerLs4ltQ4RAtglAJ0QxuTiRj7TIDgm8YNFJWyGVgTlLgCgx3g5 4MpiZcsh0pRpuIYr6zLmm2c= =Bqcs -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 )
