Re: [Duplicity-talk] Errors during test phase with duplicity

[Scott Hannahs]

Ken,

I get the same errors in that test.  I did not use the -i with sudo since there isn’t a login directory with that user.

ERROR: test_piped_password (testing.functional.test_final.FinalTest)
ERROR: test_piped_password (testing.functional.test_final.OldFilenamesFinalTest)
ERROR: test_piped_password (testing.functional.test_final.ShortFilenamesFinalTest)
ERROR: test_new_file (testing.functional.test_restart.RestartTest)
ERROR: test_split_after_large (testing.functional.test_restart.RestartTest)
ERROR: test_split_after_small (testing.functional.test_restart.RestartTest)
ERROR: test_split_inside_large (testing.functional.test_restart.RestartTest)
ERROR: test_ignore_double_snapshot (testing.functional.test_restart.RestartTestWithoutEncryption)
ERROR: test_new_file (testing.functional.test_restart.RestartTestWithoutEncryption)
ERROR: test_split_after_large (testing.functional.test_restart.RestartTestWithoutEncryption)
ERROR: test_split_after_small (testing.functional.test_restart.RestartTestWithoutEncryption)
ERROR: test_split_inside_large (testing.functional.test_restart.RestartTestWithoutEncryption)

However, they seem to be a chown error?  That is certainly a root only operation.  Is that what the call to os.chown does?

  File "/sw/src/fink.build/duplicity-0.7.14-2/duplicity-0.7.14/duplicity/path.py", line 469, in <lambda>

    util.maybe_ignore_errors(lambda: os.chown(other.name, self.stat.st_uid, self.stat.st_gid))
OSError: [Errno 1] Operation not permitted: 'testfiles/cache/8545a8b798d7684a61ae2472e32d92e2/duplicity-full-signatures.20170907T222605Z.sigtar.gz’

Is that function trying to chown the destination file during a restore?  If the restore is not being done as root then it should skip that and leave the file with the different owner of the restoring account.

Here is the full test log from 

$ sudo -u fink-bld  ./setup.py test &> ~/Desktop/setup-test1.log

setup-test1.log
Description: Binary data

The good news is despite these test errors duplicity seems to be executing a nightly run on my files to an s3 backend.

-Scott

On Sep 6, 2017, at 7:55 AM, Kenneth Loafman via Duplicity-talk <address@hidden> wrote:

Scott,

You should not need root to build or test duplicity.  Is it possible that you've run pip with sudo at some point?  That could be a problem.

No, there is no problem in the patching tests.  There's something else going on there.

From the setup-test.log file, I'm seeing a lot of permission denied errors that I don't get, mostly from chown calls.  

Try with -i 

$ sudo -i -u fink-bld  ./setup.py test &> ~/Desktop/setup-test.log

or just as yourself

$ ./setup.py test &> ~/Desktop/setup-test.log

...Ken