SKIPPED module path is sometimes resolved, sometimes not #4677
Description
The module path when a test is skipped is sometimes relative, sometimes absolute. Whether a test was skipped with a pytest.skip() call or with a @pytest.mark.skip decoration seems to be one possible cause for discrepancy.
It would be nice to make a consistent decision here, but which is the right choice - absolute path or relative?
Click me to see an example
SKIPPED [1] /home/travis/build/pytest-dev/pytest/testing/deprecated_test.py:69: xdist workers disable the terminal reporter plugin
SKIPPED [1] testing/test_assertion.py:1158: This bug does not exist on PY3
SKIPPED [1] testing/test_assertrewrite.py:938: condition: sys.version_info[0] >= 3
SKIPPED [1] testing/test_assertrewrite.py:958: condition: sys.version_info[0] >= 3
SKIPPED [1] testing/test_assertrewrite.py:889: python 2 only
SKIPPED [1] testing/test_assertrewrite.py:947: condition: sys.version_info[0] >= 3
SKIPPED [1] testing/test_assertrewrite.py:969: condition: sys.version_info[0] >= 3
SKIPPED [1] testing/test_capture.py:554: only have capsysbinary in python 3
SKIPPED [1] testing/test_capture.py:883: python2 has no buffer
SKIPPED [2] testing/test_capture.py:1107: text output different for bytes on python3
SKIPPED [1] testing/test_capture.py:1371: only py3.6+ on windows
SKIPPED [1] /home/travis/build/pytest-dev/pytest/testing/test_doctest.py:1214: could not import 'mock'
SKIPPED [1] testing/test_monkeypatch.py:211: Python 2 only test
SKIPPED [1] testing/test_monkeypatch.py:219: Python 2 only test
SKIPPED [1] /home/travis/build/pytest-dev/pytest/testing/test_parseopt.py:306: need to be run with pytest executable, not -c
SKIPPED [31] /home/travis/build/pytest-dev/pytest/.tox/py37-xdist/lib/python3.7/site-packages/_pytest/pytester.py:1209: could not import 'pexpect'
SKIPPED [11] /home/travis/build/pytest-dev/pytest/testing/test_runner.py:429: could not import 'xdist.boxed'
SKIPPED [1] testing/test_skipping.py:52: condition: sys.version_info[0] >= 3
SKIPPED [1] testing/code/test_code.py:99: python 2 only issue
SKIPPED [1] /home/travis/build/pytest-dev/pytest/testing/code/test_excinfo.py:281: could not import 'decorator'
SKIPPED [1] /home/travis/build/pytest-dev/pytest/testing/code/test_excinfo.py:386: could not import 'jinja2'
SKIPPED [1] testing/test_tmpdir.py:223: win only
SKIPPED [8] /home/travis/build/pytest-dev/pytest/testing/test_unittest.py:398: could not import 'twisted.trial.unittest'
SKIPPED [5] /home/travis/build/pytest-dev/pytest/testing/python/approx.py:76: could not import 'numpy'
SKIPPED [1] /home/travis/build/pytest-dev/pytest/testing/python/approx.py:334: could not import 'numpy'
SKIPPED [1] /home/travis/build/pytest-dev/pytest/testing/python/approx.py:358: could not import 'numpy'
SKIPPED [1] /home/travis/build/pytest-dev/pytest/testing/python/approx.py:382: could not import 'numpy'
SKIPPED [1] /home/travis/build/pytest-dev/pytest/testing/python/approx.py:400: could not import 'numpy'
SKIPPED [1] /home/travis/build/pytest-dev/pytest/testing/python/approx.py:414: could not import 'numpy'
SKIPPED [1] /home/travis/build/pytest-dev/pytest/testing/python/approx.py:480: could not import 'numpy'
SKIPPED [1] /home/travis/build/pytest-dev/pytest/testing/python/approx.py:491: could not import 'numpy'
SKIPPED [1] /home/travis/build/pytest-dev/pytest/testing/test_unittest.py:940: could not import 'unittest2'
SKIPPED [1] testing/test_warnings.py:159: warnings message is broken as it is not str instance
SKIPPED [1] testing/test_warnings.py:571: Python 2 only issue
SKIPPED [1] /home/travis/build/pytest-dev/pytest/testing/python/integration.py:169: could not import 'mock'
SKIPPED [1] /home/travis/build/pytest-dev/pytest/testing/python/integration.py:192: could not import 'mock'
SKIPPED [1] /home/travis/build/pytest-dev/pytest/testing/python/integration.py:225: could not import 'mock'
SKIPPED [1] /home/travis/build/pytest-dev/pytest/testing/python/integration.py:249: could not import 'mock'