Bug#30258342 ATRT DOES NOT STOP CLUSTER AFTER RUNNING TESTS

Modifies atrt to stop all processes after all the tests in a testsuite
are run.

Apart from cleaning up of processes after test run, it helps when atrt
restarts too fast and tries to define a process that has not yet been
undefined even though we have logic in CPCD to stop and undefine
processes once a "session" ends.

Approved by: Mauritz Sundell <[email protected]>

Change-Id: I0bd1b9f7f406018cf97ca195d627d033d0dc4ae1

Author: VarunNagaraju

storage/ndb/test/run-test/main.cpp

@@ -44,7 +44,7 @@
 
 #define PATH_SEPARATOR DIR_SEPARATOR
 #define TESTCASE_RETRIES_THRESHOLD_WARNING 5
-#define ATRT_VERSION_NUMBER 5
+#define ATRT_VERSION_NUMBER 6
 
 /** Global variables */
 static const char progname[] = "ndb_atrt";
@@ -405,6 +405,15 @@ int main(int argc, char **argv) {
     }
   }
 
+  /**
+   * Stopping all the processes after all the tests are run
+   */
+  if (!shutdown_processes(g_config, atrt_process::AP_ALL)) {
+    g_logger.critical("Failed to stop all processes");
+    return_code =
+        (return_code == TESTSUITE_SUCCESS) ? ATRT_FAILURE : return_code;
+  }
+
   if (g_report_file != 0) {
     fclose(g_report_file);
     g_report_file = 0;