## ------------- ## ERROR: All 87 tests were run, 1 failed unexpectedly. ## -------------------------- ## ## testsuite.log was created. ## ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_systemd-test-20190706-171233 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-9.1.0 * Available Python interpreters, in order of preference: [1] python3.6 [2] python2.7 (fallback) emerge -qpvO sys-apps/sandbox [ebuild U ] sys-apps/sandbox-2.17 [2.13] ABI_X86="(32) (64) (-x32)"
Created attachment 582068 [details] emerge-info.txt
Created attachment 582070 [details] emerge-history.txt
Created attachment 582072 [details] environment
Created attachment 582074 [details] etc.portage.tbz2
Created attachment 582076 [details] logs.tbz2
Created attachment 582078 [details] sys-apps:sandbox-2.17:20190706-194713.log
Created attachment 582080 [details] temp.tbz2
Maybe a dup of bug #608304 but that claims to be on HPPA (only?)
> Please send `tests/testsuite.log' and all information you think might help: Can you extract and attach `tests/testsuite.log' as well? I wonder if it will shed some light.
(In reply to Sergei Trofimovich from comment #9) > > Please send `tests/testsuite.log' and all information you think might help: > > Can you extract and attach `tests/testsuite.log' as well? I wonder if it > will shed some light. Which is done automatically by the tinderbox scripts - the attachment name logs.tbz2 should be what you need ;)
Aha, looks like ptrace was not able to catch unlink(): 76. unlink_static.at:1: testing unlink_static/1 ... /var/tmp/portage/sys-apps/sandbox-2.17/work/sandbox-2.17/tests/unlink_static.at:1: \ env \ SANDBOX_LOG="$PWD/sandbox.log" \ sandbox.sh \ addpredict / \; \ addwrite "${PWD%/*}" \; \ set -x \; \ . $abs_top_srcdir/tests/unlink_static-1.sh stderr: + . /var/tmp/portage/sys-apps/sandbox-2.17/work/sandbox-2.17/tests/unlink_static-1.sh ++ '[' no = yes ']' ++ touch f ++ test -e f ++ adddeny /var/tmp/portage/sys-apps/sandbox-2.17/work/sandbox-2.17-abi_x86_64.amd64/tests/testsuite.dir/76 ++ export SANDBOX_DENY=:/var/tmp/portage/sys-apps/sandbox-2.17/work/sandbox-2.17-abi_x86_64.amd64/tests/testsuite.dir/76 ++ SANDBOX_DENY=:/var/tmp/portage/sys-apps/sandbox-2.17/work/sandbox-2.17-abi_x86_64.amd64/tests/testsuite.dir/76 ++ unlink_static-0 -1,EPERM f ++ exit 1 stdout: FAIL: unlink("f") = 0 (wanted -1); errno = Success:0 [Success] (wanted EPERM:1 [Operation not permitted]) /var/tmp/portage/sys-apps/sandbox-2.17/work/sandbox-2.17/tests/unlink_static.at:1: exit code was 1, expected 0 76. unlink_static.at:1: 76. unlink_static/1 (unlink_static.at:1): FAILED (unlink_static.at:1)
Is this test failure consistently reproducible for you? I wonder what syscall backs your unlink_static test both in test itself and in sandbox wrapper. Easiest way to check test itself is via strace: $ LANG=C strace ./sandbox-2.17-abi_x86_64.amd64/tests/unlink_static-0 -1,EPERM file On my working system the output is $ unlink("file") = -1 ENOENT (No such file or directory)
(In reply to Sergei Trofimovich from comment #12) > Is this test failure consistently reproducible for you? I wonder what > syscall backs your unlink_static test both in test itself and in sandbox > wrapper. > > Easiest way to check test itself is via strace: > > $ LANG=C strace ./sandbox-2.17-abi_x86_64.amd64/tests/unlink_static-0 > -1,EPERM file > > On my working system the output is > > $ unlink("file") = -1 ENOENT (No such file or > directory) well: All 87 tests were successful. >>> Completed testing sys-apps/sandbox-2.18 so this is fixed?
Probably either it's not fixed (some test race) or it was an environment problem (like other processes mangling source tree).
i rewrote the main loop for sandbox-2.26 to hopefully make it less flaky. please re-open if you still see this test fail with the latest release.
