------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 13.0-desktop-gnome_20170706-211748 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-5.4.0 * Available Python interpreters, in order of preference: [1] python3.4 [2] python2.7 (fallback)
Created attachment 481466 [details] emerge-info.txt
Created attachment 481468 [details] emerge-history.txt
Created attachment 481470 [details] environment
Created attachment 481472 [details] etc.portage.tbz2
Created attachment 481474 [details] logs.tbz2
Created attachment 481476 [details] sys-apps:sandbox-2.10-r4:20170706-192524.log
Created attachment 481478 [details] temp.tbz2
from the log: FAIL: mkdir("/", 777) = -1 (wanted -1); errno = EACCES:13 [Permission denied] (wanted EEXIST:17 [File exists]) that's weird because we have logic to check to see if paths exist and return EEXIST explicitly first. that failing would imply some path checks aren't working. [s] vapier@vapier $ ./mkdir-0 -1,EEXIST / 777 * absolute_path: .../sandbox/tests/mkdir-0 * resolved_path: .../sandbox/tests/mkdir-0 * ACCESS ALLOWED: execve: .../sandbox/tests/mkdir-0 * EARLY FAIL: mkdir(/[/]) @ lstat: Success PASS: mkdir("/", 1411) = -1 (wanted -1); errno = EEXIST:17 [File exists] (wanted EEXIST:17 [File exists]) does this failure happen consistently for you ? please re-open if so, and we can dig deeper into your setup.
