[diffoscope] 02/03: skip some tests that fails in jessie-backports

[Levente Polyak]

On September 17, 2016 6:02:00 PM GMT+02:00, Mattia Rizzolo <mattia at debian.org> wrote:
>how do I tell pytest over the command line to skip single tests?
>I could have done it that way through d/rules.
>

Something like
py.test -k 'not test_icc and not test_ppu'

That's how I do that for Arch Linux. Depending on what breaks or works again I simply alter that line. 


>
>> I would be happy to see this being solved in a different way.
>
>The solution is: fix the tests so they run on jessie(-bpo).  In the
>last weeks I've been doing so for some, those I couldn't manage, but
>decideded to release nonetheless and release anyway to avoid keeping so
>many changes in git, unreleased.
>
>
>As you noted I haven't done that commit in master, it's referenced on
>by
>this tag: I don't want it to proliferate.  If you really want to make
>that commit not being present in the next backport upload, please help
>making the test suite more resilient!
>

Well as long as it does not hit the master its quite up to the packaging maintainers of Debian (f. E. You) how to approach this, but I would have added the pytest skip lines rather then source changes. 
Right now I have zero time to help passing those tests on Jessie, my todo list is exploding. Sry. 


>
>
>¹ flames about this topic can be found in the debian's MLs.  according
>to some the advantages of '3.0 (native)' are null whereas there are
>only
>disadvantages.  I disagree there: I find doing stuff on native packages
>a lot easier than having to deal with versioned tarballs, but YMMV…


Well different people always have different opinions :p looks like im part of the non native subset. I'm not looking for flame, just providing feedback. I accepted that it is like this for diffoscope. 


Cheers and have a nice weekend, 
Levente