summaryrefslogtreecommitdiffstats
path: root/tests/test_uid_minus.out
diff options
context:
space:
mode:
authorTavian Barnes <tavianator@tavianator.com>2018-11-14 00:08:11 -0500
committerTavian Barnes <tavianator@tavianator.com>2018-11-14 00:08:11 -0500
commita8f7b6dbd743bc224e2a8616993c373e82072956 (patch)
tree4f1485d9ebea1bca3e8105f9a049169aa45f0aab /tests/test_uid_minus.out
parent4b60aafc1185164cf48a0627bc3b092c6a79b3bc (diff)
downloadbfs-a8f7b6dbd743bc224e2a8616993c373e82072956.tar.xz
tests: Don't assume find continues after filesystem loops
POSIX says > When it detects an infinite loop, find shall write a diagnostic > message to standard error and shall either recover its position in the > hierarchy or terminate. So make the 'links' folder not have any loops, and add a new 'loops' folder for testing the GNU/bfs behaviour.
Diffstat (limited to 'tests/test_uid_minus.out')
0 files changed, 0 insertions, 0 deletions