tests: Properly initilize library in threads tests

This was already done in the torture_threads_pki.

Without the explicit initialization, we can observe random
failures tests (at least of the torture_threads_crypto) from
various threads.

Signed-off-by: Jakub Jelen <jjelen@redhat.com>
Reviewed-by: Andreas Schneider <asn@cryptomilk.org>

tests/unittests/torture_threads_buffer.c

@@ -589,8 +589,14 @@ int torture_run_tests(void)
         cmocka_unit_test(torture_mixed),
     };
 
+    /*
+     * If the library is statically linked, ssh_init() is not called
+     * automatically
+     */
+    ssh_init();
     torture_filter_tests(tests);
     rc = cmocka_run_group_tests(tests, NULL, NULL);
+    ssh_finalize();
 
     return rc;
 }

tests/unittests/torture_threads_crypto.c

@@ -175,7 +175,13 @@ int torture_run_tests(void)
         cmocka_unit_test(torture_crypto_aes256_cbc),
     };
 
+    /*
+     * If the library is statically linked, ssh_init() is not called
+     * automatically
+     */
+    ssh_init();
     rc = cmocka_run_group_tests(tests, NULL, NULL);
+    ssh_finalize();
 
     return rc;
 }

tests/unittests/torture_threads_init.c

@@ -88,8 +88,14 @@ int torture_run_tests(void)
         cmocka_unit_test(torture_ssh_init),
     };
 
+    /*
+     * If the library is statically linked, ssh_init() is not called
+     * automatically
+     */
+    ssh_init();
     torture_filter_tests(tests);
     rc = cmocka_run_group_tests(tests, NULL, NULL);
+    ssh_finalize();
 
     return rc;
 }