mirror of
https://github.com/linux-apfs/apfstests.git
synced 2026-05-01 15:01:44 -07:00
Eryu Guan
7898fdf670
Currently xfs/259 tests against TEST_DIR for CRC support status to decide whether 512 block size should be tested, which is wrong for this test, because configuration of TEST_DIR is not controlled by test harness and can be different to the configuration being used in the test. Fix it by reversing the block size order that's tested and capture the output of the actual mkfs command that is being tested, and determine if 512 byte block sizes should be tested based on that output. While we're at it, I think the test matrix can be enlarged as well, 4k, 2k, 1k and 512 block size can be tested in each fs size boundary, not only the minimum block size. Suggested-by: Dave Chinner <dchinner@redhat.com> Signed-off-by: Eryu Guan <eguan@redhat.com> Reviewed-by: Dave Chinner <dchinner@redhat.com> Signed-off-by: Dave Chinner <david@fromorbit.com>
18 lines
897 B
Plaintext
18 lines
897 B
Plaintext
QA output created by 259
|
|
Trying to make (4TB - 4096B) long xfs, block size 4096
|
|
Trying to make (4TB - 4096B) long xfs, block size 2048
|
|
Trying to make (4TB - 4096B) long xfs, block size 1024
|
|
Trying to make (4TB - 4096B) long xfs, block size 512
|
|
Trying to make (4TB - 2048B) long xfs, block size 4096
|
|
Trying to make (4TB - 2048B) long xfs, block size 2048
|
|
Trying to make (4TB - 2048B) long xfs, block size 1024
|
|
Trying to make (4TB - 2048B) long xfs, block size 512
|
|
Trying to make (4TB - 1024B) long xfs, block size 4096
|
|
Trying to make (4TB - 1024B) long xfs, block size 2048
|
|
Trying to make (4TB - 1024B) long xfs, block size 1024
|
|
Trying to make (4TB - 1024B) long xfs, block size 512
|
|
Trying to make (4TB - 512B) long xfs, block size 4096
|
|
Trying to make (4TB - 512B) long xfs, block size 2048
|
|
Trying to make (4TB - 512B) long xfs, block size 1024
|
|
Trying to make (4TB - 512B) long xfs, block size 512
|