fs-test.sh: Update expected result output

Given 0dc1bfb730 ("fs: fat: cannot write to subdirectories") we have
changed how the FAT code works from creating the illegal file "./file"
and instead rejecting the path.  The correct behavior would be to write
"file" to "." but not writing an illegal file is a step in the right
direction.  For now, update the expected output to account for the
failure.

Signed-off-by: Tom Rini <trini@konsulko.com>
This commit is contained in:
Tom Rini 2018-07-30 16:06:04 -04:00
parent 406fd7e207
commit f437fea01c

View file

@ -12,13 +12,13 @@
# fs-test.fs.ext4.out: Summary: PASS: 24 FAIL: 0
# FAT16 tests:
# fs-test.sb.fat16.out: Summary: PASS: 24 FAIL: 0
# fs-test.fat16.out: Summary: PASS: 21 FAIL: 3
# fs-test.fs.fat16.out: Summary: PASS: 21 FAIL: 3
# fs-test.fat16.out: Summary: PASS: 20 FAIL: 4
# fs-test.fs.fat16.out: Summary: PASS: 20 FAIL: 4
# FAT32 tests:
# fs-test.sb.fat32.out: Summary: PASS: 24 FAIL: 0
# fs-test.fat32.out: Summary: PASS: 21 FAIL: 3
# fs-test.fs.fat32.out: Summary: PASS: 21 FAIL: 3
# Total Summary: TOTAL PASS: 204 TOTAL FAIL: 12
# fs-test.fat32.out: Summary: PASS: 20 FAIL: 4
# fs-test.fs.fat32.out: Summary: PASS: 20 FAIL: 4
# Total Summary: TOTAL PASS: 200 TOTAL FAIL: 16
# pre-requisite binaries list.
PREREQ_BINS="md5sum mkfs mount umount dd fallocate mkdir"