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

[Kenneth Loafman]

Yes, the extras are there for the code tests and the cloudfiles tests, so you don't need them unless you want them.

We normally use tox for testing.  It sets up a clean environment and then runs ./setup.py test.  When I run '$ tox -e py27', I get:

Ran 419 tests in 476.537s

OK (skipped=2)

so that tells me that something is setup differently between us.

Please do:

    $ pip2 freeze > pip-freeze.txt

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

and attach the files to your reply.

...Thanks,

...Ken

On Mon, Sep 4, 2017 at 3:40 PM, Scott Hannahs <address@hidden> wrote:

Ken,

I think it helps.  Of course it leads to more questions… :-)

I think this bug is already reported.  Bug #1399843 "par2 is required to run duplicity ./setup.py test”

Actually I am trying to set up the Mac OS X fink package still and I am getting some test failures.  For running duplicity, I have the following which is *close* to what you have.  Some such as libffi are already installed as part of python27.  This should cover most of the backends that are popular?

Depends: <<
        python27,
        librsync-shlibs (>= 0.9.7-1002),
        gnupg-unified,
        fasteners-py27,
        intltool40,
        paramiko-py27,
        pycrypto-py27,
python-pycryptopp,
        pexpect-py27,
        lftp,
        ncftp,
        par2,
        boto-py27 (>= 2.1.1),
        requests-oauthlib-py27
<<

For testing, I have the additional items, but not pycodestyle, pydrive, pylint, python-cloudfiles or pyrax.  I assume that python-cloudfiles and pyrax are for the cloud files (cf) backend which I haven’t implemented yet.

Are the others necessary only when RUN_CODE_TESTS=1??

However one of the tests that fails is rdiff that I have no build for since it seems to be fairly obsolete and not a maintained.  I only see it in one test for a large file.  I can live with that one failure rather than install yet another utility.

./testing/unit/test_diffdir.py:        assert not os.system("rdiff patch testfiles/dir2/largefile "

    TestDepends: <<

        mock-py27,

        pluggy-py27,

        py-py27,

        tox-py27

<<

There are 12 tests that give an error.  Some of these are entering passwords, but I thought that pexpect would handle those but there is an empty string error.

The rest are Restart errors and those give a CmdError=30 which I have no idea what that is but seems to be a generic error?

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)

-Scott

On Sep 4, 2017, at 6:58 AM, Kenneth Loafman <address@hidden> wrote:

The tests should detect the absence and skip over it, so please submit a bug report.

I would go ahead and install the options needed if you want to test, like so:

    # apt-get install -y \

            build-essential \

            bzr \

            intltool \

            lftp \

            librsync-dev \

            libffi-dev \

            libssl-dev \

            openssl \

            par2 \

            python-dev \

            rdiff \

            tzdata

I've attached a requirement.txt file for testing as well.  Use it like so:

    # pip install --requirement requirements.txt

Hope that helps.

...Ken

On Sun, Sep 3, 2017 at 4:14 PM, Scott Hannahs via Duplicity-talk <address@hidden> wrote:

Is there a flag to disable certain backend tests?  Or should they detect if that backend is not installed and skip over it?

-Scott

> On Sep 3, 2017, at 3:39 PM, edgar.soldin--- via Duplicity-talk <address@hidden> wrote:
>
> Scott,
>
> par2 binaries are only needed for the par2 backend. so unless the par2 backend is tested, they are not needed.
>
> ..ede/duply.net
>
> On 9/3/2017 20:04, Scott Hannahs via Duplicity-talk wrote:
>> When I build duplicity and try to run the tests, I get several errors.   One question that might resolve some of them.
>>
>> Are the par2 libraries/commands necessary for duplicity?  Should successful testing depend on those libraries or should the test sequence skip over those if the par2 libraries/commands are not installed?
>>
>> This is on Mac OS X
>>
>> -Scott
>>
>>
>>
>> _______________________________________________
>> Duplicity-talk mailing list
>> address@hidden
>> https://lists.nongnu.org/mailman/listinfo/duplicity-talk
>>
>
>
> _______________________________________________
> Duplicity-talk mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/duplicity-talk


_______________________________________________
Duplicity-talk mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/duplicity-talk

<requirements.txt>