From 09b6668064bf985229121d2a8eac6fb3a133ae1e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Markus=20M=C3=A4kel=C3=A4?= Date: Tue, 1 May 2018 10:14:13 +0300 Subject: [PATCH] Ignore cleanup failures in sharding_load_data The dropping of the database should be done directly on all nodes, the same way it was created. --- maxscale-system-test/sharding_load_data.cpp | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/maxscale-system-test/sharding_load_data.cpp b/maxscale-system-test/sharding_load_data.cpp index 9e4ba10a9..224a5b3be 100644 --- a/maxscale-system-test/sharding_load_data.cpp +++ b/maxscale-system-test/sharding_load_data.cpp @@ -39,13 +39,10 @@ int main(int argc, char** argv) long total = execute_query_count_rows(test.maxscales->conn_rwsplit[0], "SELECT * FROM db1.t1"); test.add_result(total != 100, "Expected 100 rows, got %ld", total); - test.tprintf("Dropping tables and databases"); - - test.try_query(test.maxscales->conn_rwsplit[0], "DROP TABLE db1.t1"); - test.try_query(test.maxscales->conn_rwsplit[0], "DROP DATABASE db1"); - test.maxscales->close_maxscale_connections(0); + test.repl->execute_query_all_nodes("DROP DATABASE db1"); + // Remove the test data unlink("data.csv");