On Tue, Oct 15, 2013 at 01:00:02AM +0200, Zope tests summarizer wrote:
[1]FAILED Failure - zopetoolkit_trunk - Build # 427
https://mail.zope.org/pipermail/zope-tests/2013-October/079244.html
Network timeout while trying to connect and fetch
This is the summary for test reports received on the
zope-tests list between 2013-10-13 00:00:00 UTC and 2013-10-14 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:
This is the summary for test reports received on the
zope-tests list between 2013-10-12 00:00:00 UTC and 2013-10-13 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:
On Sat, Oct 12, 2013 at 01:00:02AM +0200, Zope tests summarizer wrote:
[1]FAILED winbot / zope.app.wsgi_py_265_32
https://mail.zope.org/pipermail/zope-tests/2013-October/079204.html
The usual 24-hour winbot lag. Last build was successful.
Marius Gedminas
--
http://pov.lt/ -- Zope
On Thu, Oct 10, 2013 at 02:19:21PM +0300, Marius Gedminas wrote:
On Thu, Oct 10, 2013 at 01:00:02AM +0200, Zope tests summarizer wrote:
[1]FAILED winbot / zope.app.wsgi_py_265_32
https://mail.zope.org/pipermail/zope-tests/2013-October/079170.html
I haven't found the round tuits
Hi!
Where can I report problems with svn.zope.org?
For some days now I have trouble making checkins. Commits are
successful, but somewhere in the post commit hook things go wrong. No
mail is send to the checkins list and my svn client freezes - I guess
because the server doesn't signal the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/11/2013 08:21 AM, yuppie wrote:
Hi!
Where can I report problems with svn.zope.org?
For some days now I have trouble making checkins. Commits are
successful, but somewhere in the post commit hook things go wrong. No
mail is send to
This is the summary for test reports received on the
zope-tests list between 2013-10-10 00:00:00 UTC and 2013-10-11 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:
On Thu, Oct 10, 2013 at 01:00:02AM +0200, Zope tests summarizer wrote:
[1]FAILED winbot / zope.app.wsgi_py_265_32
https://mail.zope.org/pipermail/zope-tests/2013-October/079170.html
I haven't found the round tuits to fix this yet.
I still plan on doing that, whenever I can find the
This is the summary for test reports received on the
zope-tests list between 2013-10-09 00:00:00 UTC and 2013-10-10 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:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/08/2013 07:00 PM, Zope tests summarizer wrote:
[1]FAILED winbot / z3c.tabular_py_265_32
https://mail.zope.org/pipermail/zope-tests/2013-October/079153.html
Transient github failure:
fatal: unable to connect to github.com:
This is the summary for test reports received on the
zope-tests list between 2013-10-08 00:00:00 UTC and 2013-10-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:
This is the summary for test reports received on the
zope-tests list between 2013-10-06 00:00:00 UTC and 2013-10-07 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:
This is the summary for test reports received on the
zope-tests list between 2013-10-05 00:00:00 UTC and 2013-10-06 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:
This is the summary for test reports received on the
zope-tests list between 2013-10-04 00:00:00 UTC and 2013-10-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:
This is the summary for test reports received on the
zope-tests list between 2013-10-03 00:00:00 UTC and 2013-10-04 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:
This is the summary for test reports received on the
zope-tests list between 2013-10-02 00:00:00 UTC and 2013-10-03 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:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/01/2013 07:00 PM, Zope tests summarizer wrote:
[1]FAILED winbot / zope.app.wsgi_py_265_32
https://mail.zope.org/pipermail/zope-tests/2013-October/079033.html
Failure in buildout phase::
Develop:
This is the summary for test reports received on the
zope-tests list between 2013-10-01 00:00:00 UTC and 2013-10-02 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:
On 9/18/13 4:41 PM, Jan-Wijbrand Kolman wrote:
I've been working on CSRF protection for zope.formlib.
Anyone else interested in this feature?
We made an internal release of zope.formlib with this functionality and
so far we found no issues in using it in production.
After updating
This is the summary for test reports received on the
zope-tests list between 2013-09-30 00:00:00 UTC and 2013-10-01 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:
This is the summary for test reports received on the
zope-tests list between 2013-09-29 00:00:00 UTC and 2013-09-30 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:
This is the summary for test reports received on the
zope-tests list between 2013-09-28 00:00:00 UTC and 2013-09-29 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:
This is the summary for test reports received on the
zope-tests list between 2013-09-27 00:00:00 UTC and 2013-09-28 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:
On Fri, Sep 27, 2013 at 01:00:01AM +0200, Zope tests summarizer wrote:
[1]FAILED winbot / zc.ngi_py_265_32
https://mail.zope.org/pipermail/zope-tests/2013-September/078948.html
Intermittent error. An interesting one:
This is the summary for test reports received on the
zope-tests list between 2013-09-26 00:00:00 UTC and 2013-09-27 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:
This is the summary for test reports received on the
zope-tests list between 2013-09-25 00:00:00 UTC and 2013-09-26 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:
On Wed, Sep 25, 2013 at 01:00:01AM +0200, Zope tests summarizer wrote:
[1]FAILED winbot / zope.app.wsgi_py_265_32
https://mail.zope.org/pipermail/zope-tests/2013-September/078913.html
Ah, the webtest version conflict is back.
Marius Gedminas
--
http://pov.lt/ -- Zope 3/BlueBream
This is the summary for test reports received on the
zope-tests list between 2013-09-24 00:00:00 UTC and 2013-09-25 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:
On Tue, Sep 24, 2013 at 01:00:01AM +0200, Zope tests summarizer wrote:
[1]FAILED winbot / ztk_11 py_270_win32
https://mail.zope.org/pipermail/zope-tests/2013-September/078904.html
File
c:\eggs\zope.testrunner-4.0.4-py2.7.egg\zope\testrunner\testrunner-layers-buff.txt,
line 100, in
This is the summary for test reports received on the
zope-tests list between 2013-09-23 00:00:00 UTC and 2013-09-24 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:
On Fri, Sep 13, 2013 at 09:01:37AM +0300, Marius Gedminas wrote:
On Fri, Sep 13, 2013 at 01:00:02AM +0200, Zope tests summarizer wrote:
[2]winbot / zope.app.authentication_py_265_32
[3]winbot / zope.app.http_py_265_32
[4]winbot / zope.app.publication_py_265_32
[8]winbot /
On 09/23/2013 10:03 AM, Marius Gedminas wrote:
On Fri, Sep 13, 2013 at 09:01:37AM +0300, Marius Gedminas wrote:
On Fri, Sep 13, 2013 at 01:00:02AM +0200, Zope tests summarizer wrote:
[2]winbot / zope.app.authentication_py_265_32
[3]winbot / zope.app.http_py_265_32
[4]winbot /
This is the summary for test reports received on the
zope-tests list between 2013-09-22 00:00:00 UTC and 2013-09-23 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:
Hi,
Can someone please migrate z3c.formwidget.query to github?
This package is a dependency of plone.formwidget.autocomplete and I need to
make a fix.
This is broken since z3c.form = 2.6.0 which remove :list suffix from
radiobox.
See the attached patch.
Vincent Fretin
Ecreall
I thought the zope svn was read-only, but I actually succeeded to do the
commit.
Can someone please make a new release? Thanks.
Vincent
On Sun, Sep 22, 2013 at 5:22 PM, Vincent Fretin vincent.fre...@gmail.comwrote:
Hi,
Can someone please migrate z3c.formwidget.query to github?
This package
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/22/2013 11:27 AM, Vincent Fretin wrote:
Can someone please make a new release?
Releases can be made only by one of:
malthe, optilude, davisagli, laurencerowe, timo, esteele
- --
This is the summary for test reports received on the
zope-tests list between 2013-09-21 00:00:00 UTC and 2013-09-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:
On Sat, Sep 21, 2013 at 01:00:02AM +0200, Zope tests summarizer wrote:
[1]winbot / zope.testbrowser_py_265_32
Last build was successful.
Marius Gedminas
--
http://pov.lt/ -- Zope 3/BlueBream consulting and development
signature.asc
Description: Digital signature
This is the summary for test reports received on the
zope-tests list between 2013-09-20 00:00:00 UTC and 2013-09-21 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:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/21/2013 07:00 PM, Zope tests summarizer wrote:
This is the summary for test reports received on the zope-tests list
between 2013-09-20 00:00:00 UTC and 2013-09-21 00:00:00 UTC:
See the footnotes for test reports of unsuccessful builds.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/18/2013 06:40 AM, Marius Gedminas wrote:
On Wed, Sep 18, 2013 at 11:11:50AM +0300, Marius Gedminas wrote:
On Wed, Sep 18, 2013 at 01:00:02AM +0200, Zope tests summarizer
wrote:
[6]winbot / zope.testbrowser_py_265_32
The fix that was
On Fri, Sep 20, 2013 at 09:40:00AM -0400, Tres Seaver wrote:
On 09/18/2013 06:40 AM, Marius Gedminas wrote:
On Wed, Sep 18, 2013 at 11:11:50AM +0300, Marius Gedminas wrote:
On Wed, Sep 18, 2013 at 01:00:02AM +0200, Zope tests summarizer
wrote:
[6]winbot / zope.testbrowser_py_265_32
This is the summary for test reports received on the
zope-tests list between 2013-09-19 00:00:00 UTC and 2013-09-20 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:
Op 17-09-13 17:15, Marius Gedminas schreef:
On Tue, Sep 17, 2013 at 09:35:58AM -0400, Jim Fulton wrote:
On Tue, Sep 17, 2013 at 8:58 AM, Marius Gedminas mar...@gedmin.as wrote:
FWIW the only reason I'm in favour of self-merges is that this
short-circuits the have you signed the ZF committer
This is the summary for test reports received on the
zope-tests list between 2013-09-18 00:00:00 UTC and 2013-09-19 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:
On Wed, Sep 18, 2013 at 01:00:02AM +0200, Zope tests summarizer wrote:
[1]winbot / ZODB_dev py_265_win64
Non-deterministic test failure:
Failure in test
c:\buildslave\zodb_dev_py_265_win64\build\src\ZODB\historical_connections.txt
On Wed, Sep 18, 2013 at 11:11:50AM +0300, Marius Gedminas wrote:
On Wed, Sep 18, 2013 at 01:00:02AM +0200, Zope tests summarizer wrote:
[6]winbot / zope.testbrowser_py_265_32
The fix that was supposed to fix this didn't because
https://github.com/Pylons/webtest/pull/87/files#r6427276
Hi,
I've been working on CSRF protection for zope.formlib.
I have a csrfprotection branch in my zope.formlib fork on github. The
changes against the current zope.formlib mainline can be found here:
https://github.com/janwijbrand/zope.formlib/compare/csrfprotection
When creating form
Hi Jan-Wij,
+1 for implementing convenient CSRF.
I wonder if you could make your implementation more orthogonal by
implementing a CSRF field/widget, and make your `protected` attribute
simply trigger the inclusion of this field implicitly.
This way you wouldn't need to change the `*pageform.pt`
On 9/18/13 5:26 PM, Leonardo Rochael Almeida wrote:
+1 for implementing convenient CSRF.
I wonder if you could make your implementation more orthogonal by
implementing a CSRF field/widget, and make your `protected` attribute
simply trigger the inclusion of this field implicitly.
This way you
This is the summary for test reports received on the
zope-tests list between 2013-09-17 00:00:00 UTC and 2013-09-18 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:
Hi,
I wonder if there is a formal or informal write-up of how to nicely
contribute code to the repositories under the zopefoundation umbrella.
Back in the subversion days I would branch a project, amend code, write
tests, commit this to the repository, ask for feedback on the list, and,
On Tue, Sep 17, 2013 at 12:04:04PM +0200, Jan-Wijbrand Kolman wrote:
I wonder if there is a formal or informal write-up of how to
nicely contribute code to the repositories under the
zopefoundation umbrella.
I don't think so. I'd like to see one.
Back in the subversion days I would branch a
On 9/17/13 12:04 PM, Jan-Wijbrand Kolman wrote:
snip
2) fork the repository, make a branch in the fork, do my work, push the
changes to my fork, and issue a pull request.
The latter is what I did, without explicitly asking for feedback.
Luckily someone did give me feedback (thanks!) :-)
Now
On 9/17/13 1:00 PM, Marius Gedminas wrote:
On Tue, Sep 17, 2013 at 12:04:04PM +0200, Jan-Wijbrand Kolman wrote:
I wonder if there is a formal or informal write-up of how to
nicely contribute code to the repositories under the
zopefoundation umbrella.
I don't think so. I'd like to see one.
On Tue, Sep 17, 2013 at 7:00 AM, Marius Gedminas mar...@gedmin.as wrote:
...
2) fork the repository, make a branch in the fork, do my work, push
the changes to my fork, and issue a pull request.
The latter is what I did, without explicitly asking for feedback.
Luckily someone did give me
On 9/17/13 1:47 PM, Jim Fulton wrote:
I strongly prefer that the reviewer do the merge.
I'd also really like reviewers to take their responsibility
seriously, making comments and suggestions where appropriate.
Software review, done well, improves the software, and, more
importantly, improves
On Tue, Sep 17, 2013 at 07:47:42AM -0400, Jim Fulton wrote:
On Tue, Sep 17, 2013 at 7:00 AM, Marius Gedminas mar...@gedmin.as wrote:
Now that I mended the pull request, should I merge the pull request
myself? Or is the current etiquette that someone else should merge
the pull request?
I
On Tue, Sep 17, 2013 at 8:32 AM, Jan-Wijbrand Kolman
janwijbr...@gmail.com wrote:
On 9/17/13 1:47 PM, Jim Fulton wrote:
I strongly prefer that the reviewer do the merge.
I'd also really like reviewers to take their responsibility
seriously, making comments and suggestions where appropriate.
On Tue, Sep 17, 2013 at 8:58 AM, Marius Gedminas mar...@gedmin.as wrote:
On Tue, Sep 17, 2013 at 07:47:42AM -0400, Jim Fulton wrote:
On Tue, Sep 17, 2013 at 7:00 AM, Marius Gedminas mar...@gedmin.as wrote:
Now that I mended the pull request, should I merge the pull request
myself? Or is the
On 9/17/13 3:32 PM, Jim Fulton wrote:
On Tue, Sep 17, 2013 at 8:32 AM, Jan-Wijbrand Kolman
Is this reviewer role something someone takes upon himself? I mean, if I
see a pull request for a code base that I know, I could review the request?
These are good questions. I probably don't have
Certain Subversion commits show up on the checkins@ list misattributed
to Marius Gedminas cvs-ad...@zope.org. Examples:
r130062 - https://mail.zope.org/pipermail/checkins/2013-March/065903.html
r130296 - https://mail.zope.org/pipermail/checkins/2013-August/067498.html
r130309 -
On Tue, Sep 17, 2013 at 09:35:58AM -0400, Jim Fulton wrote:
On Tue, Sep 17, 2013 at 8:58 AM, Marius Gedminas mar...@gedmin.as wrote:
FWIW the only reason I'm in favour of self-merges is that this
short-circuits the have you signed the ZF committer agreement? dance.
Only people who have can
This is the summary for test reports received on the
zope-tests list between 2013-09-16 00:00:00 UTC and 2013-09-17 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:
On Mon, Sep 16, 2013 at 01:00:01AM +0200, Zope tests summarizer wrote:
[1]winbot / zope.app.authentication_py_265_32
[2]winbot / zope.app.http_py_265_32
[3]winbot / zope.app.publication_py_265_32
[4]winbot / zope.app.wsgi_py_265_32
WebTest version conflict
[5]winbot /
On Mon, Sep 16, 2013 at 01:50:32PM +0300, Marius Gedminas wrote:
On Mon, Sep 16, 2013 at 01:00:01AM +0200, Zope tests summarizer wrote:
[5]winbot / zope.testbrowser_py_265_32
Interesting new error:
...
At first I suspected Windows line endings, but look closer:
- Content-type:
On Sat, Sep 14, 2013, at 0:38, Baiju M wrote:
Is there any roadmap release plan for Zope 4.0 ?
I'm not aware on anyone still working on Zope 4. The project might come
back to life at some point, but for the past couple of months it's been
very quiet.
At my work, we use Zope 2.12 and we are
This is the summary for test reports received on the
zope-tests list between 2013-09-15 00:00:00 UTC and 2013-09-16 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:
On Sun, Sep 15, 2013 at 01:00:01AM +0200, Zope tests summarizer wrote:
[1]winbot / zope.app.authentication_py_265_32
[2]winbot / zope.app.http_py_265_32
[3]winbot / zope.app.publication_py_265_32
[4]winbot / zope.app.wsgi_py_265_32
WebTest version conflict
[5]winbot /
This is the summary for test reports received on the
zope-tests list between 2013-09-14 00:00:00 UTC and 2013-09-15 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:
This is the summary for test reports received on the
zope-tests list between 2013-09-13 00:00:00 UTC and 2013-09-14 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:
On Fri, Sep 13, 2013 at 01:00:02AM +0200, Zope tests summarizer wrote:
[1]winbot / z3c.ptcompat_py_265_32
[5]winbot / zope.app.publisher_py_265_32
[6]winbot / zope.app.security_py_265_32
[7]winbot / zope.app.session_py_265_32
[9]winbot / zope.catalog_py_265_32
[10]
Hi,
Is there any roadmap release plan for Zope 4.0 ?
At my work, we use Zope 2.12 and we are looking forward to upgrading to
Zope 2.13. Depending on Zope 4.0 availability, we can think about directly
moving to Zope 4.0
Regards,
Baiju M
___
Zope-Dev
This is the summary for test reports received on the
zope-tests list between 2013-09-12 00:00:00 UTC and 2013-09-13 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:
On Tue, Sep 10, 2013 at 09:49:50AM +0200, Brian Sutherland wrote:
On Tue, Sep 10, 2013 at 09:32:18AM +0300, Marius Gedminas wrote:
IIRC there's a brand new zope.testbrowser 4.1.0 with Python 3 support,
built on top of WebTest, waiting in the py3 branch for... Actually, I'm
not sure what it
On Tue, Sep 10, 2013 at 09:32:18AM +0300, Marius Gedminas wrote:
IIRC there's a brand new zope.testbrowser 4.1.0 with Python 3 support,
built on top of WebTest, waiting in the py3 branch for... Actually, I'm
not sure what it is waiting for. (I thought ZODB with Python 3 support,
but it
On Thursday, September 12, 2013 11:38:16 AM Marius Gedminas wrote:
m trying to merge the py3 branch to master now. There's one issue:
the test for https://github.com/zopefoundation/zope.testbrowser/pull/4
uses the internal .mech_browser attribute.
I think what is actually wanted here is a
This is the summary for test reports received on the
zope-tests list between 2013-09-11 00:00:00 UTC and 2013-09-12 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:
This is the summary for test reports received on the
zope-tests list between 2013-09-10 00:00:00 UTC and 2013-09-11 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:
On Mon, Sep 09, 2013 at 12:26:33PM -0400, Tres Seaver wrote:
On 09/09/2013 11:53 AM, Marius Gedminas wrote:
On Sat, Sep 07, 2013 at 08:27:04PM -0400, Tres Seaver wrote:
On 09/07/2013 07:00 PM, Zope tests summarizer wrote:
[1]FAILED winbot / zope.app.authentication_py_265_32
On Tue, Sep 10, 2013 at 09:32:18AM +0300, Marius Gedminas wrote:
On Mon, Sep 09, 2013 at 12:26:33PM -0400, Tres Seaver wrote:
On 09/09/2013 11:53 AM, Marius Gedminas wrote:
On Sat, Sep 07, 2013 at 08:27:04PM -0400, Tres Seaver wrote:
On 09/07/2013 07:00 PM, Zope tests summarizer wrote:
This is the summary for test reports received on the
zope-tests list between 2013-09-09 00:00:00 UTC and 2013-09-10 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:
On 09/09/2013 04:29 AM, Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/08/2013 07:00 PM, Zope tests summarizer wrote:
[1]FAILED winbot / zope.app.wsgi_py_265_32
https://mail.zope.org/pipermail/zope-tests/2013-September/078639.html
Same failure as yesterday::
On Sat, Sep 07, 2013 at 08:27:04PM -0400, Tres Seaver wrote:
On 09/07/2013 07:00 PM, Zope tests summarizer wrote:
[1]FAILED winbot / zope.app.authentication_py_265_32
https://mail.zope.org/pipermail/zope-tests/2013-September/078621.html
[2]FAILED winbot /
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/09/2013 11:53 AM, Marius Gedminas wrote:
On Sat, Sep 07, 2013 at 08:27:04PM -0400, Tres Seaver wrote:
On 09/07/2013 07:00 PM, Zope tests summarizer wrote:
[1]FAILED winbot / zope.app.authentication_py_265_32
This is the summary for test reports received on the
zope-tests list between 2013-09-08 00:00:00 UTC and 2013-09-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:
This is the summary for test reports received on the
zope-tests list between 2013-09-07 00:00:00 UTC and 2013-09-08 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:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/08/2013 07:00 PM, Zope tests summarizer wrote:
[1]FAILED winbot / zope.app.wsgi_py_265_32
https://mail.zope.org/pipermail/zope-tests/2013-September/078639.html
Same failure as yesterday::
Installing test.
While:
Installing
This is the summary for test reports received on the
zope-tests list between 2013-09-06 00:00:00 UTC and 2013-09-07 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:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/07/2013 07:00 PM, Zope tests summarizer wrote:
[1]FAILED winbot / zope.app.authentication_py_265_32
https://mail.zope.org/pipermail/zope-tests/2013-September/078621.html
[2]FAILED winbot / zope.app.http_py_265_32
This is the summary for test reports received on the
zope-tests list between 2013-09-05 00:00:00 UTC and 2013-09-06 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:
On 09/05/2013 02:58 AM, Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/04/2013 07:00 PM, Zope tests summarizer wrote:
[1]Failure - zopetoolkit_trunk - Build # 379 Fixed -
zopetoolkit_trunk - Build # 389 [2]Still Failing -
zopetoolkit_trunk - Build # 380 [3]
On Thu, Sep 05, 2013 at 08:53:54AM +0200, Adam GROSZER wrote:
On 09/05/2013 02:58 AM, Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/04/2013 07:00 PM, Zope tests summarizer wrote:
[1]Failure - zopetoolkit_trunk - Build # 379 Fixed -
zopetoolkit_trunk - Build #
I am messing with my chef setup. I didn't figure out how to do this on a
test environment yet.
Sorry for the noise.
On Thu, Sep 5, 2013 at 9:29 AM, Marius Gedminas mar...@gedmin.as wrote:
On Thu, Sep 05, 2013 at 08:53:54AM +0200, Adam GROSZER wrote:
On 09/05/2013 02:58 AM, Tres Seaver wrote:
This is the summary for test reports received on the
zope-tests list between 2013-09-03 00:00:00 UTC and 2013-09-04 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:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/04/2013 07:00 PM, Zope tests summarizer wrote:
[1]Failure - zopetoolkit_trunk - Build # 379 Fixed -
zopetoolkit_trunk - Build # 389 [2]Still Failing -
zopetoolkit_trunk - Build # 380 [3]Still Failing -
zopetoolkit_trunk - Build #
This is the summary for test reports received on the
zope-tests list between 2013-09-02 00:00:00 UTC and 2013-09-03 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:
This is the summary for test reports received on the
zope-tests list between 2013-09-01 00:00:00 UTC and 2013-09-02 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:
This is the summary for test reports received on the
zope-tests list between 2013-08-31 00:00:00 UTC and 2013-09-01 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:
1 - 100 of 34194 matches
Mail list logo
