mirror of
https://github.com/linux-apfs/apfstests.git
synced 2026-05-01 15:01:44 -07:00
fstests: _fail test by default when _scratch_mount fails
Previously _scratch_mount didn't check the mount status and most tests continue to run even if the mount failed (unless test checks for the mount status explicitly). This would result in running tests on the underlying filesystem (usually rootfs) and implicit test failures, and such failures can be annoying and are usually hard to debug. Now _fail test by default if _scratch_mount failed and introduce _try_scratch_mount for tests that need to check mount results themselves. Suggested-by: Andreas Gruenbacher <agruenba@redhat.com> Reviewed-by: Darrick J. Wong <darrick.wong@oracle.com> Reviewed-by: Andreas Gruenbacher <agruenba@redhat.com> Signed-off-by: Eryu Guan <eguan@redhat.com>
This commit is contained in:
+1
-1
@@ -43,7 +43,7 @@ _require_scratch_encryption()
|
||||
# Try to mount the filesystem. If this fails then either the kernel
|
||||
# isn't aware of encryption, or the mkfs options were not compatible
|
||||
# with encryption (e.g. ext4 with block size != PAGE_SIZE).
|
||||
if ! _scratch_mount &>>$seqres.full; then
|
||||
if ! _try_scratch_mount &>>$seqres.full; then
|
||||
_notrun "kernel is unaware of $FSTYP encryption feature," \
|
||||
"or mkfs options are not compatible with encryption"
|
||||
fi
|
||||
|
||||
Reference in New Issue
Block a user