diff options
| author | 2019-03-18 13:54:36 +0100 | |
|---|---|---|
| committer | 2019-04-29 19:02:28 +0200 | |
| commit | 752dbe48e22aa749cbe63d52fda952108ae6249f (patch) | |
| tree | 56678ef768da005ff0dcec4bc2991afa65d4ead1 | |
| parent | btrfs: tests: fix comments about tested extent map ranges (diff) | |
| download | wireguard-linux-752dbe48e22aa749cbe63d52fda952108ae6249f.tar.xz wireguard-linux-752dbe48e22aa749cbe63d52fda952108ae6249f.zip | |
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>
| -rw-r--r-- | fs/btrfs/tests/extent-io-tests.c | 1 | ||||
| -rw-r--r-- | fs/btrfs/tests/free-space-tests.c | 1 |
2 files changed, 0 insertions, 2 deletions
diff --git a/fs/btrfs/tests/extent-io-tests.c b/fs/btrfs/tests/extent-io-tests.c index e88b7c9667f8..7bf4d5734dbe 100644 --- a/fs/btrfs/tests/extent-io-tests.c +++ b/fs/btrfs/tests/extent-io-tests.c @@ -444,6 +444,5 @@ int btrfs_test_extent_io(u32 sectorsize, u32 nodesize) ret = test_eb_bitmaps(sectorsize, nodesize); out: - test_msg("extent I/O tests finished"); return ret; } diff --git a/fs/btrfs/tests/free-space-tests.c b/fs/btrfs/tests/free-space-tests.c index dcbe526e5698..d0fdc94a5d61 100644 --- a/fs/btrfs/tests/free-space-tests.c +++ b/fs/btrfs/tests/free-space-tests.c @@ -876,6 +876,5 @@ out: btrfs_free_dummy_block_group(cache); btrfs_free_dummy_root(root); btrfs_free_dummy_fs_info(fs_info); - test_msg("free space cache tests finished"); return ret; } |
