duplicity-team team mailing list archive

[Aaron <lists@xxxxxxxxxxxxxxxxxx>]

Hi Ken,

On 02/07/2019 15:34, Kenneth Loafman wrote:
> We're making progress!  With the latest update:
>
>  1. On an 18.04 Ubuntu VM:
>       * py27 passes all tests
>       * py3 passes all but 7 tests
>  2. On a rebuilt docker instance:
>       * fails a lot more tests on both
>       * abandoned till later
These failures appear to be caused by something in rev 1382 or 1383. I 
made sure there were no failures in the tests using the Docker method 
before putting in my merge request for the 08-dockerfixes branch (r1381).

If I now do the docker test on the trunk:

bzr branch lp:duplicity dup20190702
cd dup20190702/testing/infrastructure/
./build-duplicity_test.sh
./setup.sh
cd testing/
./run-tests

I also get py27 passing, 7 failures and 1 warning on py3 and 2 failures 
on code.

But if I do:

bzr branch lp:duplicity dup20190702_tweaked
cd dup20190702_tweaked/testing/infrastructure/

[edit the duplicity_test Dockerfile to replace "bzr branch lp:duplicity duplicity"
 with "bzr branch -r 1381 lp:duplicity duplicity"
 (or bzr branch "lp:~aaron-whitehouse/duplicity/08-dockerfixes duplicity")]

./build-duplicity_test.sh
./setup.sh
cd testing/
./run-tests

There are no failures. Testing r1383 in the container brings the 7+2 
failures back. I have not yet dug into what in those revisions are 
causing the problem.

Kind regards,

Aaron