From 1ed693423d7a30c3810ddc1b6f052d376c8cd4e7 Mon Sep 17 00:00:00 2001 From: Gary Lockyer Date: Fri, 23 Feb 2018 15:03:20 +1300 Subject: ldb tests: fix null test on incorrect variable Fix up tests that were performing a null check on the wrong variable after a call to ldb_msg_new Signed-off-by: Gary Lockyer Reviewed-by: Andrew Bartlett Autobuild-User(master): Andrew Bartlett Autobuild-Date(master): Sat Feb 24 15:50:35 CET 2018 on sn-devel-144 --- lib/ldb/tests/ldb_mod_op_test.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/lib/ldb/tests/ldb_mod_op_test.c b/lib/ldb/tests/ldb_mod_op_test.c index cf2288c7bce..0190936231b 100644 --- a/lib/ldb/tests/ldb_mod_op_test.c +++ b/lib/ldb/tests/ldb_mod_op_test.c @@ -3226,7 +3226,7 @@ static void test_ldb_add_duplicate_value_to_unique_index(void **state) assert_int_equal(ret, LDB_SUCCESS); msg02 = ldb_msg_new(tmp_ctx); - assert_non_null(msg01); + assert_non_null(msg02); msg02->dn = ldb_dn_new_fmt(msg02, test_ctx->ldb, "dc=test02"); assert_non_null(msg02->dn); @@ -3267,7 +3267,7 @@ static void test_ldb_add_to_index_duplicates_allowed(void **state) assert_int_equal(ret, LDB_SUCCESS); msg02 = ldb_msg_new(tmp_ctx); - assert_non_null(msg01); + assert_non_null(msg02); msg02->dn = ldb_dn_new_fmt(msg02, test_ctx->ldb, "dc=test02"); assert_non_null(msg02->dn); -- cgit v1.2.1