Bug 835087

Summary:	gnome-bases/nautilus-41.2 test failures due to app-misc/tracker tracker-sandbox problems
Product:	Gentoo Linux	Reporter:	Mart Raudsepp <leio>
Component:	Current packages	Assignee:	Gentoo Linux Gnome Desktop Team <gnome>
Status:	CONFIRMED ---
Severity:	normal
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Mart Raudsepp gentoo-dev

2022-03-13 21:21:57 UTC

nautilus tests fail on a tracker using test, because it launches a local tracker via tracker-sandbox that wouldn't have its tracker-miners scribble to the users tracker database.
This stuff is provided by app-misc/tracker trackertestutils stuff, which has some python handling trouble.

If diving into the nautilus test failure, it ends up calling this:

/usr/lib/python-exec/python3.10/python3 -m trackertestutils --prefix=/usr --store-tmpdir --index-recursive-tmpdir test/automated/displayless/test-nautilus-search-engine-tracker

which appears stuck during test run (iirc), but running it manually gives this:

/usr/lib/python-exec/python3.10/python3: No module named trackertestutils

The module itself is shipped in /usr/lib64/tracker-2.0/trackertestutils/ right now, so it doesn't see it. This is the likely underlying reason for the nautilus failure then.

There were also questions about app-misc/tracker python handling, and whether a python dep should be there always, or perhaps testutils should be installed via a USE flag which nautilus[test] would USE-dep on then too.

Comment 1 Mart Raudsepp gentoo-dev

2022-03-13 21:24:16 UTC

On second look, it's called with /usr/lib64/tracker-3.0/trackertestutils/tracker-sandbox, which sets up PYTHONPATH and then calls it. So python module handling is not actually the core reason and it's still a mystery.