Description
pytest-nodev have a module blacklist
and an object blacklist
that is update with every release.
If the enabling pytest-nodev crashes of hangs the pytest process you have probably found a problem object that needs to be added to the blacklist. In order to identify the problem object remove all non essential options from the command line, in particular --candidates-fail
and -n
, and add -vv
instead. Any test line that doesn't end with xfail
is a good candidate, especially if it is the last line before the summary or the crash report. For example the following command hangs:
$ py.test -vv examples/test_rfc3986_parse.py --candidates-from-modules itertools
[...]
examples/test_rfc3986_parse.py::test_rfc3986_parse_basic[itertools:count] xfail
examples/test_rfc3986_parse.py::test_rfc3986_parse_full[itertools:count] xfail
examples/test_rfc3986_parse.py::test_rfc3986_parse_basic[itertools:cycle]
and this is a hint that itertools:cycle
causes the hang.
Comment here to submit objects that crash or hang during the candidate
fixture for review, be sure to mention the the full object name, usually the string in square brackets.