On Tuesday, February 26, 2013 01:00:39 PM Tres Seaver wrote:
> > * ZODB 4.0.0 (I am currently using an sdist of the py3 branch.)
>
> AFAIK, the remaining test failures on Py33 are largely spurious (doctest
> repr issues, or else are pending the fork to use 'zodbpickle'.
So the state here is:
- W
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/26/2013 10:46 AM, Stephan Richter wrote:
> Even though, most ported packages are fully Python 3 compatible, they
> might depend on packages that are not ready to get a final release.
> Those two are:
>
> * zope.security 4.0.0 (pending PyPy suppo
On Tue, Feb 26, 2013 at 08:48:10AM -0500, Stephan Richter wrote:
> This brings up a bigger question:
>
> Even though, most ported packages are fully Python 3 compatible, they might
> depend on packages that are not ready to get a final release. Those two are:
>
> * zope.security 4.0.0 (pending P
On Tuesday, February 26, 2013 02:41:02 PM Marius Gedminas wrote:
> This error is caused by zope.publisher 4.0.0a1:
>
> bin/buildout -n buildout:prefer-final=false buildout:versions=versions \
>versions:zope.publisher='<4.0.0a1' \
>versions:zope.session='<4.0.0a1'
On Tue, Feb 26, 2013 at 02:41:02PM +0200, Marius Gedminas wrote:
> On Tue, Feb 26, 2013 at 08:54:01AM +0200, Marius Gedminas wrote:
> > > [5]winbot / z3c.contents_py_265_32
> > > [6]winbot / z3c.contents_py_265_32
> >
> > There's this lovely bit at the beginning I don't remember from befor
On Tue, Feb 26, 2013 at 08:54:01AM +0200, Marius Gedminas wrote:
> > [5]winbot / z3c.contents_py_265_32
> > [6]winbot / z3c.contents_py_265_32
>
> There's this lovely bit at the beginning I don't remember from before,
> but it's not counted as a test failure:
>
> ZopeXMLConfigurationError
On Tue, Feb 26, 2013 at 08:54:01AM +0200, Marius Gedminas wrote:
> On Tue, Feb 26, 2013 at 01:00:02AM +, Zope tests summarizer wrote:
> > [5]winbot / z3c.contents_py_265_32
> > [6]winbot / z3c.contents_py_265_32
>
> There's this lovely bit at the beginning I don't remember from before,
On Tue, Feb 26, 2013 at 01:00:02AM +, Zope tests summarizer wrote:
> This is the summary for test reports received on the
> zope-tests list between 2013-02-24 00:00:00 UTC and 2013-02-25 00:00:00 UTC:
>
> See the footnotes for test reports of unsuccessful builds.
>
> An up-to date view of th
This is the summary for test reports received on the
zope-tests list between 2013-02-24 00:00:00 UTC and 2013-02-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:
http://docs.zope.org/
On Fri, Sep 07, 2012 at 01:27:38PM -0400, Tres Seaver wrote:
> On 09/06/2012 03:08 PM, Stefan H. Holek wrote:
> > On 06.09.2012, at 10:58, Marius Gedminas wrote:
> >
> >> How do you redirect the stderr of a process spawned with
> >> suprocess.Popen(shell=False) to /dev/null in a cross-platform
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/06/2012 03:08 PM, Stefan H. Holek wrote:
> On 06.09.2012, at 10:58, Marius Gedminas wrote:
>
>> How do you redirect the stderr of a process spawned with
>> suprocess.Popen(shell=False) to /dev/null in a cross-platform
>> manner?
>
> os.devnull
On 06.09.2012, at 10:58, Marius Gedminas wrote:
> How do you redirect the stderr of a process spawned with
> suprocess.Popen(shell=False) to /dev/null in a cross-platform manner?
os.devnull perhaps? Or rather, what about subprocess.Popen(cmd,
stderr=subprocess.PIPE)?
Stefan
--
Stefan H. Holek
On 09/06/2012 10:58 AM, Marius Gedminas wrote:
On Thu, Sep 06, 2012 at 01:00:01AM +, Zope tests summarizer wrote:
[2]FAILED winbot / z3c.coverage_py_265_32
https://mail.zope.org/pipermail/zope-tests/2012-September/067652.html
[3]FAILED winbot / z3c.coverage_py_265_32
On Thu, Sep 06, 2012 at 01:00:01AM +, Zope tests summarizer wrote:
> [2]FAILED winbot / z3c.coverage_py_265_32
>https://mail.zope.org/pipermail/zope-tests/2012-September/067652.html
>
>
> [3]FAILED winbot / z3c.coverage_py_265_32
>https://mail.zope.org/pipermail/zope
This is the summary for test reports received on the
zope-tests list between 2012-09-04 00:00:00 UTC and 2012-09-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/
ZODB failures: that was me, playing with the buildbot
On 08/30/2012 03:00 AM, Zope tests summarizer wrote:
This is the summary for test reports received on the
zope-tests list between 2012-08-28 00:00:00 UTC and 2012-08-29 00:00:00 UTC:
See the footnotes for test reports of unsuccessful builds.
This is the summary for test reports received on the
zope-tests list between 2012-08-28 00:00:00 UTC and 2012-08-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:
http://docs.zope.org/
17 matches
Mail list logo
