Star64_linux/fs/btrfs/tests
David Sterba 752dbe48e2 btrfs: tests: drop messages when some tests finish
The messages like 'extent I/O tests finished' are redundant, if the test
fails it's quite obvious in the log and hang is also noticeable. No
other then extent_io and free space tree tests print that so make it
consistent.

Signed-off-by: David Sterba <dsterba@suse.com>
2019-04-29 19:02:28 +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: drop messages when some tests finish 2019-04-29 19:02:28 +02:00
extent-map-tests.c btrfs: tests: fix comments about tested extent map ranges 2019-04-29 19:02:28 +02:00
free-space-tests.c btrfs: tests: drop messages when some tests finish 2019-04-29 19:02:28 +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