[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Looking for sponsor for first DM upload



On Jan 03 2017, Eriberto <eriberto@eriberto.pro.br> wrote:
>>>>
>>>> http://www.rath.org/debs/s3ql_2.21+dfsg-1~bpo8+1.dsc>
>
> On my machine:
>
> ============================ pytest-warning summary ============================
> WC1 /tmp/nikolaus2/s3ql/s3ql-2.21+dfsg/tests/t2_block_cache.py cannot
> collect test class 'TestBackendPool' because it has a __init__
> constructor
> !!!!!!!!!!!!!!!!!!!! Interrupted: stopping after 1 failures !!!!!!!!!!!!!!!!!!!!
> ====== 48 passed, 1 skipped, 1 pytest-warnings, 1 error in 14.03 seconds =======
> debian/rules:51: recipe for target 'override_dh_auto_test' failed
> make[1]: *** [override_dh_auto_test] Error 2
> make[1]: Leaving directory '/tmp/nikolaus2/s3ql/s3ql-2.21+dfsg'
> debian/rules:8: recipe for target 'build' failed
> make: *** [build] Error 2
> dpkg-buildpackage: error: debian/rules build gave error exit status 2
> debuild: fatal error at line 1376:
> dpkg-buildpackage -rfakeroot -D -us -uc failed
>
>
> We have a problem...

Can you just try a rebuild? There is a race condition in one of the
tests that I have not yet managed to root out.

If it still fails, could you provide more output? The above doesn't
actually contain the reason for the failure (the pytest warning is
unrelated).

If you're using libeatmydata, you need to either disable it or make
libeatmydata*.so setuid root (but not executable), otherwise the error
messages when running the (setuid) /bin/fusermount will make the unit
tests think that something went wrong.

If you're building in a chroot, make sure that /etc/mtab exists (it
should probably be a symlink to /proc/mounts).


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.«


Reply to: