Discussion:
zope-tests - FAILED: 20, OK: 6
(too old to reply)
Zope tests summarizer
2017-04-09 23:00:02 UTC
Permalink
This is the summary for test reports received on the
zope-tests list between 2017-04-08 00:00:00 UTC and 2017-04-09 00:00:00 UTC:

See the footnotes for test reports of unsuccessful builds.

An up-to date view of the builders is also available in our
buildbot documentation:
http://docs.zope.org/zopetoolkit/process/buildbots.html#the-nightly-builds

Reports received
----------------

winbot / ZODB_dev py_270_win32
winbot / ZODB_dev py_270_win64
winbot / ZODB_dev py_330_win32
winbot / ZODB_dev py_330_win64
winbot / ZODB_dev py_340_win32
winbot / ZODB_dev py_340_win64
[1] winbot / z3c.contents_py_270_win32
[2] winbot / z3c.contents_py_270_win64
[3] winbot / z3c.jsonrpc_py_270_win32
[4] winbot / z3c.jsonrpc_py_270_win64
[5] winbot / z3c.ptcompat_py_270_win64
[6] winbot / z3c.testing_py_270_win32
[7] winbot / zc.catalog_py_270_win64
[8] winbot / zc.resourcelibrary_py_270_win32
[9] winbot / zope.app.applicationcontrol_py_270_win32
[10] winbot / zope.app.authentication_py_270_win32
[11] winbot / zope.app.authentication_py_270_win64
[12] winbot / zope.app.component_py_270_win32
[13] winbot / zope.app.component_py_270_win64
[14] winbot / zope.app.testing_py_270_win32
[15] winbot / zope.app.testing_py_270_win64
[16] winbot / zope.index_py_270_win32
[17] winbot / ztk_dev py_270_win32
[18] winbot / ztk_dev py_270_win64
[19] winbot / ztk_dev py_330_win32
[20] winbot / ztk_dev py_330_win64

Non-OK results
--------------

[1] FAILED winbot / z3c.contents_py_270_win32
https://mail.zope.org/pipermail/zope-tests/2017-April/104339.html


[2] FAILED winbot / z3c.contents_py_270_win64
https://mail.zope.org/pipermail/zope-tests/2017-April/104345.html


[3] FAILED winbot / z3c.jsonrpc_py_270_win32
https://mail.zope.org/pipermail/zope-tests/2017-April/104335.html


[4] FAILED winbot / z3c.jsonrpc_py_270_win64
https://mail.zope.org/pipermail/zope-tests/2017-April/104330.html


[5] FAILED winbot / z3c.ptcompat_py_270_win64
https://mail.zope.org/pipermail/zope-tests/2017-April/104344.html


[6] FAILED winbot / z3c.testing_py_270_win32
https://mail.zope.org/pipermail/zope-tests/2017-April/104336.html


[7] FAILED winbot / zc.catalog_py_270_win64
https://mail.zope.org/pipermail/zope-tests/2017-April/104340.html


[8] FAILED winbot / zc.resourcelibrary_py_270_win32
https://mail.zope.org/pipermail/zope-tests/2017-April/104342.html


[9] FAILED winbot / zope.app.applicationcontrol_py_270_win32
https://mail.zope.org/pipermail/zope-tests/2017-April/104332.html


[10] FAILED winbot / zope.app.authentication_py_270_win32
https://mail.zope.org/pipermail/zope-tests/2017-April/104337.html


[11] FAILED winbot / zope.app.authentication_py_270_win64
https://mail.zope.org/pipermail/zope-tests/2017-April/104341.html


[12] FAILED winbot / zope.app.component_py_270_win32
https://mail.zope.org/pipermail/zope-tests/2017-April/104343.html


[13] FAILED winbot / zope.app.component_py_270_win64
https://mail.zope.org/pipermail/zope-tests/2017-April/104338.html


[14] FAILED winbot / zope.app.testing_py_270_win32
https://mail.zope.org/pipermail/zope-tests/2017-April/104334.html


[15] FAILED winbot / zope.app.testing_py_270_win64
https://mail.zope.org/pipermail/zope-tests/2017-April/104331.html


[16] FAILED winbot / zope.index_py_270_win32
https://mail.zope.org/pipermail/zope-tests/2017-April/104333.html


