|
From: | Scott Hannahs |
Subject: | Re: [Duplicity-talk] Errors during test phase of installation..... |
Date: | Thu, 2 Feb 2017 12:27:10 -0500 |
Ken, I am sorry, I did not get back to you on this…. I thought I had written the email. I have resolved almost all the test issues. The main problem was that in setting up and running the test, there are a huge number of open files simultaneously and this runs up against the Mac OS X default setting for number of open files per process. That defaults to 256 files. It turns out that the duplicity test needs more than that simultaneous open files and if I set that limit to 8192 most of the tests pass. I think all the remaining test issues are due to the missing paramiko version 2.X backend. The clues was the “AssertionError 37” which had insufficient file system resources or something like that when I looked at the code. So when I give it a lot more file resources it works. This is only during the testing phase since I think I have been running it on big directories with the default values. The other big error was that the un-tar of the test files would set file permissions and owners so that the test user could not delete them. I set a note that the testing phase has to run as root. It shouldn’t but that seems to be an issue. If the no-owner no-group flags were set on the untar command for the test directories it might work. But that may mess up some of the tests. The librsyncmodule is compiled correctly. As I said, I have installed it and run duplicity for a long time using the rsync and now S3 backend. -Scott
|
[Prev in Thread] | Current Thread | [Next in Thread] |