[U-Boot] [PATCH] test/py: Fix pytest4 deprecation warnings

[Marek Vasut]

On 3/13/19 12:25 PM, Tom Rini wrote:
> On Wed, Mar 13, 2019 at 12:20:49PM +0100, Marek Vasut wrote:
>> On 3/13/19 12:19 PM, Tom Rini wrote:
>>> On Wed, Mar 13, 2019 at 05:08:14AM +0100, Marek Vasut wrote:
>>>
>>>> Fix the following spit from pytest:
>>>>
>>>> u-boot/test/py/conftest.py:438: RemovedInPytest4Warning: MarkInfo objects are deprecated as they contain merged marks which are hard to deal with correctly.
>>>>   Please use node.get_closest_marker(name) or node.iter_markers(name).
>>>>   Docs: https://docs.pytest.org/en/latest/mark.html#updating-code
>>>>     for board in mark.args:
>>>>
>>>> In both cases, the later suggestion is applicable.
>>>>
>>>> Signed-off-by: Marek Vasut <marek.vasut+renesas at gmail.com>
>>>> Cc: Igor Opaniuk <igor.opaniuk at linaro.org>
>>>> Cc: Tom Rini <trini at konsulko.com>
>>>> Cc: Simon Glass <sjg at chromium.org>
>>>
>>> Deferred, for now we don't support newer pytest than 2.8.7 and you'll
>>> need to use virtualenv to set that up if needed.  There is not, AFAICT,
>>> a way to support both versions.
>>
>> That's what's in debian testing though, so maybe we need to support it
>> somehow.
> 
> Yes, I'm _very_ frustrated at the speed at which pytest went from "this
> is the API" to "this API is deprecated" to "this API doesn't work and
> here's the new, incompatible API".  Debian/testing needs to use
> virtualenv to setup a python area with older pytest installed, just like
> we do in .travis.yml.

Can't we rather have people use the new APIs and virtualenv new python?

> And wrt making our python stuff happier with newer versions, I'm far
> more worried about all of the python2-and-not-3 scripts we have
> currently. :(

Right

-- 
Best regards,
Marek Vasut