"ebuild test" fails, while "make check" (from /var/tmp/portage/sys-devel/m4-1.4.12/work/m4-1.4.12/checks) succeeds. The test is effectively "echo -n | ../src/m4 -F /none/such" (freeze ending state to file /none/such) which succeeds, and it doesn't seem to run in a chroot, so I'm not sure why it's failing. Reproducible: Always Steps to Reproduce: 1. ebuild /usr/portage/sys-devel/m4/m4-1.4.12.ebuild test 2. 3. Actual Results: Checking ./196.using_froz @ ../doc/m4.texinfo:6843: Origin of test ./196.using_froz: stderr mismatch --- m4-tmp.4786/m4-xerr 2009-03-27 00:49:05.000000000 +0000 +++ m4-tmp.4786/m4-err 2009-03-27 00:49:05.000000000 +0000 @@ -1 +1 @@ -m4: cannot open `/none/such': No such file or directory +m4: cannot open `/none/such': Permission denied Checking ./197.extensions ... Checking ./stackovf.test Stack soft limit set to 300K Pass Failed checks were: ./196.using_froz:err make[2]: *** [check] Error 1 make[2]: Leaving directory `/var/tmp/portage/sys-devel/m4-1.4.12/work/m4-1.4.12/checks' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/sys-devel/m4-1.4.12/work/m4-1.4.12' make: *** [check] Error 2 * * ERROR: sys-devel/m4-1.4.12 failed. Workaround: rm /var/tmp/portage/sys-devel/m4-1.4.12/work/m4-1.4.12/checks/196.using_froz ebuild /usr/portage/sys-devel/m4/m4-1.4.12.ebuild merge
This is a sandbox issue, the program doesn't have write access to /none/such. If you run FEATURES="-sandbox -usersandbox' ebuild `equery which m4` test it works (for me anyhow). You aren't getting a sandbox violation, because the src_test function is wrapped in an addpredict /.
Created attachment 186374 [details, diff] ebuild patch A simple ebuild patch, to sed the offending path from /none/such to ./none/such, which also happens not to exist, but is in the sandbox.
*** This bug has been marked as a duplicate of bug 244396 ***
