The Thunar file manager requires X11 to run its suite, something that cannot be done in portage. Reproducible: Always Steps to Reproduce: 1. emerge -1 thunar Actual Results: make[3]: Entering directory `/var/tmp/portage/xfce-base/thunar-0.9.3/work/Thunar-0.9.3/tests' Xlib: connection to ":0.0" refused by server Xlib: No protocol specified (lt-test-thunar-vfs-path:26967): Gtk-WARNING **: cannot open display: :0.0 FAIL: test-thunar-vfs-path [...] ERROR: xfce-base/thunar-0.9.3 failed. * Call stack: * ebuild.sh, line 49: Called src_test * environment, line 2572: Called die * The specific snippet of code: * Xemake check || die "emake check failed." * The die message: * emake check failed. Expected Results: Thunar merged into the system. The workaround is FEATURES='-test' emerge -1 thunar. Thunar also has a few non-graphical tests (for its internal database for example) in its suite. They pass on my system. I am a bit curious. What is the difference between Xemake and emake?
Created attachment 176057 [details] emerge --info
well, the difference between Xemake and emake is that Xemake spawns an Xvfb, so this problem shouldn't happen
Which means it does not work with an xorg-server compiled with the minimal USE flag, as Xvfb is not installed on my system. Thus, the problem is not the ebuild itself. I did a quick search about excluding tests and found nothing. Can you point me to the document, if such document exists, please?
(In reply to comment #3) > Which means it does not work with an xorg-server compiled with the minimal USE > flag, as Xvfb is not installed on my system. > > Thus, the problem is not the ebuild itself. I did a quick search about > excluding tests and found nothing. Can you point me to the document, if such > document exists, please? > Please post your build.log of the failure. I get "All 1 tests passed" when I compiled xorg-server with USE=minimal and do not have Xvfb on my system.
well, Xemake uses the running X when it's accessible, so it doesn't always require Xvfb. I'm not quite sure how we could fix this though, maybe let the virtualx skip/die/warn/whatever Xemake when it's unable to open any DISPLAY?
Sorry, not a clue. Still worksforme. please don't be offended because I am closing this bug. We have reached a stagnate point that will not resolve itself. =/
