Re: Testing for FUSE in ci tests

2014-07-11 Thread Nikolaus Rath
Antonio Terceiro writes: > On Thu, Jul 10, 2014 at 11:06:59PM -0700, Nikolaus Rath wrote: >> On Thu, 17 Apr 2014 15:15:00 -0300, Antonio Terceiro wrote: >> > On Wed, Apr 16, 2014 at 06:49:41PM -0700, Nikolaus Rath wrote: >> >> Currently the S3QL CI tests fail because the test runner does not have

Re: Testing for FUSE in ci tests

2014-07-11 Thread Antonio Terceiro
On Thu, Jul 10, 2014 at 11:06:59PM -0700, Nikolaus Rath wrote: > On Thu, 17 Apr 2014 15:15:00 -0300, Antonio Terceiro wrote: > > On Wed, Apr 16, 2014 at 06:49:41PM -0700, Nikolaus Rath wrote: > >> Currently the S3QL CI tests fail because the test runner does not have > >> permission to access the /

Re: Testing for FUSE in ci tests

2014-07-10 Thread Nikolaus Rath
On Thu, 17 Apr 2014 15:15:00 -0300, Antonio Terceiro wrote: > On Wed, Apr 16, 2014 at 06:49:41PM -0700, Nikolaus Rath wrote: >> Currently the S3QL CI tests fail because the test runner does not have >> permission to access the /dev/fuse device >> (http://ci.debian.net/data/unstable-amd64/packages/s

Re: Testing for FUSE in ci tests

2014-04-17 Thread Antonio Terceiro
Hello Nikolaus, On Wed, Apr 16, 2014 at 06:49:41PM -0700, Nikolaus Rath wrote: > Hello, > > Currently the S3QL CI tests fail because the test runner does not have > permission to access the /dev/fuse device > (http://ci.debian.net/data/unstable-amd64/packages/s/s3ql/2014-04-10.log). > > Nothing

Testing for FUSE in ci tests

2014-04-16 Thread Nikolaus Rath
Hello, Currently the S3QL CI tests fail because the test runner does not have permission to access the /dev/fuse device (http://ci.debian.net/data/unstable-amd64/packages/s/s3ql/2014-04-10.log). Nothing wrong with that, but the test already goes out of its way to determine if it ought to be able