|
From: | Scott Hannahs |
Subject: | Re: [Duplicity-talk] Errors during test phase with duplicity |
Date: | Tue, 5 Sep 2017 22:50:30 -0400 |
Ken,
I take that back. When the testing is run as root I get less errors (3 instead of 12) : % grep FAILED duplicity.*.err.txt duplicity.nonroot.err.txt:FAILED (failures=1, errors=12, skipped=5) duplicity.root.err.txt:FAILED (failures=2, errors=3, skipped=5) As root, just the "piped password” tests fail. The other “restart” test errors seem to work. But restarting shouldn’t necessitate root permissions? As root, there is a second and different failure in the “patching” sequence?? Test patching sequence ... FAIL ====================================================================== FAIL: test_patch_seq2ropath (testing.unit.test_patchdir.TestInnerFuncs) Test patching sequence ---------------------------------------------------------------------- Traceback (most recent call last): File "/sw/src/fink.build/duplicity-0.7.14-4/duplicity-0.7.14/testing/unit/test_patchdir.py", line 290, in test_patch_seq2ropath testseq([self.snapshot()], ("%s 600" % ids), "hello, world!") File "/sw/src/fink.build/duplicity-0.7.14-4/duplicity-0.7.14/testing/unit/test_patchdir.py", line 282, in testseq assert result.getperms() == perms, (result.getperms(), perms) AssertionError: ('0:1000 600', '0:0 600')
Duplicity-talk mailing list address@hidden https://lists.nongnu.org/mailman/listinfo/duplicity-talk |
[Prev in Thread] | Current Thread | [Next in Thread] |