zope-tests - FAILED: 3, OK: 13
This is the summary for test reports received on the zope-tests list between 2014-01-28 00:00:00 UTC and 2014-01-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/zopetoolkit/process/buildbots.html#the-nightly-builds Reports received ---------------- Successful - zopetoolkit_trunk - Build # 529 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.layer.ready2go_py_265_32 [3] winbot / z3c.pagelet_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/2014-January/080676.html [2] FAILED winbot / z3c.layer.ready2go_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-January/080674.html [3] FAILED winbot / z3c.pagelet_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-January/080675.html
On Thu, Jan 30, 2014 at 01:00:02AM +0100, Zope tests summarizer wrote:
[1] winbot / z3c.contents_py_265_32 [2] winbot / z3c.layer.ready2go_py_265_32 [3] winbot / z3c.pagelet_py_265_32
winbot is unable to build lxml[1], which is needed for the above. AFAICT the problem is that lxml 3.3.0 wants to include stdint.h[2] winbot has Microsoft Visual Studio 9.0 (which is same as Visual Studio 2008 apparently?), which is missing stdint.h[3]. [1] http://winbot.zope.org/builders/wineggbuilder/builds/48053/steps/release%20e... [2] "c:\temp\lxmlbuild\lxml\src\lxml\lxml_endian.h(2) : fatal error C1083: Cannot open include file: 'stdint.h': No such file or directory" shows up in [1] [3] http://stackoverflow.com/questions/126279/c99-stdint-h-header-and-ms-visual-... This may be part of a larger problem -- if lxml wants C99, and MSVC2008 does not support C99, we might encounter more problems. Anyone have ideas? I filed this bug: https://bugs.launchpad.net/lxml/+bug/1274413 Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development
On Thu, Jan 30, 2014 at 10:37:38AM +0200, Marius Gedminas wrote:
On Thu, Jan 30, 2014 at 01:00:02AM +0100, Zope tests summarizer wrote:
[1] winbot / z3c.contents_py_265_32 [2] winbot / z3c.layer.ready2go_py_265_32 [3] winbot / z3c.pagelet_py_265_32
winbot is unable to build lxml[1], which is needed for the above.
AFAICT the problem is that lxml 3.3.0 wants to include stdint.h[2] winbot has Microsoft Visual Studio 9.0 (which is same as Visual Studio 2008 apparently?), which is missing stdint.h[3].
[1] http://winbot.zope.org/builders/wineggbuilder/builds/48053/steps/release%20e... [2] "c:\temp\lxmlbuild\lxml\src\lxml\lxml_endian.h(2) : fatal error C1083: Cannot open include file: 'stdint.h': No such file or directory" shows up in [1] [3] http://stackoverflow.com/questions/126279/c99-stdint-h-header-and-ms-visual-...
This may be part of a larger problem -- if lxml wants C99, and MSVC2008 does not support C99, we might encounter more problems.
Anyone have ideas? I filed this bug: https://bugs.launchpad.net/lxml/+bug/1274413
Fixed upstream. We're now waiting for 3.3.1 to show up on PyPI. It would be nice to try and build the current master snapshot, but I don't have a recent-enough Cython :/ Any takers? Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development
On Thu, Jan 30, 2014 at 02:10:24PM +0200, Marius Gedminas wrote:
On Thu, Jan 30, 2014 at 10:37:38AM +0200, Marius Gedminas wrote:
On Thu, Jan 30, 2014 at 01:00:02AM +0100, Zope tests summarizer wrote:
[1] winbot / z3c.contents_py_265_32 [2] winbot / z3c.layer.ready2go_py_265_32 [3] winbot / z3c.pagelet_py_265_32
winbot is unable to build lxml[1], which is needed for the above.
AFAICT the problem is that lxml 3.3.0 wants to include stdint.h[2] winbot has Microsoft Visual Studio 9.0 (which is same as Visual Studio 2008 apparently?), which is missing stdint.h[3].
[1] http://winbot.zope.org/builders/wineggbuilder/builds/48053/steps/release%20e... [2] "c:\temp\lxmlbuild\lxml\src\lxml\lxml_endian.h(2) : fatal error C1083: Cannot open include file: 'stdint.h': No such file or directory" shows up in [1] [3] http://stackoverflow.com/questions/126279/c99-stdint-h-header-and-ms-visual-...
This may be part of a larger problem -- if lxml wants C99, and MSVC2008 does not support C99, we might encounter more problems.
Anyone have ideas? I filed this bug: https://bugs.launchpad.net/lxml/+bug/1274413
Fixed upstream. We're now waiting for 3.3.1 to show up on PyPI.
It would be nice to try and build the current master snapshot, but I don't have a recent-enough Cython :/
Any takers?
Stefan Behnel uploaded an sdist with all the Cython files already preprocessed to http://lxml.de/files/lxml-3.3.1pre.tar.gz I built it on winbot using a local zope.wineggbuilder checkout in /tmp (which, I think, is mapped to c:\documents and settings\mgedmin\temporary files or something like that). I got an .exe installer for 32-bit Python 2.7 in /tmp/lxmlbuild/lxml/dist and tested it in a bit in a virtualenv. Things work. So we can hope that when 3.3.1 final is on PyPI, these errors will just clean up. (Meanwhile it would be nice if we could teach zope.wineggbuilder how to build wheels, since pip install can't install .exe files) Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development
participants (2)
-
Marius Gedminas -
Zope tests summarizer