Works for me with doing py.test, I can live with it.
On Wed, Jul 9, 2014 at 1:55 PM, Mike Bayer wrote:
> OK this is fixed now, I hope.
>
>
>
> On 7/9/14, 9:52 AM, Mike Bayer wrote:
>
> OK what if you just run it via "py.test" ?the distutils/setuptools
> approach is so often problematic.
>
OK this is fixed now, I hope.
On 7/9/14, 9:52 AM, Mike Bayer wrote:
> OK what if you just run it via "py.test" ?the distutils/setuptools
> approach is so often problematic.
>
> issue appeared in 0.9.6, not 0.9.5 ?
>
>
>
>
> On 7/9/14, 3:01 AM, Jason Newton wrote:
>> Yes, it seems to me like i
OK what if you just run it via "py.test" ?the distutils/setuptools
approach is so often problematic.
issue appeared in 0.9.6, not 0.9.5 ?
On 7/9/14, 3:01 AM, Jason Newton wrote:
> Yes, it seems to me like it gets to the end and then commits suicide
> just before returning, but I wasn't abl
Yes, it seems to me like it gets to the end and then commits suicide just
before returning, but I wasn't able to make heads or tails.
Nothing fancy to running it - just unpack the pypi archive, and run python
setup.py test. I first ran into it when updating the opensuse package from
0.8.5 but
how are you running them?
it isn't reporting any "failure", this seems like it's finding a bad
test case. do you have any test.py type stuff it might be hitting?
On 7/8/14, 5:56 PM, Jason Newton wrote:
> Any thoughts on why the unit testing is failing?
>
> platform linux2 -- Python 2.7.6 -- p
Any thoughts on why the unit testing is failing?
platform linux2 -- Python 2.7.6 -- py-1.4.20 -- pytest-2.5.2 --
/usr/bin/python
== 5776 passed, 688
skipped in 139.77 seconds
===
