Summary: | sys-apps-coreutils-7.2 test failure | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Ryan Hill (RETIRED) <rhill> |
Component: | [OLD] Core system | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | kentnl |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | coreutils-7.2-mv-test-stdin.patch |
Description
Ryan Hill (RETIRED)
2009-04-01 02:13:19 UTC
it passed just fine for me you do have /dev/stdin right ? it should be a symlink to fd/0 ... I had thought it might have been sandboxy related, but this problem occurs for me with it either on OR off. If /dev/stdin did not exist the test would have been skipped: fail=0 ls /dev/stdin >/dev/null 2>&1 \ || skip_test_ 'there is no /dev/stdin file' The above code runs fine. mv f g < /dev/stdin > out 2>&1 & pid=$! Appears to be the problem. Out doesn't get created, so I'm guessing this is due to something related to bash-4 ( which, like many of the other facets he lists in his --info, I also have, cpu/arch/gcc-version ) Created attachment 187028 [details, diff]
coreutils-7.2-mv-test-stdin.patch
yes, i saw that change, but your system is still broken. /dev/stdin should exist and be a symlink to fd/0. we shouldnt ignore that. it is: dirtyepic@halo ~ $ ll /dev/stdin lrwxrwxrwx 1 root root 4 2009-03-31 23:25 /dev/stdin -> fd/0 dirtyepic@halo ~ $ ll /dev/fd/0 lrwx------ 1 dirtyepic users 64 2009-04-01 17:47 /dev/fd/0 -> /dev/pts/2 i did ask for that info originally :P added the patch to coreutils-7.2 then, thanks |