pyliblo_0.9.1-3_amd64.changes REJECTED

[Sebastian Ramacher]

Hi,

On 2013-08-26 22:19:02, Jaromír Mikeš wrote:
> 2013/8/26 Sebastian Ramacher <sramacher at debian.org>
> 
> Hi Sebastian,
> 
>   * The package contains tests, so please run them at build time.
> >
> >  * One of the test fails. This should be investigated.
> >
> > | ======================================================================
> > | ERROR: testSendVarious (unit.ServerTestCase)
> > | ----------------------------------------------------------------------
> > | Traceback (most recent call last):
> > |   File "/tmp/sadt.u8ku9v/tmp.1sUegUi4nD/test/unit.py", line 86, in
> > testSendVarious
> > |     self.server.send(1234, '/blah', 123, 2**42, 123.456, 666.666,
> > "hello", ('c', 'x'), (12, 34, 56))
> > |   File "liblo.pyx", line 401, in liblo._ServerBase.send
> > (src/liblo.c:5459)
> > |   File "liblo.pyx", line 131, in liblo._send (src/liblo.c:2414)
> > |   File "liblo.pyx", line 707, in liblo.Message.__init__
> > (src/liblo.c:8213)
> > |   File "liblo.pyx", line 728, in liblo.Message.add (src/liblo.c:8435)
> > |   File "liblo.pyx", line 781, in liblo.Message._add_auto
> > (src/liblo.c:9071)
> > | OverflowError: value too large to convert to signed int
> >
> 
>  now I am running test during build and having different output:
> 
> ---------------------------------
> unit (unittest.loader.ModuleImportFailure) ... ERROR
> 
> ======================================================================
> ERROR: unit (unittest.loader.ModuleImportFailure)
> ----------------------------------------------------------------------
> ImportError: Failed to import test module: unit
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/unittest/loader.py", line 252, in _find_tests
>     module = self._get_module_from_name(name)
>   File "/usr/lib/python2.7/unittest/loader.py", line 230, in
> _get_module_from_name
>     __import__(name)
>   File "/tmp/tmp.Trgcr7ayk0/test/unit.py", line 18, in <module>
>     import liblo
> ImportError: No module named liblo
> ----------------------------------------------------------------------
> 
> This is new to me ... can you advice what to do with it?

The thing is that pyliblo builds an extension module. distutils builds
these modules in build/lib-$something-$pyver per default. From there they
will be installed when setup.py is invoked with install.

To run the tests, the extensions modules need to be available in
PYTHONPATH. Starting with something like the test targets found at
https://wiki.debian.org/Python/LibraryStyleGuide, one could use

# Callable functions to determine the correct PYTHONPATH
pythonpath = $$(ls -d $(CURDIR)/build/lib.*-$(1))

ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS)))
test-python%:
  PYTHONPATH=$(call pythonpath,$*) \
    python$* -m unittest discover -s test/ -p '*.py' -v

override_dh_auto_test: $(PYTHON2:%=test-python%) $(PYTHON3:%=test-python%)
endif

(untested)

Hope that helps
-- 
Sebastian Ramacher
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-multimedia-maintainers/attachments/20130827/7db9b5e9/attachment.sig>