On 04/13/2014 11:51 PM, Cristian Manoni wrote: > > > Hmm. Does it by any chance help if you apply the following patch? > > diff --git a/tests/t2_block_cache.py b/tests/t2_block_cache.py > --- a/tests/t2_block_cache.py > +++ b/tests/t2_block_cache.py > @@ -156,6 +156,7 @@ > > # Shutdown threads > llfuse.lock.release() > + time.sleep(10) > try: > > > > we are not lucky > > I had the same error:
Darn. Could you please file a bug at https://bitbucket.org/nikratio/s3ql/issues? I'll see what I can do. Could you check if any other tests fail as well? If you remove the --exitfirst argument in tests/pytest.ini, py.test will continue with the remaining tests even when encountering a failure. If the other tests all pass, you can probably still safely use S3QL, i.e. the bug is in the testcase rather than in the program itself. 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.« -- You received this message because you are subscribed to the Google Groups "s3ql" group. To unsubscribe from this group and stop receiving emails from it, send an email to s3ql+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
