file /var/tmp/portage/dev-python/jaraco-logging-1.5/work/jaraco.logging-1.5/jaraco/logging.py, line 14 def log_level(level_string): E fixture 'level_string' not found > available fixtures: cache, capfd, caplog, capsys, capturelog, cov, doctest_namespace, environ, metadata, mock, mocker, monkeypatch, pytestconfig, record_xml_property, recwarn, tmpdir, tmpdir_factory, worker_id, workspace > use 'pytest --fixtures [testpath]' for help on them. ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0-systemd_abi32+64-test_20180203-182621 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-7.3.0 * Available Python interpreters, in order of preference: [1] python3.5 [2] python2.7 (fallback) java-config: The following VMs are available for generation-2: *) IcedTea JDK 3.6.0 [icedtea-bin-8] Available Java Virtual Machines: [1] icedtea-bin-8 system-vm emerge -qpv dev-python/jaraco-logging [ebuild N ] dev-python/jaraco-logging-1.5 USE="{-test}" PYTHON_TARGETS="python2_7 python3_5 -python3_4"
Created attachment 518636 [details] emerge-info.txt
Created attachment 518638 [details] dev-python:jaraco-logging-1.5:20180208-180724.log
Created attachment 518640 [details] emerge-history.txt
Created attachment 518642 [details] environment
Created attachment 518644 [details] etc.portage.tbz2
Created attachment 518646 [details] temp.tbz2
pytest is acting like log_level is a test function which gets passed a fixture called "level_string" (it is not). It should just be running the doctest. I'll close this because I can't reproduce it even with the same pytest version as you.
