diff options
| author | Tavian Barnes <tavianator@tavianator.com> | 2023-10-14 08:55:57 -0400 |
|---|---|---|
| committer | Tavian Barnes <tavianator@tavianator.com> | 2023-10-14 08:55:57 -0400 |
| commit | ddb476bcd224f8c262d24981af48da2fc649f43d (patch) | |
| tree | 1e016328a9ee33c54d0e35e4ed85fbc675b6a280 /tests/bfs/closed_stdout.sh | |
| parent | 287c2c72afeb8fbf017cd62cc100b2d05dca0fae (diff) | |
| download | bfs-ddb476bcd224f8c262d24981af48da2fc649f43d.tar.xz | |
tests: Move closed_std* tests out of the POSIX group
POSIX actually says
> If the utility would be executed with file descriptor 0, 1, or 2
> closed, implementations may execute the utility with the file
> descriptor open to an unspecified file.
So we're not guaranteed to be able to detect the situation in the first
place. Add a best-effort check for these platforms and skip the test.
Link: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_09_01_01
Diffstat (limited to 'tests/bfs/closed_stdout.sh')
| -rw-r--r-- | tests/bfs/closed_stdout.sh | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/tests/bfs/closed_stdout.sh b/tests/bfs/closed_stdout.sh new file mode 100644 index 0000000..5b6f7c3 --- /dev/null +++ b/tests/bfs/closed_stdout.sh @@ -0,0 +1,4 @@ +# Check if the platform automatically re-opens stdout before we can +(bash -c echo >&-) && skip + +! invoke_bfs basic >&- |