Re: [Zope3-dev] working towards 3.4 alpha release
Hi, Am Samstag, den 14.04.2007, 08:06 -0400 schrieb Benji York: > Christian Theune wrote: > > I noticed that the buildbots have not run a successfull Zope 3 trunk > > build since March 25. :( > > The only builder that is configured to run the trunk and is currently > on-line is zc-buildbot, and it would appear to be running the tests with > every trunk check-in. > > OTOH, the 3.2, and 3.3 branches are broken and have been for quite some > time. > > Sidebar: when trying to kick off a run for those two branches those two > builders started exhibiting assertion errors, I'm looking into why that is. Appreciated. > > Most of the clients are broken. > > The single Windows slave that is "purple" is a result of bugs in > twisted/buildbot. Hopefully newer versions don't have these problems. > (We currently run 0.6.6, 0.7.5 is the latest). I don't have time to > fight with upgrading at the moment. Ok, good to know. > Two others are off-line, see the nagging section below. ;) > > > The one at ZC is good but hasn't been > > run for quite a while. > > zc-buildout appears to run the trunk tests with every check-in. Is that > the one you are referring to? The 3.2 and 3.3 tests failed the last > time they were manually run. I don't think any changes have been made > to those branches since, therefore not further runs have been triggered. > > > Some of the rules that detect changes in the > > branches seem unreliable. > > Can you give an example? I'm *pretty* sure that there were checkins on the trunk after March 25. Those have never been run by zc-buildout. Did I miss anything? > > I propose to start make the clients do nightly builds. > > That's fine with me. I can get that configured pretty easily. Yay! Double please from me. :) > > Also, do we have > > someone who is the official 'client nagging guy' to remind people when > > their buildbot clients die? > > I'll be glad to nag anyone, but don't consider it a privilege available > to only a few. The slave names are pretty clear (a couple could be > clearer), so anyone can get a good nag in once and a while. True. Sidebar from me: Obviously this is because of the instability that buildout does. It's not about annoying people about their installations. Christian -- gocept gmbh & co. kg - forsterstraße 29 - 06112 halle/saale - germany www.gocept.com - [EMAIL PROTECTED] - phone +49 345 122 9889 7 - fax +49 345 122 9889 1 - zope and plone consulting and development signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ Zope3-dev mailing list [EMAIL PROTECTED] Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] buildbot failure in Zope3 branches Zope-3.1 2.4 Windows 2000 zc-bbwin4
The Buildbot has detected a failed build of Zope3 branches Zope-3.1 2.4 Windows 2000 zc-bbwin4. Buildbot URL: http://buildbot.zope.org/ Build Reason: The web-page 'force build' button was pressed by 'Benji': see if Windows slave is feeling better Build Source Stamp: None Blamelist: BUILD FAILED: failed test sincerely, -The Buildbot ___ Zope3-dev mailing list [EMAIL PROTECTED] Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] working towards 3.4 alpha release
Christian Theune wrote: I noticed that the buildbots have not run a successfull Zope 3 trunk build since March 25. :( The only builder that is configured to run the trunk and is currently on-line is zc-buildbot, and it would appear to be running the tests with every trunk check-in. OTOH, the 3.2, and 3.3 branches are broken and have been for quite some time. Sidebar: when trying to kick off a run for those two branches those two builders started exhibiting assertion errors, I'm looking into why that is. Most of the clients are broken. The single Windows slave that is "purple" is a result of bugs in twisted/buildbot. Hopefully newer versions don't have these problems. (We currently run 0.6.6, 0.7.5 is the latest). I don't have time to fight with upgrading at the moment. Two others are off-line, see the nagging section below. ;) The one at ZC is good but hasn't been run for quite a while. zc-buildout appears to run the trunk tests with every check-in. Is that the one you are referring to? The 3.2 and 3.3 tests failed the last time they were manually run. I don't think any changes have been made to those branches since, therefore not further runs have been triggered. Some of the rules that detect changes in the branches seem unreliable. Can you give an example? I propose to start make the clients do nightly builds. That's fine with me. I can get that configured pretty easily. Also, do we have someone who is the official 'client nagging guy' to remind people when their buildbot clients die? I'll be glad to nag anyone, but don't consider it a privilege available to only a few. The slave names are pretty clear (a couple could be clearer), so anyone can get a good nag in once and a while. -- Benji York Senior Software Engineer Zope Corporation ___ Zope3-dev mailing list [EMAIL PROTECTED] Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] working towards 3.4 alpha release
And on a third note: Those tests fail without using --all as well. I noticed that the buildbots have not run a successfull Zope 3 trunk build since March 25. :( Most of the clients are broken. The one at ZC is good but hasn't been run for quite a while. Some of the rules that detect changes in the branches seem unreliable. I propose to start make the clients do nightly builds. Also, do we have someone who is the official 'client nagging guy' to remind people when their buildbot clients die? Christian Am Samstag, den 14.04.2007, 10:19 +0200 schrieb Christian Theune: > More test breakage: > > Running zope.app.workflow.testing.AppWorkflowLayer tests: > Running in a subprocess. > Set up zope.app.workflow.testing.AppWorkflowLayer in 1.290 seconds. > Ran 5 tests with 0 failures and 0 errors in 0.720 seconds. > Tear down zope.app.workflow.testing.AppWorkflowLayer in 0.000 seconds. > Traceback (most recent call last): > File "test.py", line 61, in ? > result = testrunner.run(defaults) > File > "/home/ctheune/Development/Zope-3.4a1/src/zope/testing/testrunner.py", > line 256, in run > failed = not run_with_options(options) > File > "/home/ctheune/Development/Zope-3.4a1/src/zope/testing/testrunner.py", > line 423, in run_with_options > failures, errors) > File > "/home/ctheune/Development/Zope-3.4a1/src/zope/testing/testrunner.py", > line 620, in resume_tests > for l in subout: > IOError: [Errno 4] Interrupted system call > > > ___ > Zope3-dev mailing list > [EMAIL PROTECTED] > Unsub: http://mail.zope.org/mailman/options/zope3-dev/ct%40gocept.com > -- gocept gmbh & co. kg - forsterstraße 29 - 06112 halle/saale - germany www.gocept.com - [EMAIL PROTECTED] - phone +49 345 122 9889 7 - fax +49 345 122 9889 1 - zope and plone consulting and development signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ Zope3-dev mailing list [EMAIL PROTECTED] Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] working towards 3.4 alpha release
More test breakage: Running zope.app.workflow.testing.AppWorkflowLayer tests: Running in a subprocess. Set up zope.app.workflow.testing.AppWorkflowLayer in 1.290 seconds. Ran 5 tests with 0 failures and 0 errors in 0.720 seconds. Tear down zope.app.workflow.testing.AppWorkflowLayer in 0.000 seconds. Traceback (most recent call last): File "test.py", line 61, in ? result = testrunner.run(defaults) File "/home/ctheune/Development/Zope-3.4a1/src/zope/testing/testrunner.py", line 256, in run failed = not run_with_options(options) File "/home/ctheune/Development/Zope-3.4a1/src/zope/testing/testrunner.py", line 423, in run_with_options failures, errors) File "/home/ctheune/Development/Zope-3.4a1/src/zope/testing/testrunner.py", line 620, in resume_tests for l in subout: IOError: [Errno 4] Interrupted system call -- gocept gmbh & co. kg - forsterstraße 29 - 06112 halle/saale - germany www.gocept.com - [EMAIL PROTECTED] - phone +49 345 122 9889 7 - fax +49 345 122 9889 1 - zope and plone consulting and development signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ Zope3-dev mailing list [EMAIL PROTECTED] Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] working towards 3.4 alpha release
Hi,
I'm working on the 3.4 alpha release today. When running _all_ tests, I
found this unit test to fail:
[EMAIL PROTECTED] ~/Development/Zope-3.4a1 $ python test.py --all
Running unit tests:
Failure in test testStandalone (zope.component.tests.StandaloneTests)
Traceback (most recent call last):
File "/usr/lib/python2.4/unittest.py", line 260, in run
testMethod()
File
"/home/ctheune/Development/Zope-3.4a1/src/zope/component/tests.py", line
984, in testStandalone
self.fail(''.join(lines))
File "/usr/lib/python2.4/unittest.py", line 301, in fail
raise self.failureException, msg
AssertionError: .
--
Ran 1 test in 0.010s
OK
Ran 6863 tests with 1 failures and 0 errors in 87.973 seconds.
Does this ring a bell somewhere?
--
gocept gmbh & co. kg - forsterstraße 29 - 06112 halle/saale - germany
www.gocept.com - [EMAIL PROTECTED] - phone +49 345 122 9889 7 -
fax +49 345 122 9889 1 - zope and plone consulting and development
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
___
Zope3-dev mailing list
[EMAIL PROTECTED]
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