[17] FAILED winbot / ztk_dev py_270_win32
https://mail.zope.org/pipermail/zope-tests/2017-April/104346.html


[18] FAILED winbot / ztk_dev py_270_win64
https://mail.zope.org/pipermail/zope-tests/2017-April/104347.html


[19] FAILED winbot / ztk_dev py_330_win32
https://mail.zope.org/pipermail/zope-tests/2017-April/104348.html


[20] FAILED winbot / ztk_dev py_330_win64
https://mail.zope.org/pipermail/zope-tests/2017-April/104349.html


_______________________________________________
Zope-Dev maillist - Zope-***@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 )
Jim Fulton
2017-04-10 14:40:52 UTC
Permalink
Post by Zope tests summarizer
This is the summary for test reports received on the
See the footnotes for test reports of unsuccessful builds.
An up-to date view of the builders is also available in our
http://docs.zope.org/zopetoolkit/process/buildbots.html#the-nightly-builds
Reports received
----------------
winbot / ZODB_dev py_270_win32
winbot / ZODB_dev py_270_win64
winbot / ZODB_dev py_330_win32
winbot / ZODB_dev py_330_win64
winbot / ZODB_dev py_340_win32
winbot / ZODB_dev py_340_win64
I've added appveyor tests for ZODB:
https://ci.appveyor.com/project/jimfulton/zodb/build/1.0.27

so this isn't needed anymore.
Post by Zope tests summarizer
[1] winbot / z3c.contents_py_270_win32
[2] winbot / z3c.contents_py_270_win64
[3] winbot / z3c.jsonrpc_py_270_win32
[4] winbot / z3c.jsonrpc_py_270_win64
[5] winbot / z3c.ptcompat_py_270_win64
[6] winbot / z3c.testing_py_270_win32
[7] winbot / zc.catalog_py_270_win64
[8] winbot / zc.resourcelibrary_py_270_win32
[9] winbot / zope.app.applicationcontrol_py_270_win32
[10] winbot / zope.app.authentication_py_270_win32
[11] winbot / zope.app.authentication_py_270_win64
[12] winbot / zope.app.component_py_270_win32
[13] winbot / zope.app.component_py_270_win64
[14] winbot / zope.app.testing_py_270_win32
[15] winbot / zope.app.testing_py_270_win64
[16] winbot / zope.index_py_270_win32
[17] winbot / ztk_dev py_270_win32
[18] winbot / ztk_dev py_270_win64
[19] winbot / ztk_dev py_330_win32
[20] winbot / ztk_dev py_330_win64
IMO, these (and the 6 that pass) should all be converted to appveyor.

In any case, no one seems to be paying attention to these reports.

Jim
Jim Fulton
2017-04-10 14:48:46 UTC
Permalink
Post by Zope tests summarizer
This is the summary for test reports received on the
See the footnotes for test reports of unsuccessful builds.
An up-to date view of the builders is also available in our
http://docs.zope.org/zopetoolkit/process/buildbots.html#the-nightly-builds
Reports received
----------------
winbot / ZODB_dev py_270_win32
winbot / ZODB_dev py_270_win64
winbot / ZODB_dev py_330_win32
winbot / ZODB_dev py_330_win64
winbot / ZODB_dev py_340_win32
winbot / ZODB_dev py_340_win64
I've added appveyor tests for ZODB: https://ci.appveyor.com/
project/jimfulton/zodb/build/1.0.27

so this isn't needed anymore.
Post by Zope tests summarizer
[1] winbot / z3c.contents_py_270_win32
[2] winbot / z3c.contents_py_270_win64
[3] winbot / z3c.jsonrpc_py_270_win32
[4] winbot / z3c.jsonrpc_py_270_win64
[5] winbot / z3c.ptcompat_py_270_win64
[6] winbot / z3c.testing_py_270_win32
[7] winbot / zc.catalog_py_270_win64
[8] winbot / zc.resourcelibrary_py_270_win32
[9] winbot / zope.app.applicationcontrol_py_270_win32
[10] winbot / zope.app.authentication_py_270_win32
[11] winbot / zope.app.authentication_py_270_win64
[12] winbot / zope.app.component_py_270_win32
[13] winbot / zope.app.component_py_270_win64
[14] winbot / zope.app.testing_py_270_win32
[15] winbot / zope.app.testing_py_270_win64
[16] winbot / zope.index_py_270_win32
[17] winbot / ztk_dev py_270_win32
[18] winbot / ztk_dev py_270_win64
[19] winbot / ztk_dev py_330_win32
Post by Zope tests summarizer
[20] winbot / ztk_dev py_330_win64
IMO, these (and the 6 that pass) should all be converted to appveyor.

