As can be seen on github, this test case is failing since https://github.com/gentoo/portage/commit/b716e3591933300aa3eedff56ab92d54dd17c516. In ResolverPlayground.__init__(), we usually set up a fake "eprefix" and populate it with symlinks to essential binaries. However, this population gets skipped if the caller passes in a value for eprefix themselves. I think we should probably refactor the code that sets up the symlinks and call it where needed in the testSetCpv test case.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/proj/portage.git/commit/?id=44ea72efd7378cb26cb58cea7534449b1f4968c6 commit 44ea72efd7378cb26cb58cea7534449b1f4968c6 Author: Zac Medico <zmedico@gentoo.org> AuthorDate: 2022-07-25 21:36:16 +0000 Commit: Zac Medico <zmedico@gentoo.org> CommitDate: 2022-07-25 21:37:04 +0000 ResolverPlayground: unconditionally setup essential_binaries Closes: https://bugs.gentoo.org/861077 Signed-off-by: Zac Medico <zmedico@gentoo.org> lib/portage/tests/resolver/ResolverPlayground.py | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-)
