zope-tests - FAILED: 21, OK: 19
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/zopetoolkit/process/buildbots.html#the-nightly-builds Reports received ---------------- Zope-2.10 Python-2.4.6 : Linux Zope-2.11 Python-2.4.6 : Linux Zope-2.12 Python-2.6.8 : Linux Zope-2.13 Python-2.6.8 : Linux Zope-2.13 Python-2.7.3 : Linux Zope-trunk Python-2.6.8 : Linux Zope-trunk Python-2.7.3 : Linux winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 [1] winbot / z3c.contents_py_265_32 [2] winbot / z3c.coverage_py_265_32 [3] winbot / z3c.coverage_py_265_32 [4] winbot / z3c.coverage_py_265_32 [5] winbot / z3c.datagenerator_py_265_32 [6] winbot / z3c.layer.pagelet_py_265_32 [7] winbot / z3c.layer.ready2go_py_265_32 [8] winbot / z3c.menu.ready2go_py_265_32 [9] winbot / z3c.recipe.paster_py_265_32 [10] winbot / zc_buildout_dev py_254_win32 1.6.x [11] winbot / zc_buildout_dev py_265_win32 1.6.x [12] winbot / zc_buildout_dev py_265_win32 master [13] winbot / zc_buildout_dev py_265_win64 1.6.x [14] winbot / zc_buildout_dev py_265_win64 master [15] winbot / zc_buildout_dev py_270_win32 1.6.x [16] winbot / zc_buildout_dev py_270_win32 master [17] winbot / zc_buildout_dev py_270_win64 1.6.x [18] winbot / zc_buildout_dev py_270_win64 master [19] winbot / zc_buildout_dev py_323_win32 master [20] winbot / zc_buildout_dev py_323_win64 master [21] winbot / zope.testbrowser_py_265_32 winbot / ztk_10 py_254_win32 winbot / ztk_10 py_265_win32 winbot / ztk_10 py_265_win64 winbot / ztk_11 py_254_win32 winbot / ztk_11 py_265_win32 winbot / ztk_11 py_265_win64 winbot / ztk_11 py_270_win32 winbot / ztk_11 py_270_win64 Non-OK results -------------- [1] FAILED winbot / z3c.contents_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-September/067641.html [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-tests/2012-September/067651.html [4] FAILED winbot / z3c.coverage_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-September/067639.html [5] FAILED winbot / z3c.datagenerator_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-September/067640.html [6] FAILED winbot / z3c.layer.pagelet_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-September/067636.html [7] FAILED winbot / z3c.layer.ready2go_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-September/067637.html [8] FAILED winbot / z3c.menu.ready2go_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-September/067638.html [9] FAILED winbot / z3c.recipe.paster_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-September/067643.html [10] FAILED winbot / zc_buildout_dev py_254_win32 1.6.x https://mail.zope.org/pipermail/zope-tests/2012-September/067667.html [11] FAILED winbot / zc_buildout_dev py_265_win32 1.6.x https://mail.zope.org/pipermail/zope-tests/2012-September/067668.html [12] FAILED winbot / zc_buildout_dev py_265_win32 master https://mail.zope.org/pipermail/zope-tests/2012-September/067661.html [13] FAILED winbot / zc_buildout_dev py_265_win64 1.6.x https://mail.zope.org/pipermail/zope-tests/2012-September/067669.html [14] FAILED winbot / zc_buildout_dev py_265_win64 master https://mail.zope.org/pipermail/zope-tests/2012-September/067662.html [15] FAILED winbot / zc_buildout_dev py_270_win32 1.6.x https://mail.zope.org/pipermail/zope-tests/2012-September/067670.html [16] FAILED winbot / zc_buildout_dev py_270_win32 master https://mail.zope.org/pipermail/zope-tests/2012-September/067663.html [17] FAILED winbot / zc_buildout_dev py_270_win64 1.6.x https://mail.zope.org/pipermail/zope-tests/2012-September/067671.html [18] FAILED winbot / zc_buildout_dev py_270_win64 master https://mail.zope.org/pipermail/zope-tests/2012-September/067664.html [19] FAILED winbot / zc_buildout_dev py_323_win32 master https://mail.zope.org/pipermail/zope-tests/2012-September/067665.html [20] FAILED winbot / zc_buildout_dev py_323_win64 master https://mail.zope.org/pipermail/zope-tests/2012-September/067666.html [21] FAILED winbot / zope.testbrowser_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-September/067642.html
On Thu, Sep 06, 2012 at 01:00:01AM +0000, 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-tests/2012-September/067651.html
[4] FAILED winbot / z3c.coverage_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-September/067639.html
Mea culpa. How do you redirect the stderr of a process spawned with suprocess.Popen(shell=False) to /dev/null in a cross-platform manner? Marius Gedminas -- Sufficiently advanced incompetence is indistinguishable from malice. -- David Sawford
On 09/06/2012 10:58 AM, Marius Gedminas wrote:
On Thu, Sep 06, 2012 at 01:00:01AM +0000, 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-tests/2012-September/067651.html
[4] FAILED winbot / z3c.coverage_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-September/067639.html Mea culpa.
How do you redirect the stderr of a process spawned with suprocess.Popen(shell=False) to /dev/null in a cross-platform manner?
Use NUL if you are running on Windows. You'll need to test the OS yourself - there is no cross-platform method as far as I know. Wichert.
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 stefan@epy.co.at
-----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 perhaps? Or rather, what about subprocess.Popen(cmd, stderr=subprocess.PIPE)?
subprocess.PIPE is no good -- it sets up stderr to be read from the parent process. If enough stuff gets written without the parent reading, the child will block. Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlBKLooACgkQ+gerLs4ltQ4SzQCeKdcaC5s0Xae3ByPh84n2fZPw /qMAnA6uzro7BFFLxoq7+zfXi499rib4 =XlCf -----END PGP SIGNATURE-----
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 manner?
os.devnull perhaps? Or rather, what about subprocess.Popen(cmd, stderr=subprocess.PIPE)?
os.devnull was what I was looking for. subprocess.Popen(stderr=subprocess.PIPE) was what I went with when I didn't find os.devnull in time.
subprocess.PIPE is no good -- it sets up stderr to be read from the parent process. If enough stuff gets written without the parent reading, the child will block.
I believe subprocess.Popen.communicate() takes care of that. Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development
participants (5)
-
Marius Gedminas -
Stefan H. Holek -
Tres Seaver -
Wichert Akkerman -
Zope tests summarizer