You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Pillow currently fails to build from source on the buildds for the sh4 (Renesas SuperH) port of Debian. The testsuite crashes at some point with a traceback starting in the file /usr/lib/python2.7/dist-packages/nose/plugins/multiprocess.py.
I am not really an expert in Python but I would assume this issue arises since Pillow makes wrong assumptions about the underlying architecture. But please have a look at it yourself, I am attaching a the full build log [1]. I am also happy to provide further details if necessary and I would be happy to test any patches.
Alright, that was actually my guess :). I will ask the maintainer in Debian to disable that particular test on sh4. I am a Debian Developer myself but I don't maintain Pillow.
Could you give me a quick hint how to disable it so I can come up with a patch right away? Otherwise I am sure that Matthias Klose (maintainer of Pillow in Debian) will be able to do that as well.
If these are nose tests, then pass 0 to --processes to disable multiprocessing:
--processes=NUM Spread test run among this many processes. Set a
number equal to the number of processors or cores in
your machine for best results. Pass a negative number
to have the number of processes automatically set to
the number of cores. Passing 0 means to disable
parallel testing. Default is 0 unless NOSE_PROCESSES
is set. [NOSE_PROCESSES]
Hello!
Pillow currently fails to build from source on the buildds for the sh4 (Renesas SuperH) port of Debian. The testsuite crashes at some point with a traceback starting in the file /usr/lib/python2.7/dist-packages/nose/plugins/multiprocess.py.
I am not really an expert in Python but I would assume this issue arises since Pillow makes wrong assumptions about the underlying architecture. But please have a look at it yourself, I am attaching a the full build log [1]. I am also happy to provide further details if necessary and I would be happy to test any patches.
Cheers,
Adrian
The text was updated successfully, but these errors were encountered: