Bug#851724: python-llfuse: FTBFS (failing tests)

[Nikolaus Rath]

On Jan 22 2017, Santiago Vila  wrote:
> On Sat, Jan 21, 2017 at 04:12:28PM -0800, Nikolaus Rath wrote:
>
>> Are you able to reproduce this with Python 3.5?
>
> I don't know. I'm just building the package from source.
>
> The package currently build-depends on both python-all-dev and 
> python3-all-dev.
>
> By "trying with Python 3.5" you mean removing the build-dependency on
> python-all-dev?

Sorry, this was a little terse. The build process runs with unit tests
with all available Python versions, starting with 2.x. However, it
aborts on the first failed test. I was wondering if in any of your
builds it ever made it through the 2.7 tests and then failed when
testing with 3.x.

You could force this behavior by removing the "-x" from test/pytest.ini
(in this case it attempts to run all tests). Removing the build-depends
may work as well, I'm not 100% sure.


Best,
Nikolaus

-- 
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F

 »Time flies like an arrow, fruit flies like a Banana.«

Bug#851724: python-llfuse: FTBFS (failing tests)

[Santiago Vila]

On Sat, Jan 21, 2017 at 04:12:28PM -0800, Nikolaus Rath wrote:

> Are you able to reproduce this with Python 3.5?

I don't know. I'm just building the package from source.

The package currently build-depends on both python-all-dev and python3-all-dev.

By "trying with Python 3.5" you mean removing the build-dependency on 
python-all-dev?

Thanks.

Bug#851724: python-llfuse: FTBFS (failing tests)

[Nikolaus Rath]

On Jan 17 2017, Santiago Vila  wrote:
> Exception in thread Thread-1 (most likely raised during interpreter shutdown):
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/threading.py", line 801, in __bootstrap_inner
>   File "/usr/lib/python2.7/threading.py", line 754, in run
>   File "src/misc.pxi", line 261, in llfuse._notify_loop (src/llfuse.c:29495)
>   File "/usr/lib/python2.7/Queue.py", line 179, in get
>   File "/usr/lib/python2.7/threading.py", line 384, in notify
> : 'NoneType' object is not callable
>  Interrupted: stopping after 1 failures 
> 

Thanks for reporting. This looks like a bug in Python 2.7
itself. Calling Queue.get() (a standard library class) should never fail
like that. Probably the best solution is for the test to ignore errors
during interpreter shutdown.

Are you able to reproduce this with Python 3.5?


Thanks,
-Nikolaus

-- 
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F

 »Time flies like an arrow, fruit flies like a Banana.«

Bug#851724: python-llfuse: FTBFS (failing tests)

[Santiago Vila]

Package: src:python-llfuse
Version: 1.1.1+dfsg-5
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep --with python2,python3,sphinxdoc --buildsystem=pybuild
   dh_testdir -i -O--buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
pybuild --configure -i python{version} -p 2.7
I: pybuild base:184: python2.7 setup.py config 
running config
pybuild --configure -i python{version}-dbg -p 2.7
I: pybuild base:184: python2.7-dbg setup.py config 
running config
[88380 refs]
pybuild --configure -i python{version} -p 3.5
I: pybuild base:184: python3.5 setup.py config 

[... snipped ...]

make[1]: Leaving directory '/<>/python-llfuse-1.1.1+dfsg'
   dh_auto_test -i -O--buildsystem=pybuild
pybuild --test -i python{version} -p 2.7
I: pybuild base:184: cd 
/<>/python-llfuse-1.1.1+dfsg/.pybuild/pythonX.Y_2.7/build; python2.7 
-m pytest --installed "/<>/python-llfuse-1.1.1+dfsg/test/"
= test session starts ==
platform linux2 -- Python 2.7.13, pytest-3.0.5, py-1.4.32, pluggy-0.4.0 -- 
/usr/bin/python2.7
cachedir: ../../../test/.cache
rootdir: /<>/python-llfuse-1.1.1+dfsg/test, inifile: pytest.ini
plugins: catchlog-1.2.2
collecting ... collected 13 items

../../../test/test_api.py::test_inquire_bits PASSED
../../../test/test_api.py::test_listdir PASSED
../../../test/test_api.py::test_sup_groups PASSED
../../../test/test_api.py::test_entry_res PASSED
../../../test/test_api.py::test_xattr PASSED
../../../test/test_examples.py::test_lltest PASSED
../../../test/test_examples.py::test_tmpfs FAILED

=== FAILURES ===
__ test_tmpfs __
Traceback (most recent call last):
  File "/<>/python-llfuse-1.1.1+dfsg/test/pytest_checklogs.py", line 
127, in pytest_runtest_call
check_output(item)
  File "/<>/python-llfuse-1.1.1+dfsg/test/pytest_checklogs.py", line 
119, in check_output
check_test_output(cm._capturing, item)
  File "/<>/python-llfuse-1.1.1+dfsg/test/pytest_checklogs.py", line 
96, in check_test_output
raise AssertionError('Suspicious output to stderr (matched "%s")' % 
hit.group(0))
AssertionError: Suspicious output to stderr (matched "Exception")
- Captured stderr call -
Exception in thread Thread-1 (most likely raised during interpreter shutdown):
Traceback (most recent call last):
  File "/usr/lib/python2.7/threading.py", line 801, in __bootstrap_inner
  File "/usr/lib/python2.7/threading.py", line 754, in run
  File "src/misc.pxi", line 261, in llfuse._notify_loop (src/llfuse.c:29495)
  File "/usr/lib/python2.7/Queue.py", line 179, in get
  File "/usr/lib/python2.7/threading.py", line 384, in notify
: 'NoneType' object is not callable
 Interrupted: stopping after 1 failures 
== 1 failed, 6 passed in 0.46 seconds ==
E: pybuild pybuild:276: test: plugin distutils failed with: exit code=2: cd 
/<>/python-llfuse-1.1.1+dfsg/.pybuild/pythonX.Y_2.7/build; python2.7 
-m pytest --installed "{dir}/test/"
dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13
debian/rules:10: recipe for target 'build-indep' failed
make: *** [build-indep] Error 25
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


This is just how the build ends, not necessarily the relevant part.

I've put several build logs here:

https://people.debian.org/~sanvila/build-logs/python-llfuse/

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

The bug should be reproducible with sbuild on a single CPU virtual machine.

I know this is strange because it built fine last time on buildd.debian.org,
but I can reproduce the failure in 7 different machines. In case you need help
to reproduce it, please say so. As a last resort I could offer ssh access
to a machine where this happens.

Thanks.