On Feb 22 2016, Steven Chamberlain <steven@pyro.eu.org> wrote:
> Nikolaus Rath wrote:
>> Ah, ok. I guess it gives non-zero exact status if it doesn't find any
>> tests to run at all.
>>
>> So the next question is why is it finding only one test, and why is it
>> skipping that one.
>>
>> * Is there a "fusermount" executable available on kfreebsd?
>
> No, but there is a mount_fusefs in package fuse4bsd.
That explains why two out of 3 test files are skipped. But not why only
1 out of 3 is discovered.
>
> Also I realised when I suggested before putting in Build-Depends:
> fuse [linux-any] | fuse4bsd [kfreebsd-any],
> that actually does not do as intended unless written as:
> fuse [linux-any], fuse4bsd [kfreebsd-any],
Fixed, thanks!
>> * Can you re-run with 'py.test-3 --collect-only test/'?
>
> I tried on two different machines with the same result:
> 1. a restricted chroot like on the buildds, clean up-to-date sid,
> without the fuse kernel module loaded, and no /dev/fuse;
> 2. a local machine having the kernel module loaded, and /dev/fuse.
>
> $ py.test-3 --collect-only test/ ; echo exit status $?
> ============================= test session starts ==============================
> platform gnukfreebsd10 -- Python 3.4.4rc1, pytest-2.8.5, py-1.4.31, pluggy-0.3.1 -- /usr/bin/python3
> cachedir: test/.cache
> rootdir: /home/steven/python-llfuse-0.41.1+dfsg/test, inifile: pytest.ini
> collected 0 items / 1 skipped
>
> ========================== 1 skipped in 0.06 seconds ===========================
> exit status 5
What the heck. I don't want to take too much of your time, I'll try to
get access to a kfreebsd machine to look into this directly.
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.«
Attachment:
signature.asc
Description: PGP signature