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.
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.
