David Sterba ccfada1f65 btrfs: tests: return error from all extent map test cases ...

The way the extent map tests handle errors does not conform to the rest
of the suite, where the first failure is reported and then it stops.
Do the same now that we have the errors returned from all the functions.

Signed-off-by: David Sterba <dsterba@suse.com>

2019-04-29 19:02:27 +02:00

..

btrfs-tests.c

btrfs: tests: add table of most common errors

2019-04-29 19:02:25 +02:00

btrfs-tests.h

btrfs: tests: add table of most common errors

2019-04-29 19:02:25 +02:00

extent-buffer-tests.c

btrfs: tests: use standard error message after path allocation failure

2019-04-29 19:02:26 +02:00

extent-io-tests.c

btrfs: tests: properly initialize fs_info of extent buffer

2019-04-29 19:02:26 +02:00

extent-map-tests.c

btrfs: tests: return error from all extent map test cases

2019-04-29 19:02:27 +02:00

free-space-tests.c

btrfs: tests: use standard error message after block group allocation failure

2019-04-29 19:02:26 +02:00

free-space-tree-tests.c

btrfs: tests: use standard error message after block group allocation failure

2019-04-29 19:02:26 +02:00

inode-tests.c

btrfs: tests: use standard error message after inode allocation failure

2019-04-29 19:02:26 +02:00

qgroup-tests.c

btrfs: tests: use standard error message after path allocation failure

2019-04-29 19:02:26 +02:00