| Message ID | 20160704224838.GA18686@charon (mailing list archive) |
|---|---|
| State | Accepted |
| Headers | show |
On Mon, Jul 04, 2016 at 11:48:47PM +0100, Luis Henriques wrote: > If btrfs isn't in the path, this test will fail with: > > [TEST/misc] 006-image-on-missing-device > failed: btrfs fi show /dev/loop0 > test failed for case 006-image-on-missing-device > Makefile:226: recipe for target 'test-misc' failed > make: *** [test-misc] Error 1 > > Fix the test script by adding $TOP to the path. > > Signed-off-by: Luis Henriques <henrix@camandro.org> Applied, thanks. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
diff --git a/tests/misc-tests/006-image-on-missing-device/test.sh b/tests/misc-tests/006-image-on-missing-device/test.sh index 8680a707afbb..dd02d93e5fdd 100755 --- a/tests/misc-tests/006-image-on-missing-device/test.sh +++ b/tests/misc-tests/006-image-on-missing-device/test.sh @@ -61,12 +61,12 @@ test_run() run_check $SUDO_HELPER umount $TEST_MNT test_image_dump - run_check btrfs fi show $dev1 + run_check $TOP/btrfs fi show $dev1 # create a degraded raid1 filesystem, check must succeed # btrfs-image must not loop run_mayfail wipefs -a $dev2 run_check $SUDO_HELPER losetup -d $dev2 - run_check btrfs fi show $dev1 + run_check $TOP/btrfs fi show $dev1 test_image_dump }
If btrfs isn't in the path, this test will fail with: [TEST/misc] 006-image-on-missing-device failed: btrfs fi show /dev/loop0 test failed for case 006-image-on-missing-device Makefile:226: recipe for target 'test-misc' failed make: *** [test-misc] Error 1 Fix the test script by adding $TOP to the path. Signed-off-by: Luis Henriques <henrix@camandro.org> --- tests/misc-tests/006-image-on-missing-device/test.sh | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html