Re: [Duplicity-talk] Duplicity Testing...

[Michael Terry]

I'm not sure why that would hang necessarily.  If you comment that test out, does the next test just hang as well, or is it something wrong with all tests?

On 23 June 2015 at 14:44, Scott Hannahs <address@hidden> wrote:

Michael,

Thanks that helps.  I can patch the testing to use python2.7 which fink uses to make sure that the correct version is being used.  Actually I kept running into missing packages.  For testing it seems I need the following

tox-py27, pluggy-py27, pexpect-py27, mock-py27
Which are obviously the python 2.7 versions of those packages.  This multiple python installation is a pain for package managers.  But necessary...

Now I am one step further on the testing phase…  The test is running but hangs?  The first (and last message) is
"test_missing_file (testing.functional.test_badupload.BadUploadTest) … "

The testing script is executed from the main directory with:
python2.7 setup.py test

-Scott

> On Jun 23, 2015, at 03:08, Michael Terry <address@hidden> wrote:
>
> Hello!
>
> On Monday, 22 June 2015, Scott Hannahs <address@hidden> wrote:
> > I maintain the “fink” installer for duplicity on Mac OS X.  I have been asked why I haven’t had duplicity run the built in test suite.  I think that the answer is that I have been lazy!  I started looking at it and have a few questions.
> >
> > The duplicity program has some testing built in when the installer runs in “test” mode.  I am not well versed in python installers by any means.  But it appears that these tests are run with the installer command
> >
> > setup.py -test
> >
> > But this depends on some environment variable “python2” that should point to ???
> > % setup.py -test
> > env: python2: No such file or directory
>
> Ah yes... I think Mac does not use the python2 executable, it's just python there. We could use just python ourselves (though this would conflict with Arch which allows that to point at python3).
>
> Or you could patch it to be python without the 2?
>
>
> > If I run the tests manually I see that I need the packages “tox” and “pluggy” installed.  Is that correct?  Are there others?
>
> I'm not familiar with us using pluggy, but I don't have the code near me right now. But tox we use (to set up the fake/reproducible python environment for the tests)
>
>
> > I have tox installed and just (maybe??) made a module to install pluggy.
> >
> > I am also not clear on how duplicity uses a server during the test or does it just use the local file system?
>
> Just the local system. For tests that would hit a server, we use mocks.
>
>
> >
> > -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