asyncio: mode=legacy collected 706 items / 1 error / 194 deselected / 512 selected ==================================== ERRORS ==================================== _______________________ ERROR collecting CONTRIBUTING.md _______________________ /usr/lib/python3.9/site-packages/_pytest/nodes.py:140: in _create return super().__call__(*k, **kw) ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_desktop_gnome_systemd-j4_test-20220327-230019 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-9.3.1 [2] x86_64-pc-linux-gnu-11.2.1 * clang/llvm (if any): clang version 14.0.0 Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/lib/llvm/14/bin /usr/lib/llvm/14 14.0.0 Python 3.9.12 Available Ruby profiles: [1] ruby26 (with Rubygems) [2] ruby27 (with Rubygems) [3] ruby31 (with Rubygems) * Available Rust versions: [1] rust-bin-1.59.0 [2] rust-1.59.0 * The following VMs are available for generation-2: *) Eclipse Temurin JDK 11.0.14_p9 [openjdk-bin-11] 2) Eclipse Temurin JDK 8.322_p06 [openjdk-bin-8] Available Java Virtual Machines: [1] openjdk-bin-8 [2] openjdk-bin-11 system-vm The Glorious Glasgow Haskell Compilation System, version 8.10.4 php cli: [1] php7.4 [2] php8.0 [3] php8.1 * HEAD of ::gentoo commit 613977c7cef51c6f015b8db49feb3bf36c332977 Author: Repository mirror & CI <repomirrorci@gentoo.org> Date: Mon Apr 4 13:04:43 2022 +0000 2022-04-04 13:04:42 UTC emerge -qpvO dev-vcs/pre-commit [ebuild N ] dev-vcs/pre-commit-2.17.0 USE="test" PYTHON_SINGLE_TARGET="python3_9 -python3_8 -python3_10"
Created attachment 768763 [details] emerge-info.txt
Created attachment 768764 [details] dev-vcs:pre-commit-2.17.0:20220404-140003.log
Created attachment 768765 [details] emerge-history.txt.bz2
Created attachment 768766 [details] environment
Created attachment 768767 [details] etc.portage.tar.bz2
Created attachment 768768 [details] temp.tar.bz2
Created attachment 768769 [details] tests.tar.bz2
In case this is confusing, this is likely the work of pytest-markdown (epytest -p no:markdown).
Does this still happen with 2.19.0?
(In reply to Marek Szuba from comment #9) > Does this still happen with 2.19.0? It probably would, but -p no:markdown was added to epytest by default in commit 607b95b7a1245b02224486e6871b783c5e858500, so ebuilds don't need to omit this themselves anymore