duplicity-team team mailing list archive

[Michael Terry <mike@xxxxxxxxxxx>]

They aren't?  They should be...  The build runs ./setup.py test.  And
that's what tox does too I believe.

On 13 November 2014 09:28, Kenneth Loafman <kenneth@xxxxxxxxxxx> wrote:

> Why aren't these tests in the tox tests?
>
>
> On Tue, Nov 11, 2014 at 9:12 AM, Michael Terry <mike@xxxxxxxxxxx> wrote:
>
>> On 11 November 2014 04:43, <edgar.soldin@xxxxxx> wrote:
>>
>>> 1. how can i get the build log?
>>>
>>
>> Well if you run locally you can see the errors.  Otherwise the
>> build-failed messages on this list have links.
>>
>>
>>> 2. how to run the same tests locally on my box?
>>>
>>
>> python setup.py test
>>
>>
>>> 3. how to just run one test if it fails (was on the list, just ask for
>>> completeness here)
>>>
>>
>> That's a little harder (the above command does some proper path-pointing
>> and such so you get the correct built versions of everything).  I haven't
>> tried in a while, but I believe there's a trick for this.
>>
>> Either you could edit setup.py and change:
>>       test_suite = 'testing',
>> to something like:
>>       test_suite = 'testing.functional.test_final',
>>
>> Or you could try to run nosetests directly and maybe point it at the
>> right things like:
>> PATH=./bin:$PATH nosetests testing/functional/test_final.py
>> or some such.  Haven't tried that recently.
>>
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~duplicity-team
>> Post to     : duplicity-team@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~duplicity-team
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>