On Fri, Mar 22, 2013 at 01:00:02AM +, Zope tests summarizer wrote:
[1]Still Failing - zopetoolkit_trunk - Build # 209
[2]winbot / z3c.contents_py_265_32
[3]winbot / z3c.form_py_265_32
Same as yesterday: three failures I can't reproduce.
Marius Gedminas
--
http://pov.lt/ --
Hi,
Stephan, may I kindly request a few more package migrations to github?
Here's the list:
groktoolkit
grokcore.errorview
grokcore.permission
grokcore.registries
grokcore.resource
grokui.admin
hurry.query
hurry.workflow
z3c.bcrypt
zc.relation
zc.relationship
zopetoolkit
Thank you *very much*
On Friday, March 22, 2013 10:23:21 AM Jan-Wijbrand Kolman wrote:
zopetoolkit
Is everyone ok with me moving this? Hanno mentioned that several external
tools depend on the SVN location and the move was delayed because of that. I
think this package also does not have the traditional tags,
On 3/22/13 12:59 PM, Stephan Richter wrote:
On Friday, March 22, 2013 10:23:21 AM Jan-Wijbrand Kolman wrote:
zopetoolkit
Is everyone ok with me moving this? Hanno mentioned that several external
tools depend on the SVN location and the move was delayed because of that. I
think this package
On Fri, Mar 22, 2013 at 10:23 AM, Jan-Wijbrand Kolman
janwijbr...@gmail.com wrote:
Here's the list:
groktoolkit
grokcore.errorview
grokcore.permission
grokcore.registries
grokcore.resource
grokui.admin
hurry.query
hurry.workflow
z3c.bcrypt
Don't understand why Grok packages (or 3rd
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/22/2013 08:13 AM, Sebastien Douche wrote:
On Fri, Mar 22, 2013 at 10:23 AM, Jan-Wijbrand Kolman
janwijbr...@gmail.com wrote:
Here's the list:
groktoolkit grokcore.errorview grokcore.permission
grokcore.registries grokcore.resource
This is the summary for test reports received on the
zope-tests list between 2013-03-21 00:00:00 UTC and 2013-03-22 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:
