socat tests are fails on my system, and according to bug 277104 it's sad, but old and expected behaviour for socat. Problem is, after switching EAPI from 4 (socat-1.7.2.2) to 5 (socat-1.7.2.3) it begins to run tests while emerge, and I think this happens because something is wrong in ebuild - probably it wasn't correctly converted to EAPI=5. My setup is somewhat unusual according to running tests because I want to run tests for most perl modules but not other packages. To accomplish this I'm using setup recommended to me in bug 482844: ### make.conf FEATURES="${FEATURES} test" ### profile/use.mask test ### profile/package.use.mask perl-core/* -test dev-perl/* -test # Mask USE=test per-package to override above and don't run tests for: dev-perl/Crypt-SSLeay test dev-perl/DBD-mysql test ... As you see, this way tests should be run only for most of perl packages but not other packages - with only exception for net-misc/socat at this time (actually, there are may be some other packages which also run tests but they won't fail and thus go unnoticed).
Nothing changed at all, really. If you want src_test() to be non-fatal, then simply set FEATURES=test-fail-continue. Bug #277104 comment #6 was never committed (c.f [1]). [1] http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/net-misc/socat/socat-1.7.2.2.ebuild?hideattic=0&view=markup *** This bug has been marked as a duplicate of bug 277104 ***
(In reply to Jeroen Roovers from comment #1) > Nothing changed at all, really. With EAPI=4 src_test() doesn't run in my configuration, but with EAPI=5 src_test() is executed - can you please explain why this happens?
