|
From: | Scott Hannahs |
Subject: | Re: [Duplicity-talk] Duplicity 2.2.2 Released |
Date: | Sat, 10 Feb 2024 18:29:08 -0500 |
Ken, Thanks, I don’t mind extra output, but it looked like duplicity was merely repeating an error for a bad command line option. That was very different than when I setup duplicity 2.2.1. I am running the tests right now and will let you know how it goes. For testing on macOS, I use the following parameters to install the dependencies and then to set the number of files to “large” and to explicitly run the correct pytest version. Is tox not needed anymore? TestDepends: << pylint-py310, future-py310, librsync-bin, mock-py310, pluggy-py310, py-py310, tox-py310 << TestScript: << #!/bin/sh -ev ulimit -n 8192 %p/bin/pytest3.10 << Using pytest I get 23 command line “usage” errors. I get a much larger number of errors: ""ModuleNotFoundError: No module named 'fasteners'" Which is why I tested running python3.10 manually and import fasteners. Do I need to set the “PYTHONPATH” variable to anything specific? And the very last line of testing shows way more errors that previously: =========== 124 failed, 303 passed, 17 skipped in 112.73s (0:01:52) ============ -Scott
|
[Prev in Thread] | Current Thread | [Next in Thread] |