|
From: | Scott Hannahs |
Subject: | Re: [Duplicity-talk] Failure running tests. |
Date: | Thu, 12 Sep 2019 17:54:27 -0400 |
Ken, I am willing to leave the unicode errors as just an old OS weirdness. The others I am a bit concerned that I am not testing correctly or it isn’t passing the test. This happens both on the old OS and the new OS with Python 3.7. To take the second failed test (the first failure is a unicode problem in test_selection).
which if I read this right gives me a command line: ...command: "../bin/duplicity" "file://testfiles/replicate_out" "testfiles/restore_out" "--restore-time" "100000" "-v0" "--no-print-statistics" "--allow-source-mismatch" "--archive-dir=testfiles/cache" < /dev/null And then the error which seems way beyond my python knowledge. I can find the fsdecode function in os.py but why it is getting a bad argument is beyond me. I do not know why it should think that it will find the cache directory since that is not in the gzip tar file. But maybe it was generated in a previous test? In reading the test language I don’t see that but that may be my limitation.
Including the whole output including the build and testing phase. -Scott |
fink-duplicity.txt
Description: Text document
|
[Prev in Thread] | Current Thread | [Next in Thread] |