>
> 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.
>
>
Test failed are:
Hi, I get exception when I'm trying to connect to swift backend.
My provider uses '/auth/v1.0' so swift backend fails in first iteration of
for loop in _get_conn but instead of second try with '/auth/v1.0' I get
this:
Uncaught top-level exception:
Traceback (most recent call last):
File "/home
S3ql 2.x needs Python 3 so you should use python3-devel python3-setuptools
python3-crypto python3-apsw and python3-llfuse packages.
On Tuesday, April 8, 2014 8:16:36 PM UTC+2, Diogo Vieira wrote:
>
> Hello,
>
> I'm trying to package s3ql in Fedora since the version in the repositories
> is still
On 04/14/2014 10:07 AM, Adam Watkins wrote:
>
>
> This comes from the server discussed in my first email, and is running
> S3QL 2.8.1:
[...]
Could you apply the attached patches the python-dugong and S3QL, and
then try to reproduce the problem?
To apply the patches, do a 'patch -p1 < patchname.
On 04/14/2014 10:07 AM, Adam Watkins wrote:
>
>
> This comes from the server discussed in my first email, and is running
> S3QL 2.8.1:
Alright, I'll probably have to send you some extra code to get more
debugging information.
Could you please also file this as a (second, new) bug on
https://bi
On 04/14/2014 10:06 AM, Adam Watkins wrote:
> This comes from another server running Debian 7.4 and using the S3QL
> 1.11 package:
> This server _isn't_ running on my home network, and I've no reason to
> believe that it's connection is particularly unreliable.
>
[]
Thanks! Could you please f
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 @@
>
On 04/14/2014 08:17 AM, Adrin wrote:
>
>
> On Monday, 14 April 2014 03:11:04 UTC+2, Nikolaus Rath wrote:
> On 04/13/2014 01:46 PM, Adrin wrote:
> > Hi,
> >
> > I'm not sure if I understand it correctly, but is it true that you are
> > storing the AES key along with the dat
This comes from the server discussed in my first email, and is running S3QL
2.8.1:
2014-04-13 03:49:09.689 [pid=27186, thread='Thread-3', module='root',
fn='excepthook', line=157]: Uncaught top-level exception:
Traceback (most recent call last):
File
"/usr/local/lib/python3.4/si
This comes from another server running Debian 7.4 and using the S3QL 1.11
package:
This server _isn't_ running on my home network, and I've no reason to
believe that it's connection is particularly unreliable.
2014-04-14 16:38:31.830 [11382] MainThread: [mount] Encountered
exception, trying
>
>
>
> On Monday, 14 April 2014 03:11:04 UTC+2, Nikolaus Rath wrote:
> On 04/13/2014 01:46 PM, Adrin wrote:
> > Hi,
> >
> > I'm not sure if I understand it correctly, but is it true that you are
> > storing the AES key along with the data?
>
> Yes.
>
> > Then what's the point of encrypting the da
11 matches
Mail list logo
