On 2015-09-09 18:09, Chris Lamb wrote: > What's notable is that no tests are now even being found (local build):
That I can reproduce, ... > So, this is a bug in itself. Poking a bit more, if I do something like: ... but it does not differ from the behavior in jessie even though the test driver switches from unittest to nose ... so is this really a bug? > $ python2.7 -m nose tests/unit > > .. I get a bunch of errors related to python-mock. Might be a good place > to start? I don't want to fix this, I'm just looking whether this affects jessie, too :-) The dh_auto_test section from my build logs: ===== jessie ===== dh_auto_test -O--buildsystem=pybuild I: pybuild base:170: cd /tmp/buildd/python-pika-0.9.14/.pybuild/pythonX.Y_2.7/build; python2.7 -m unittest discover -v ---------------------------------------------------------------------- Ran 0 tests in 0.000s OK ===== /jessie ===== ===== sid ===== dh_auto_test -O--buildsystem=pybuild I: pybuild base:170: cd /tmp/buildd/python-pika-0.9.14/.pybuild/pythonX.Y_2.7/build; python2.7 -m nose ---------------------------------------------------------------------- Ran 0 tests in 0.142s OK ===== /sid ===== ===== yours ===== dh_auto_test -O--buildsystem=pybuild I: pybuild base:170: cd /tmp/buildd/python-pika-0.9.14/.pybuild/pythonX.Y_2.7/build; python2.7 -m nose --with-doctest E ====================================================================== ERROR: Failure: ImportError (No module named pyev) ===== /yours ===== The only difference I see here is that pybuild no longer runs nose with --with-doctest (#749506). Andreas
