Closed kdelee closed 6 years ago
stab # 2, see that @AlanCoding was working on this recently and had filed #14
Looks like those 5 tests are also failing for me on master FWIW
I made this PR to get a clean check in Travis https://github.com/jlaska/pytest-github/pull/17
python 2.7 gives
============== 5 failed, 53 passed, 12 warnings in 12.02 seconds ===============
yours gives
=============== 5 failed, 53 passed, 6 warnings in 5.90 seconds ================
the warnings may be due to the issue being fixed here.
yeah, that's right, this PR got rid of
/home/travis/build/jlaska/pytest-github/pytest_github/plugin.py:304: 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
issue_urls = tuple(sorted(set(marker.args))) # (O_O) for caching
Looks good to me!
I'll give this a few more min to see if I can address these failing tests, even though they appear to be stale for other reasons unrelated to these changes
Also FWIW -- I have pip installed this version and run test modules that use the github marker and all seems to be working
Thanks for the fix! Can we fix the tests too?
Working off master to diagnose these test failures...something is going on with
Re: our discussion I filed https://github.com/jlaska/pytest-github/issues/18 to track fixing those tests.
We have decided to merge these changes, which appear to have no effect on those existing issues
Thanks @kdelee! Merging this for now, and we can address potential test changes later.
See https://docs.pytest.org/en/latest/mark.html#updating-code for reference. This update resolves depreciation warnings for "get_marker".