crucible-run: Add flag --no-separate-cleanup-threads

If separate cleanup threads are disabled, then each test's cleanup
handlers will run inside the test's "result" thread. If enabled, then
the "result" thread will create a new thread in which to run the cleanup
handlers.

Tested by:
    * Inspecting `crucible run --no-separate-cleanup-threads
      func.draw-indexed` in gdb.
    * Confirming the result totals are the same with and without
      --no-separate-cleanup-threads.

1 files changed, 13 insertions, 1 deletions

diff --git a/misc/crucible-completion.bash b/misc/crucible-completion.bash
index 018840d..f9db1d1 100644
--- a/misc/crucible-completion.bash
+++ b/misc/crucible-completion.bash
@@ -17,7 +17,19 @@ __crucible_ls_tests()
 
 __crucible_run()
 {
-   COMPREPLY=($(compgen -W "--help --fork --no-fork --dump --no-dump --no-cleanup --use-spir-v $($1 ls-tests)" -- ${COMP_WORDS[COMP_CWORD]}))
+   local flags="
+      --help
+      --fork
+      --no-fork
+      --separate-cleanup-threads
+      --no-separate-cleanup-threads
+      --dump
+      --no-dump
+      --no-cleanup
+      --use-spir-v
+   "
+
+   COMPREPLY=($(compgen -W "$flags $($1 ls-tests)" -- ${COMP_WORDS[COMP_CWORD]}))
 }
 
 __crucible()