Re: [Zope-dev] zope-tests - FAILED: 16, OK: 12

2013-03-05 Thread Marius Gedminas
On Wed, Mar 06, 2013 at 01:00:01AM +, Zope tests summarizer wrote: > This is the summary for test reports received on the > zope-tests list between 2013-03-04 00:00:00 UTC and 2013-03-05 00:00:00 UTC: Nothing new, everything same as last time. Marius Gedminas -- http://pov.lt/ -- Zope 3/Blu

[Zope-dev] zope-tests - FAILED: 16, OK: 12

2013-03-05 Thread Zope tests summarizer
This is the summary for test reports received on the zope-tests list between 2013-03-04 00:00:00 UTC and 2013-03-05 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/

Re: [Zope-dev] Switching zope.testbrowser to webtest instead of mechanize

2013-03-05 Thread Brian Sutherland
On Tue, Mar 05, 2013 at 06:49:35PM +0200, Andrey Lebedev wrote: > On 03/05/2013 06:45 PM, Brian Sutherland wrote: > >One thing which I'm not sure you can do with a webtest backend is using > >it as a real browser. i.e. you'll probably not get over_the_wire.txt to > >pass. However, I don't know of a

Re: [Zope-dev] Switching zope.testbrowser to webtest instead of mechanize

2013-03-05 Thread Andrey Lebedev
On 03/05/2013 06:45 PM, Brian Sutherland wrote: One thing which I'm not sure you can do with a webtest backend is using it as a real browser. i.e. you'll probably not get over_the_wire.txt to pass. However, I don't know of anyone who actually uses that functionality. Hm, webtest claims it can d

Re: [Zope-dev] Switching zope.testbrowser to webtest instead of mechanize

2013-03-05 Thread Brian Sutherland
On Tue, Mar 05, 2013 at 05:56:54PM +0200, Andrey Lebedev wrote: > On 03/05/2013 05:10 PM, Brian Sutherland wrote: > >>So far, it seems webtest has all the features needed to do the > >>>switch. I started a branch at github ([2]) to track work in > >>>progress. The goal is to make most (say 80%) of

Re: [Zope-dev] GitHub and Travis CI

2013-03-05 Thread Godefroid Chapelle
Le 04/03/13 20:00, Stephan Richter a écrit : Hi everyone, I have invested some time today to implement the Travis CI hook setup for GitHub. I can now turn on and update Travis CI for any package. See the ``README.rst`` file. I did the same in z3c.taskqueue and five.taskqueue that Stephan ve

Re: [Zope-dev] Switching zope.testbrowser to webtest instead of mechanize

2013-03-05 Thread Andrey Lebedev
On 03/05/2013 05:10 PM, Brian Sutherland wrote: So far, it seems webtest has all the features needed to do the >switch. I started a branch at github ([2]) to track work in >progress. The goal is to make most (say 80%) of existing tests to >work without modifications under new implementation. L

Re: [Zope-dev] Switching zope.testbrowser to webtest instead of mechanize

2013-03-05 Thread Brian Sutherland
On Mon, Mar 04, 2013 at 08:40:23PM +0200, Andrey Lebedev wrote: > Hello zope-dev, > > As you may already know, there is an effort to port zope packages to > Python 3 going on. As part of this effort we want to port > zope.testbrowser. Great! I'm very interested in this, I've also got an app which

Re: [Zope-dev] GitHub and Travis CI

2013-03-05 Thread Stephan Richter
On Tuesday, March 05, 2013 10:27:24 AM Albertas Agejevas wrote: > > So my question is: What do we want to do? I would suggest E-mails on > > status change should be sufficient. > > It would be cool to have a single page with such status icons for all > packages we care about. So once "zopetoolki

Re: [Zope-dev] GitHub and Travis CI

2013-03-05 Thread Albertas Agejevas
On Mon, Mar 04, 2013 at 02:00:22PM -0500, Stephan Richter wrote: > In addition, Marius added this to his sample project: > > https://github.com/zopefoundation/zope.dottedname > > See the ``README.rst`` file. > > So my question is: What do we want to do? I would suggest E-mails on status > chang