In any case, no one seems to be paying attention to these reports.

Jim
--
Jim Fulton
http://jimfulton.info
Michael Howitz
2017-04-11 06:46:01 UTC
Permalink
Am 10.04.2017 um 16:48 schrieb Jim Fulton <***@jimfulton.info>:
[…]
I've added appveyor tests for ZODB: https://ci.appveyor.com/project/jimfulton/zodb/build/1.0.27
Jim, is this your private AppVeyor account? Is there a common Zope foundation account, too?
[1] winbot / z3c.contents_py_270_win32
[2] winbot / z3c.contents_py_270_win64
[3] winbot / z3c.jsonrpc_py_270_win32
[4] winbot / z3c.jsonrpc_py_270_win64
[5] winbot / z3c.ptcompat_py_270_win64
[6] winbot / z3c.testing_py_270_win32
[7] winbot / zc.catalog_py_270_win64
[8] winbot / zc.resourcelibrary_py_270_win32
[16] winbot / zope.index_py_270_win32
Although these ones do not seem to be too widely used (especially on Windows) they could be ported to AppVeyor, too.
[9] winbot / zope.app.applicationcontrol_py_270_win32
[10] winbot / zope.app.authentication_py_270_win32
[11] winbot / zope.app.authentication_py_270_win64
[12] winbot / zope.app.component_py_270_win32
[13] winbot / zope.app.component_py_270_win64
[14] winbot / zope.app.testing_py_270_win32
[15] winbot / zope.app.testing_py_270_win64
IMHO these ones are deprecated, so they can be dropped altogether.
[17] winbot / ztk_dev py_270_win32
[18] winbot / ztk_dev py_270_win64
[19] winbot / ztk_dev py_330_win32
[20] winbot / ztk_dev py_330_win64
It would be nice to have these ones on AppVeyor, too.


--
Mit freundlichen Grüßen
Michael Howitz
_______________________________________________
Zope-Dev maillist - Zope-***@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-a
Jim Fulton
2017-04-11 12:50:58 UTC
Permalink
Post by Jim Fulton
[
]
Post by Jim Fulton
I've added appveyor tests for ZODB: https://ci.appveyor.com/
project/jimfulton/zodb/build/1.0.27
Jim, is this your private AppVeyor account?
Yes.
Post by Jim Fulton
Is there a common Zope foundation account, too?
I have no idea. IDK if there's a way to set up group accounts.

persistent is tested with appveyor. IDK how that was set up.
Post by Jim Fulton
Post by Jim Fulton
[1] winbot / z3c.contents_py_270_win32
[2] winbot / z3c.contents_py_270_win64
[3] winbot / z3c.jsonrpc_py_270_win32
[4] winbot / z3c.jsonrpc_py_270_win64
[5] winbot / z3c.ptcompat_py_270_win64
[6] winbot / z3c.testing_py_270_win32
[7] winbot / zc.catalog_py_270_win64
[8] winbot / zc.resourcelibrary_py_270_win32
[16] winbot / zope.index_py_270_win32
Although these ones do not seem to be too widely used (especially on
Windows) they could be ported to AppVeyor, too.
I would hope they all could be, if anyone cares. If not, why are we
spamming people here? :)
Post by Jim Fulton
Post by Jim Fulton
[9] winbot / zope.app.applicationcontrol_py_270_win32
[10] winbot / zope.app.authentication_py_270_win32
[11] winbot / zope.app.authentication_py_270_win64
[12] winbot / zope.app.component_py_270_win32
[13] winbot / zope.app.component_py_270_win64
[14] winbot / zope.app.testing_py_270_win32
[15] winbot / zope.app.testing_py_270_win64
IMHO these ones are deprecated, so they can be dropped altogether.
Cool. Adam?
Post by Jim Fulton
Post by Jim Fulton
[17] winbot / ztk_dev py_270_win32
[18] winbot / ztk_dev py_270_win64
[19] winbot / ztk_dev py_330_win32
[20] winbot / ztk_dev py_330_win64
It would be nice to have these ones on AppVeyor, too.
And the six that are passing too.

Jim
--
Jim Fulton
http://jimfulton.info
Marius Gedminas
2017-04-11 14:21:29 UTC
Permalink
Post by Jim Fulton
[…]
I've added appveyor tests for ZODB: [3]https://ci.appveyor.com/project/
jimfulton/zodb/build/1.0.27
Jim, is this your private AppVeyor account?
Yes.
 
Is there a common Zope foundation account, too?
I have no idea. IDK if there's a way to set up group accounts.
AFAIK there isn't one currently.
Post by Jim Fulton
persistent is tested with appveyor. IDK how that was set up.
A bunch of ZopeFoundation repos are currently set up with my personal
AppVeyor account. I'm not very happy about it (I don't want to be a
bottleneck), and would prefer a shared Zope Foundation account.

(I like the way Travis CI links things to the GitHub owner organisation,
and uses GitHub logins to grant access. I wish AppVeyor could do that
too, but AFAIK it can't.)

Marius Gedminas
--
<AdamV> SamB: PHP's basic control structure is the "database
timeout error". -- from Twisted.Quotes
Michael Howitz
2017-04-13 06:16:29 UTC
Permalink
Am 11.04.2017 um 14:50 schrieb Jim Fulton <***@jimfulton.info>:
[…]
Post by Jim Fulton
Post by Michael Howitz
It would be nice to have these ones on AppVeyor, too.
And the six that are passing too.
According to http://winbot.zope.org/builders there are many more builders which currently succeed.
I didn’t even know that so many packages are tested using buildbot.

It would cost a huge effort to migrate all of them (or at least the not deprecated ones) to AppVeyor.
Maybe it would be easier to have a Zopefoundation AppVeyor account and create a build there if someone has a Windows only problem with a package or works on a package which contains C code.
This would allow to disable the buildbot and have a strategy for upcoming Windows problems.

What do you think?
--
Mit freundlichen Grüßen
Michael Howitz

_______________________________________________
Zope-Dev maillist - Zope-***@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
Jim Fulton
2017-04-13 13:06:48 UTC
Permalink
Post by Michael Howitz
[
]
Post by Jim Fulton
Post by Michael Howitz
It would be nice to have these ones on AppVeyor, too.
And the six that are passing too.
According to http://winbot.zope.org/builders there are many more builders
which currently succeed.
I didn’t even know that so many packages are tested using buildbot.
It would cost a huge effort to migrate all of them (or at least the not
deprecated ones) to AppVeyor.
Maybe it would be easier to have a Zopefoundation AppVeyor account and
create a build there if someone has a Windows only problem with a package
or works on a package which contains C code.
This would allow to disable the buildbot and have a strategy for upcoming Windows problems.
What do you think?
I think we should leave them be for now. I don't think we should be
seeking chores. I regret my comment about the "six". :) In my defence, I
said "it would be nice" as opposed to "we must". I also endorse dropping
tests for obsolete or unimportant packages with failing tests.

I don't think anyone has paid much attention to these emails, given how
long they've gone without change. For the most part they're just spam.

Also, the fact that it's so hard to change the buildbot config (I tried and
failed for ZODB), means that if anyone actually cared about a project, they
would probably move it to appveyor. (Something that Travis and Appveyor
seem to get is that people who use CI often don't give a pit about CI, they
just want their software to work. Looking at a Jenkins screen makes me
want to stop writing software.)

Having written the above ... IMO, we should give up on buildot, or at least
the automated emails. IDK if any Zope projects find it useful. Clearly the
ones whose tests have been failing forever don't. (As someone pointed out,
many of these are obsolete.) I would leave it up to people who care about
packages to convert them, or to pay attention to buildbot.

I *greatly* appreciate the efforts of Adam and whoever else worked on
buildbot and generosity of the PSF (or was it rackspace) in providing
resources. It's just not clear to me that it's providing benefit. <shrug>

If there's a way to create group accounts for Travis and Appveyor, I'd
wildly support using that. I set up Appveyor for ZODB out of desperation
(and because I was making a change that was likely to provoke issues on
Windows).

Jim
--
Jim Fulton
http://jimfulton.info
Loading...