test/crimson: use ASSERT_EQ() for verify critial results

the following EXPECT_EQ() statements actually depends on this test.

Signed-off-by: Kefu Chai <kchai@redhat.com>

diff --git a/src/test/crimson/seastore/test_extmap_manager.cc b/src/test/crimson/seastore/test_extmap_manager.cc
index 5018170a9b57ee517d58c4538e0dd3f7ae5310be..9722bc5f74658670425fa163fe79f6718b07c764 100644 (file)
--- a/src/test/crimson/seastore/test_extmap_manager.cc
+++ b/src/test/crimson/seastore/test_extmap_manager.cc
@@ -110,7 +110,7 @@ struct extentmap_manager_test_t : public seastar_test_suite_t {
   void check_mappings(extmap_root_t &extmap_root, Transaction &t) {
     for (const auto& [lo, ext]: test_ext_mappings){
       const auto ext_list = find_extent(extmap_root, t, lo, ext.length);
-      EXPECT_EQ(ext_list.size(), 1);
+      ASSERT_EQ(ext_list.size(), 1);
       const auto& ext_map = ext_list.front();
       EXPECT_EQ(ext.laddr, ext_map.laddr);
       EXPECT_EQ(ext.length, ext_map.length);