From d47c1bca904c9f70f66b0ee789c05f20018386da Mon Sep 17 00:00:00 2001 From: Ian Jackson Date: Wed, 21 Oct 2020 18:38:51 +0100 Subject: [PATCH] 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 ? into the runvar. Previously this would produce ?: which the flight reporting code would choke on. Signed-off-by: Ian Jackson --- 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.39.5