On 1/23/14, holger krekel <holger@merlinux.eu> wrote:
> On Thu, Jan 23, 2014 at 18:27 +0000, Sarah Mount wrote:
>> The tests were completely ad-hoc and did not use unittest or any other
>> library. They had a hand-rolled runner which ran all the functions like
>> test_one_one from a script.
>>
>> The odd thing is that Python 2.7 + py.test + the functools.wraps version
>> of
>> the decorators worked OK.
>>
>> Could it be that I have inadvertently turned the logging module on and
>> output from that is confusing the py.test runner?
>
> wouldn't think so.  Can you attach a zip file and state the dependencies
> so we can try to reproduce?  Or a repo-url?
>

Many thanks, I am reluctant to give you a repo-url since there is so
much code in there that is irrelevant to this issue it would be hard
to figure out what is going on.

The attached zip contains the minimum code to reproduce. If you run
"show_bug.sh" from the pytest-bug directory this will:

1) install the requirements via pip,

2) run a single test from vanilla python (should pass),

3) run the same test with py.test (should green at this stage) and

4) display some text explaining what to uncomment to reproduce the bug.

I have narrowed it down quite a bit, and it turns out that if you
comment out most of the code in base.py everything works just fine...
which is odd.

Thanks for your help,

Sarah

--
Sarah Mount, Senior Lecturer, University of Wolverhampton
website:  http://www.snim2.org/
twitter: @snim2