Re: [Zope-dev] We need to get the board green
* Tres Seaver [2011-03-21 16:56]: > Too many never-resolve failures in our buildbots makes their output just > noise: the amount of effort required to diagnose the cause of a failure > seems to have no payoff if we don't get them each cleared up. On a tangentially-related note, what happened to the proposed new summarizer formatting? Half a year ago (or whenever), I got the impression it was going to be ready "in a few days", but it seems it never happened. What is needed to get this switched? (I'm not saying dressing the continuous failures up nicer is a solution to the problem Tres is presenting, but I do think the noisy format contributes to the confusion about the buildbots) Wolfgang ___ 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] We need to get the board green
* Tres Seaver [2011-03-22 14:18]: > On 03/22/2011 03:59 AM, Adam GROSZER wrote: >> And please please kick the guilty one's a**, not the buildbot maintainer's. >> It does not make much sense to disable tests just because they fail. > > Leaving the packages as "permanently failing" is obviously not doing > anything to motivate those maintainers. Leaving the board red is > *de-motivating* to the community at large, who have to wade through > failure reports for (apparently) unmaintained packages daily while > trying to diagnose stuff which might have been broken by changes made > the day before. I have to admit, I'm ignoring the buildbots completely at this time, (even though I think that having them in place could be very valuable), since all I perceive from them is failure-noise, and no trend of it getting less, at all, over the last few months. (That's my gut feeling, not based on research. It still makes me very much want to ignore them.) So, I agree with Tres: this situation is quite demotivating. But I also agree with Adam: I think the value of the buildbots is that they run tests, so disabling tests because they fail feels a little like closing our eyes shut because we don't want to see we're going to be falling off a cliff. I don't have much of an idea how to proceed, except maybe explicitly reducing the scope of the buildbots to a set of packages people around here care enough about that they want and will keep them green. Wolfgang ___ 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: 69 OK, 30 Failed, 10 Unknown
On Tue, Mar 22, 2011 at 4:30 PM, Gediminas Paulauskas wrote: > This one fails because python-gettext 1.1 tests use `with` statement > that is not available on python 2.4 or 2.5, and also depends on > unittest2 that has the same problem. This introduces a new dependency > to the stable branch, and that's not welcome... Right. I acted too quickly there, without taking the old Python versions into account. I haven't touched Python 2.5 or earlier in a long time, so I tend to forget their limitations. I reverted python-gettext to its 1.0 release for the ZTK and pulled it in on the Zope2 level, where we require Python 2.6+ for some time now. > I do not think that > either the with statement or unittest2 are needed for the fixes that > you did. It may look better, but can be made compatible with old > pythons and not add a dependency. Sure. You could write the code in a different way. I'm just not motivated to do so myself. Pull requests welcome at https://github.com/hannosch/python-gettext ;-) 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] We need to get the board green
On Mon, Mar 21, 2011 at 11:56:05AM -0400, Tres Seaver wrote: > Too many never-resolve failures in our buildbots makes their output just > noise: the amount of effort required to diagnose the cause of a failure > seems to have no payoff if we don't get them each cleared up. +100 to any method of reducing that noise. Continuously failing buildbots shouldn't make the system unusable. -- Brian Sutherland ___ 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: 69 OK, 30 Failed, 10 Unknown
2011/3/22 Zope Tests Summarizer : > Summary of messages to the zope-tests list. > Period Mon Mar 21 12:00:00 2011 UTC to Tue Mar 22 12:00:00 2011 UTC. ... > Subject: FAILED : Zope Buildbot / zopetoolkit-1.0_win-py2.4 slave-win > From: jdriessen at thehealthagency.com > Date: Mon Mar 21 14:49:16 EDT 2011 > URL: http://mail.zope.org/pipermail/zope-tests/2011-March/035748.html This one fails because python-gettext 1.1 tests use `with` statement that is not available on python 2.4 or 2.5, and also depends on unittest2 that has the same problem. This introduces a new dependency to the stable branch, and that's not welcome... I do not think that either the with statement or unittest2 are needed for the fixes that you did. It may look better, but can be made compatible with old pythons and not add a dependency. We don't run tests for external packages and it looks like only the tests are incompatible, so it is strange to see such failure. There is a warning for both packages: zip_safe flag not set; analyzing archive contents... and then the failures. Maybe setting zip_safe would prevent compilation of test files and installation will work on python 2.4? Also strange is that buildbots on Linux have not complained about this. Gediminas ___ 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] Non-ZCML config for ZCA. (Was: Anyone want to do Google Summer of code mentoring for PSF?)
Hi there, It is my understanding that the ZTK is primarily to adopt proven solutions that arise from our community that we intend to be shared by this community. I'll also note that Martian is already in use in combination with Bluebream, Zope 2 and Grok. With that, I was thinking, concerning alternative configuration mechanisms I think we should have: * a clear statement of use cases concerning configuration. * a weighing of the importance of these use cases, underlying reasons, etc. * an evaluation whether Martian or Venusian can fulfill those use cases. * if use cases are found that Martian or Venusian cannot fulfill, then an evaluation whether these can be made to fulfill them by modifying them. 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] We need to get the board green
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/22/2011 03:59 AM, Adam GROSZER wrote: > Hello, > > On Mon, 21 Mar 2011 11:56:05 -0400 you wrote: >> >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> Too many never-resolve failures in our buildbots makes their output just >> noise: the amount of effort required to diagnose the cause of a failure >> seems to have no payoff if we don't get them each cleared up. >> >> I'm just about done with trying to diagnose them, myself, which is >> making me sad, as I *want* to be pleased with the quality of the >> software our community produces. > > I'd say revert back to the original procedure. > The guilty dev has x days to fix the failure or the change gets reverted. > > PS: > And please please kick the guilty one's a**, not the buildbot maintainer's. > It does not make much sense to disable tests just because they fail. Chameleon is an external dependency, not managed as part of the Zope repository; I presume that the authors / maintainers of the z3c.* packages chose to depend on it with full knowledge of the risks that entails. If a new release of Chameleon breaks z3c.*, then it is the z3c.* maintainers whose tails need to be motivated: they should either get the exteranl dependency fixed, or work around it in their own packages (e.g., by pinning their dependency to a "known good" version, or by updating to use the newer APIs). Leaving the packages as "permanently failing" is obviously not doing anything to motivate those maintainers. Leaving the board red is *de-motivating* to the community at large, who have to wade through failure reports for (apparently) unmaintained packages daily while trying to diagnose stuff which might have been broken by changes made the day before. 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.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk2IobQACgkQ+gerLs4ltQ7ZeQCgopO4FTJE9KhgDsXy7OyCtw5V qbcAn3OG56JqlMqKAqOj/YjQRRf0VDoW =68up -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: 68 OK, 34 Failed, 6 Unknown
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/22/2011 03:54 AM, Adam GROSZER wrote: >>> Subject: FAILED : winbot / z3c.ptcompat_py_265_32 >>> From: buildbot at winbot.zope.org >>> Date: Sun Mar 20 20:04:06 EDT 2011 >>> URL: http://mail.zope.org/pipermail/zope-tests/2011-March/035712.html >>> >>> Subject: FAILED : winbot / z3c.rml_py_265_32 >>> From: buildbot at winbot.zope.org >>> Date: Sun Mar 20 20:23:58 EDT 2011 >>> URL: http://mail.zope.org/pipermail/zope-tests/2011-March/035713.html >>> >>> Subject: FAILED : winbot / z3c.form_py_265_32 >>> From: buildbot at winbot.zope.org >>> Date: Sun Mar 20 20:36:50 EDT 2011 >>> URL: http://mail.zope.org/pipermail/zope-tests/2011-March/035714.html >>> >>> Subject: FAILED : winbot / z3c.coverage_py_265_32 >>> From: buildbot at winbot.zope.org >>> Date: Sun Mar 20 20:56:05 EDT 2011 >>> URL: http://mail.zope.org/pipermail/zope-tests/2011-March/035718.html >>> >>> Subject: FAILED : winbot / z3c.macro_py_265_32 >>> From: buildbot at winbot.zope.org >>> Date: Sun Mar 20 20:57:10 EDT 2011 >>> URL: http://mail.zope.org/pipermail/zope-tests/2011-March/035719.html >>> >>> Subject: FAILED : winbot / z3c.pagelet_py_265_32 >>> From: buildbot at winbot.zope.org >>> Date: Sun Mar 20 21:08:18 EDT 2011 >>> URL: http://mail.zope.org/pipermail/zope-tests/2011-March/035720.html >>> >>> Subject: FAILED : winbot / z3c.recipe.paster_py_265_32 >>> From: buildbot at winbot.zope.org >>> Date: Sun Mar 20 21:26:39 EDT 2011 >>> URL: http://mail.zope.org/pipermail/zope-tests/2011-March/035721.html >>> >>> Subject: FAILED : winbot / z3c.template_py_265_32 >>> From: buildbot at winbot.zope.org >>> Date: Sun Mar 20 21:28:29 EDT 2011 >>> URL: http://mail.zope.org/pipermail/zope-tests/2011-March/035722.html >> >> Can we *please* either get these tests to pass, or else kill them off? >> At a bare minimum, put all the 'zc3.*' tests into a single buildout and >> have only one failure? > > No please no please. > This was Malthe, he broke those tests with the newest chameleon. Kick > his a** if you can get him online, I already sent him an email, but it > still looks like that. > z3c.form is definitely a prominent package that definitely needs > testing. If I disable those tests, those problems will never get fixed. You need to pin the packages to the non-borked version of chameleon. Leaving the board "permanently red" destroys the reason to have it at all. 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.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk2In6MACgkQ+gerLs4ltQ5SvACgnxbD2GBvdoaKOlFQOUVbTzdI fi4An0LQDqR1RUdm21uVarscqdwB5lrx =tR8Y -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] Anyone want to do Google Summer of code mentoring for PSF?
Am 20.03.2011, 18:07 Uhr, schrieb Tres Seaver : > The one downside I can see is giving up on the sugar^Wexpressivity of > calling the interface directly -- I guess we could propagate the > 'default_factory' argument through to the '__call__' of interface. Note > that I *wanted* some extra sugar at one point (doing utility lookup when > no arguments were passed to Interface.__call__), but I haven't missed > that convenience much since I went on a low sugar diet with BFG / > pyramid. Callable interfaces are, in my view, a huge wart with a pimple on top! Convenient, yes, but just try and explain why a specification against which "living" code should be built should itself be executable. Charlie -- Charlie Clark Managing Director Clark Consulting & Research German Office Helmholtzstr. 20 Düsseldorf D- 40215 Tel: +49-211-600-3657 Mobile: +49-178-782-6226 ___ 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] Non-ZCML config for ZCA. (Was: Anyone want to do Google Summer of code mentoring for PSF?)
Am 21.03.2011, 20:33 Uhr, schrieb Tres Seaver : > FWIW, I just added 'queryAdapterFactory' and 'queryMultiAdapterFactory' > APIs to zope.component on a branch: > http://svn.zope.org/zope.component/branches/tseaver-queryAdapterFactory/ > These APIs make the "almost never overridden" / dependency injection > case as compact for adapters as for utilities. This is an excellent suggestion! Being able to supply a default implementation that is easily overridden by a configuration is clean and easily understood and avoids both clumsy code checking and configuration. Charlie -- Charlie Clark Managing Director Clark Consulting & Research German Office Helmholtzstr. 20 Düsseldorf D- 40215 Tel: +49-211-600-3657 Mobile: +49-178-782-6226 ___ 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: 69 OK, 30 Failed, 10 Unknown
Summary of messages to the zope-tests list. Period Mon Mar 21 12:00:00 2011 UTC to Tue Mar 22 12:00:00 2011 UTC. There were 109 messages: 8 from Zope Tests, 4 from buildbot at pov.lt, 30 from buildbot at winbot.zope.org, 8 from ccomb at free.fr, 59 from jdriessen at thehealthagency.com. Test failures - Subject: FAILED : Zope Buildbot / zope2.12-py2.6 slave-ubuntu64 From: jdriessen at thehealthagency.com Date: Mon Mar 21 14:32:54 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/035740.html Subject: FAILED : Zope Buildbot / zope2.14-py2.6 slave-ubuntu64 From: jdriessen at thehealthagency.com Date: Mon Mar 21 14:37:09 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/035743.html Subject: FAILED : Zope Buildbot / zope2.14-py2.7 slave-ubuntu64 From: jdriessen at thehealthagency.com Date: Mon Mar 21 14:38:33 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/035744.html Subject: FAILED : Zope Buildbot / zope2.13_win-py2.6 slave-win From: jdriessen at thehealthagency.com Date: Mon Mar 21 14:41:28 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/035745.html Subject: FAILED : Zope Buildbot / zope2.13_win-py2.7 slave-win From: jdriessen at thehealthagency.com Date: Mon Mar 21 14:43:14 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/035746.html Subject: FAILED : Zope Buildbot / zopetoolkit-1.0_win-py2.4 slave-win From: jdriessen at thehealthagency.com Date: Mon Mar 21 14:49:16 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/035748.html Subject: FAILED : Zope Buildbot / zope2.13_win-py2.7 slave-win From: jdriessen at thehealthagency.com Date: Mon Mar 21 16:02:52 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/035761.html Subject: FAILED : Zope Buildbot / zope2.14-py2.6 slave-ubuntu32 From: jdriessen at thehealthagency.com Date: Mon Mar 21 16:22:28 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/035769.html Subject: FAILED : Zope Buildbot / zope2.14-py2.7 slave-ubuntu32 From: jdriessen at thehealthagency.com Date: Mon Mar 21 16:24:01 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/035771.html Subject: FAILED : Zope Buildbot / zopetoolkit-1.1-py2.6 slave-ubuntu32 From: jdriessen at thehealthagency.com Date: Mon Mar 21 16:51:00 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/035781.html Subject: FAILED : Zope Buildbot / zopetoolkit-py2.6 slave-ubuntu32 From: jdriessen at thehealthagency.com Date: Mon Mar 21 16:56:33 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/035785.html Subject: FAILED : winbot / z3c.form_py_265_32 From: buildbot at winbot.zope.org Date: Mon Mar 21 17:08:46 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/035788.html Subject: FAILED : winbot / zc_buildout_dev py_254_win32 From: buildbot at winbot.zope.org Date: Mon Mar 21 17:08:58 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/035789.html Subject: FAILED : winbot / zc_buildout_dev py_265_win32 From: buildbot at winbot.zope.org Date: Mon Mar 21 17:09:10 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/035790.html Subject: FAILED : winbot / zc_buildout_dev py_265_win64 From: buildbot at winbot.zope.org Date: Mon Mar 21 17:09:21 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/035791.html Subject: FAILED : winbot / zc_buildout_dev py_270_win32 From: buildbot at winbot.zope.org Date: Mon Mar 21 17:09:32 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/035792.html Subject: FAILED : winbot / zc_buildout_dev py_270_win64 From: buildbot at winbot.zope.org Date: Mon Mar 21 17:09:43 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/035793.html Subject: FAILED : Zope Buildbot / zope2.14-py2.6 slave-osx From: jdriessen at thehealthagency.com Date: Mon Mar 21 17:31:51 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/035798.html Subject: FAILED : Zope Buildbot / zope2.14-py2.7 slave-osx From: jdriessen at thehealthagency.com Date: Mon Mar 21 17:34:13 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/035799.html Subject: FAILED : winbot / z3c.ptcompat_py_265_32 From: buildbot at winbot.zope.org Date: Mon Mar 21 20:11:54 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/035813.html Subject: FAILED : winbot / z3c.rml_py_265_32 From: buildbot at winbot.zope.org Date: Mon Mar 21 20:31:03 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/035814.html Subject: FAILED : winbot / z3c.form_py_265_32 From: buildbot at winbot.zope.org Date: Mon Mar 21 20:43:32 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/035815.html Subject: FAILED : winbot / z3c.coverage_py_265_32 From: buildbot at winbot.zope.org Date: Mon Mar 21 21:02:37 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/035819.html Subject: FAILED : winbot / z3c.macro_py_2
Re: [Zope-dev] We need to get the board green
Hello, On Mon, 21 Mar 2011 11:56:05 -0400 you wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Too many never-resolve failures in our buildbots makes their output just > noise: the amount of effort required to diagnose the cause of a failure > seems to have no payoff if we don't get them each cleared up. > > I'm just about done with trying to diagnose them, myself, which is > making me sad, as I *want* to be pleased with the quality of the > software our community produces. I'd say revert back to the original procedure. The guilty dev has x days to fix the failure or the change gets reverted. PS: And please please kick the guilty one's a**, not the buildbot maintainer's. It does not make much sense to disable tests just because they fail. -- Best regards, Adam GROSZER -- Quote of the day: If Presidents don't do it to their wives, they do it to the country. - Mel Brooks ___ 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: 68 OK, 34 Failed, 6 Unknown
Hello, On Mon, 21 Mar 2011 11:53:01 -0400 you wrote: >> Subject: FAILED : Zope Buildbot / zope2.13_win-py2.6 slave-win >> From: jdriessen at thehealthagency.com >> Date: Sun Mar 20 15:41:43 EDT 2011 >> URL: http://mail.zope.org/pipermail/zope-tests/2011-March/035665.html >> >> Subject: FAILED : Zope Buildbot / zope2.13_win-py2.7 slave-win >> From: jdriessen at thehealthagency.com >> Date: Sun Mar 20 15:43:55 EDT 2011 >> URL: http://mail.zope.org/pipermail/zope-tests/2011-March/035666.html > > These are both weird Windows build failures:: > > error: Setup script exited with error: Unable to find vcvarsall.bat > While: > Installing test. > Getting distribution for 'Acquisition==2.13.7'. > Error: Couldn't install: Acquisition 2.13.7 Weird, eggs should be in place. Maybe the builder got the tarball and uses that... Deleting the tarball should help. >> Subject: FAILED : winbot / zc_buildout_dev py_254_win32 >> From: buildbot at winbot.zope.org >> Date: Sun Mar 20 17:07:28 EDT 2011 >> URL: http://mail.zope.org/pipermail/zope-tests/2011-March/035690.html >> >> Subject: FAILED : winbot / zc_buildout_dev py_265_win32 >> From: buildbot at winbot.zope.org >> Date: Sun Mar 20 17:07:39 EDT 2011 >> URL: http://mail.zope.org/pipermail/zope-tests/2011-March/035691.html >> >> Subject: FAILED : winbot / zc_buildout_dev py_265_win64 >> From: buildbot at winbot.zope.org >> Date: Sun Mar 20 17:07:50 EDT 2011 >> URL: http://mail.zope.org/pipermail/zope-tests/2011-March/035692.html >> >> Subject: FAILED : winbot / zc_buildout_dev py_270_win32 >> From: buildbot at winbot.zope.org >> Date: Sun Mar 20 17:08:00 EDT 2011 >> URL: http://mail.zope.org/pipermail/zope-tests/2011-March/035693.html >> >> Subject: FAILED : winbot / zc_buildout_dev py_270_win64 >> From: buildbot at winbot.zope.org >> Date: Sun Mar 20 17:08:14 EDT 2011 >> URL: http://mail.zope.org/pipermail/zope-tests/2011-March/035694.html > > More weird Windows build failures:: > > > c:\buildslave\zc_buildout_dev_py_254_win32\build>bin\test.exe > - --exit-with-status -1" > 'bin\test.exe' is not recognized as an internal or external command, > operable program or batch file. Bootstrap failed, it just does not exit with the right exitcode. See: http://winbot.zope.org/builders/zc_buildout_dev%20py_270_win32/builds/239/steps/bootstrap/logs/stdio >> Subject: FAILED : winbot / z3c.ptcompat_py_265_32 >> From: buildbot at winbot.zope.org >> Date: Sun Mar 20 20:04:06 EDT 2011 >> URL: http://mail.zope.org/pipermail/zope-tests/2011-March/035712.html >> >> Subject: FAILED : winbot / z3c.rml_py_265_32 >> From: buildbot at winbot.zope.org >> Date: Sun Mar 20 20:23:58 EDT 2011 >> URL: http://mail.zope.org/pipermail/zope-tests/2011-March/035713.html >> >> Subject: FAILED : winbot / z3c.form_py_265_32 >> From: buildbot at winbot.zope.org >> Date: Sun Mar 20 20:36:50 EDT 2011 >> URL: http://mail.zope.org/pipermail/zope-tests/2011-March/035714.html >> >> Subject: FAILED : winbot / z3c.coverage_py_265_32 >> From: buildbot at winbot.zope.org >> Date: Sun Mar 20 20:56:05 EDT 2011 >> URL: http://mail.zope.org/pipermail/zope-tests/2011-March/035718.html >> >> Subject: FAILED : winbot / z3c.macro_py_265_32 >> From: buildbot at winbot.zope.org >> Date: Sun Mar 20 20:57:10 EDT 2011 >> URL: http://mail.zope.org/pipermail/zope-tests/2011-March/035719.html >> >> Subject: FAILED : winbot / z3c.pagelet_py_265_32 >> From: buildbot at winbot.zope.org >> Date: Sun Mar 20 21:08:18 EDT 2011 >> URL: http://mail.zope.org/pipermail/zope-tests/2011-March/035720.html >> >> Subject: FAILED : winbot / z3c.recipe.paster_py_265_32 >> From: buildbot at winbot.zope.org >> Date: Sun Mar 20 21:26:39 EDT 2011 >> URL: http://mail.zope.org/pipermail/zope-tests/2011-March/035721.html >> >> Subject: FAILED : winbot / z3c.template_py_265_32 >> From: buildbot at winbot.zope.org >> Date: Sun Mar 20 21:28:29 EDT 2011 >> URL: http://mail.zope.org/pipermail/zope-tests/2011-March/035722.html > > Can we *please* either get these tests to pass, or else kill them off? > At a bare minimum, put all the 'zc3.*' tests into a single buildout and > have only one failure? No please no please. This was Malthe, he broke those tests with the newest chameleon. Kick his a** if you can get him online, I already sent him an email, but it still looks like that. z3c.form is definitely a prominent package that definitely needs testing. If I disable those tests, those problems will never get fixed. -- Best regards, Adam GROSZER -- Quote of the day: Don't feed the bats tonight. ___ 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 )
