The dev-perl/Apache-Test ebuild is interactive in asking which server is needed. It also causes various sandbox violations: Please provide a full path to (optional) 'apxs' executable or choose from the following options: [1] /usr/sbin/apxs [2] /usr/sbin/apxs2 [1] 2 [warning] rerunning '/usr/bin/perl /var/tmp/portage/Apache-Test-1.11/work/Apache-Test-1.11/t/TEST -bugreport -verbose=0' with new config opts /usr/sbin/apache2 -d /var/tmp/portage/Apache-Test-1.11/work/Apache-Test-1.11/t -f /var/tmp/portage/Apache-Test-1.11/work/Apache-Test-1.11/t/conf/httpd.conf -D APACHE2 using Apache/2.0.49 (prefork MPM) waiting 60 seconds for server to start: .... waiting 60 seconds for server to start: ok (waited 3 secs) server localhost:8529 started t/ping.......ok t/request....ok All tests successful. Files=2, Tests=12, 3 wallclock secs ( 2.43 cusr + 0.49 csys = 2.92 CPU) [warning] server localhost:8529 shutdown --------------------------- ACCESS VIOLATION SUMMARY --------------------------- LOG FILE = "/tmp/sandbox-dev-perl_-_Apache-Test-1.11-807.log" unlink: /var/run/cgisock unlink: /var/run/cgisock unlink: /var/run/cgisock unlink: /var/run/cgisock unlink: /var/run/cgisock --------------------------------------------------------------------------------
Paul, Will fix this before morning (catching up on unclaimed bugs). Solution will have to be two fold - the obvious fix for the apxs/apxs2 choice, and removing the SRC_TEST line completely (doesn't look like SKIP is being honored correctly) which will skip the tests that are causing the sandbox violation. And just in case you were going to ask - perl module tests are flaky at best, as in this case where they attempt to create filesystem sockets to connect to running apache servers.
Simply removing the SRC_TEST line works over here (the tests for this module appear to be flawed regardless). Can you confirm that removing that line fixes this for you?
It seems to work for me too.
