host reuse fixes: Fix runvar entry for adhoc tasks

When processing an item from the host lifecycle table into the runvar,
we don't want to do all the processing of flight and job.  Instead, we
should simply put the ?<taskid> into the runvar.

Previously this would produce ?<taskid>: which the flight reporting
code would choke on.

Signed-off-by: Ian Jackson <iwj@xenproject.org>

diff --git a/Osstest/JobDB/Executive.pm b/Osstest/JobDB/Executive.pm
index 045551130642d213924087aad4b2b1a9ec30c68c..1dcf55ff8d6bd1bbe945f7a6375fd811bc1638b8 100644 (file)
--- a/Osstest/JobDB/Executive.pm
+++ b/Osstest/JobDB/Executive.pm
@@ -649,6 +649,11 @@ END
            }
            next if $tj_seen{$oisprepmark.$otj}++;
 
+           if (!defined $o->{flight}) {
+               push @lifecycle, "$omarks$otj";
+               next;
+           }
+
            if (!$omarks && !$olive && defined($o->{flight}) &&
                $ho->{Shared} &&
                $ho->{Shared}{Type} =~ m/^build-/ &&