This is an auto-filled bug because dev-python/ptyprocess fails tests. The issue was originally discovered on ppc64, but it may be reproducible on other arches as well. If you think that a different summary clarifies the issue better, feel free to change it. Attached build log and emerge --info.
Created attachment 635852 [details] build.log build log and emerge --info
Now that is weird because pytest-fixture-config is definitely in pytest-virtualenv's deps.
Hmm, let me guess. You've just tested pytest-fixture-config...-r1, correct? Then I suppose Portage allowed you to break pytest-virtualenv's depgraph because it wasn't strictly pulled in by anything.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=6f3ce9bb87dae9eca368a404c9cd30f13ffd2b21 commit 6f3ce9bb87dae9eca368a404c9cd30f13ffd2b21 Author: Michał Górny <mgorny@gentoo.org> AuthorDate: 2020-05-03 19:49:13 +0000 Commit: Michał Górny <mgorny@gentoo.org> CommitDate: 2020-05-03 20:03:37 +0000 dev-python/pytest-fixture-config: Block py2 pytest-virtualenv Since dev-python/pytest normally loads all plugins, and PMs don't necessarily enforce dependencies of these that are not part of @world, it is possible to break their depgraph and break pytest on py2.7 completely. Add a blocker to make that harder. Closes: https://bugs.gentoo.org/720828 Signed-off-by: Michał Górny <mgorny@gentoo.org> .../pytest-fixture-config/pytest-fixture-config-1.7.0-r1.ebuild | 4 ++++ 1 file changed, 4 insertions(+)
*** Bug 720830 has been marked as a duplicate of this bug. ***
*** Bug 720824 has been marked as a duplicate of this bug. ***
