Index: runs.scm
==================================================================
--- runs.scm
+++ runs.scm
@@ -267,11 +267,12 @@
 		  (loop (car remtests)(cdr remtests)))))))
 
     (if (not (null? required-tests))
 	(debug:print 1 "INFO: Adding " required-tests " to the run queue"))
     ;; NOTE: these are all parent tests, items are not expanded yet.
-    (runs:run-tests-queue db run-id runname test-records keyvallst flags)))
+    (runs:run-tests-queue db run-id runname test-records keyvallst flags)
+    (debug:print 4 "INFO: All done by here")))
 
 (define (runs:run-tests-queue db run-id runname test-records keyvallst flags)
     ;; At this point the list of parent tests is expanded 
     ;; NB// Should expand items here and then insert into the run queue.
   (debug:print 5 "test-records: " test-records ", keyvallst: " keyvallst)
@@ -363,11 +364,14 @@
 	  (debug:print 0 "ERROR: Should not have a list of items in a test and the itemspath set - please report this")
 	  (exit 1))))
 	
       ;; we get here on "drop through" - loop for next test in queue
       (if (null? tal)
-	  (debug:print 1 "INFO: All tests launched")
+	  (begin
+	    ;; FIXME!!!! THIS SHOULD NOT REQUIRE AN EXIT!!!!!!!
+	    (debug:print 1 "INFO: All tests launched, exiting")
+	    (exit 0))
 	  (loop (car tal)(cdr tal))))))
 
 ;; parent-test is there as a placeholder for when parent-tests can be run as a setup step
 (define (run:test db run-id runname keyvallst test-record flags parent-test)
   ;; All these vars might be referenced by the testconfig file reader