Bug#893743: python-cffi: FTBFS on hurd-i386: test_thread AssertionError
Source: python-cffi
Version: 1.11.5-1
Severity: important
Tags: upstream
Justification: fails to build from source (but built successfully in the past)
User: debian-hurd@lists.debian.org
Usertags: hurd
The latest build of python-cffi for hurd-i386 (admittedly not a
release architecture) failed, per the below excerpts from [1]:
I: pybuild base:184: python2.7-dbg -m pytest c/ testing/
= test session starts
==
[...]
=== FAILURES
===
_ TestThread.test_init_different_modules_in_different_threads
__
self =
def test_init_different_modules_in_different_threads(self):
add1_cffi = self.prepare_module('add1')
add2_cffi = self.prepare_module('add2')
self.compile('thread2-test', [add1_cffi, add2_cffi], threads=True)
output = self.execute('thread2-test')
output = self._take_out(output, "preparing")
output = self._take_out(output, ".")
output = self._take_out(output, ".")
# at least the 3rd dot should be after everything from ADD2
> assert output == ("starting\n"
"prepADD2\n"
"adding 1000 and 200 and 30\n"
".\n"
"adding 40 and 2\n"
"done\n")
E AssertionError: assert 'starting\n.\...nd 30\ndone\n' ==
'starting\npre...and 2\ndone\n'
E starting
E + prepADD2
E + adding 1000 and 200 and 30
E .
E adding 40 and 2
E - prepADD2
E - adding 1000 and 200 and 30...
E
E ...Full output truncated (2 lines hidden), use '-vv' to show
testing/embedding/test_thread.py:29: AssertionError
Could you please take a look?
Thanks!
[1]
https://buildd.debian.org/status/fetch.php?pkg=python-cffi&arch=hurd-i386&ver=1.11.5-1&stamp=1519773174&raw=0
--
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
Bug#893750: universal-ctags: FTBFS on hurd-i386: timeouts, even on empty input
Source: universal-ctags Version: 0+git20180225-1 Severity: normal Tags: upstream User: debian-hurd@lists.debian.org Usertags: hurd The build of universal-ctags for hurd-i386 (admittedly not a release architecture) failed with timeouts across the board, even on empty input, per the below excerpts from [1]. Could you please take a look? Thanks! [1] https://buildd.debian.org/status/fetch.php?pkg=universal-ctags&arch=hurd-i386&ver=0%2Bgit20180225-1&stamp=1519749399&raw=0 -- Category: ROOT Testing conflib-recursive as Cof[31mfailed[39m (TIMED OUT) Shrinking ./Units/conflib-recursive.d/input.cof as Cof [0292]...timeout(124) [0 0]...timeout(124) the target command line exits abnormally against the empty input Testing conflib-simple as coffee[31mfailed[39m (TIMED OUT) Shrinking ./Units/conflib-simple.d/input.coffee as coffee [0292]...timeout(124) [0 0]...timeout(124) the target command line exits abnormally against the empty input [...] Testing truncation as C/xref[31mfailed[39m (TIMED OUT) Shrinking ./Units/xformat-option.r/truncation.d/input.c as C [0103]...timeout(124) [0 0]...timeout(124) the target command line exits abnormally against the empty input Summary (see CMDLINE.tmp to reproduce without test harness) #passed:0 #FIXED: 0 #FAILED (broken args.ctags?): 0 #FAILED (unexpected-exit-status): 0 #FAILED (unexpected-output):0 #TIMED-OUT (10s)865 -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
Bug#893752: leatherman: FTBFS on hurd-i386: test times out
Source: leatherman Version: 1.4.0+dfsg-1 Severity: normal Tags: upstream User: debian-hurd@lists.debian.org Usertags: hurd The build of leatherman for hurd-i386 (admittedly not a release architecture) failed: Running tests... /usr/bin/ctest --force-new-ctest-process -j1 Test project /<>/leatherman-1.4.0+dfsg/obj-i686-gnu Start 1: leatherman tests E: Build killed with signal TERM after 180 minutes of inactivity E: Build killed with signal KILL after 360 minutes of inactivity Could you please take a look? Thanks! -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
Bug#893756: ignition-common: FTBFS on hurd-i386: PATH_MAX not declared
Source: ignition-common Version: 1.0.1-1 Severity: normal Tags: upstream User: debian-hurd@lists.debian.org Usertags: hurd The build of ignition-common for hurd-i386 (admittedly not a release architecture) failed: /<>/src/FilesystemBoost.cc: In function 'std::__cxx11::string ignition::common::cwd()': /<>/src/FilesystemBoost.cc:134:25: error: 'PATH_MAX' was not declared in this scope The Hurd makes a point of not having a static PATH_MAX. Best practice is dynamically accommodating whatever you actually encounter, for instance by taking advantage of realpath's policy of allocating the buffer itself when supplied a NULL buffer. (You'll of course need to free it when done.) Could you please take a look? Thanks! -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
