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 <i...@xenproject.org>
---
Osstest/JobDB/Executive.pm | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/Osstest/JobDB/Executive.pm b/Osstest/JobDB/Executive.pm
index 04555113..1dcf55ff 100644
--- 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-/ &&
--
2.20.1
