Running this command and having a single test decorated with

@pytest.mark.integration

(defined in the

projectA

directory):

$ ./pants test :: --pytest-args='-m "integration"'

✓ projectA/tests/test_module.py:../projectA_tests succeeded.
𐄂 projectB/tests/test_module.py:../tests failed.
𐄂 projectC/tests/test_module.py:../tests failed.

$ echo $?
5

The pytest docs say:

pytest now exits with status code 5 in situations where no tests were run at all, such as the directory given in the command line does not contain any tests or as result of a command line option filters all out all tests

This makes sense and I find this to be reasonable. However, users may find it slightly confusing to see the red crosses with the

"failed"

status in the Pants output. Do you think we should instead have some other status such as

"skipped"

- I assume this happens because Pants thinks that

pytest

commands returning any other code than 0 have failed.

would still love the thoughts of others on having those test modules reporting

failed

despite not having any tests run…