Sorry, I could have been more clear. That error happens at the END of the
tests. I don't believe a test is failing per se. Nothing is flagged as
failed, anyway (191 passed, 103 skipped in 63.60 seconds). This looks like
it is something to do with cleanup.
brian
On Thursday, May 1, 2014 2:53:11 PM UTC-4, Brian Pribis wrote:
>
> Compiled s3ql 2.8.1 on ubuntu 14.04. I get a fail on my tests like:
>
> Exception ignored in: <bound method BlockCache.__del__ of
> <s3ql.block_cache.BlockCache object at 0xb65cd24c>>
> Traceback (most recent call last):
> File "/mnt/netshare/home/brian/s3ql-2.8.1/src/s3ql/block_cache.py", line
> 923, in __del__
> raise RuntimeError("BlockManager instance was destroyed without
> calling destroy()!")
> RuntimeError: BlockManager instance was destroyed without calling
> destroy()!
>
>
> I'm not running the test as sudo (not sure if that makes a difference).
> If I run as sudo I get:
>
> Traceback (most recent call last):
> File "/mnt/netshare/home/brian/s3ql-2.8.1/tests/t2_block_cache.py", line
> 163, in test_destroy_deadlock
> self.cache.destroy()
> File "_pytest.python", line 1009, in __exit__
> pytest.fail("DID NOT RAISE")
> File "_pytest.runner", line 456, in fail
> raise Failed(msg=msg, pytrace=pytrace)
> Failed: DID NOT RAISE
>
>
> Any help would be appreciated. Thanks,
>
> Brian
>
--
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
