@@ -76,6 +76,8 @@ proc run-job {job} {
if {$ok && ![catch { info args prep-job/$jobinfo(recipe) }]} \
{ catching-otherwise fail prep-job/$jobinfo(recipe) }
+ if {$ok} { set syslog [spawn-ts broken = | ts-syslog-server] }
+
if {$ok && $need_build_host} \
{ catching-otherwise broken prepare-build-host }
@@ -99,6 +101,10 @@ proc run-job {job} {
run-ts !broken capture-logs ts-logs-capture + host
}
+ if {[info exists syslog]} {
+ reap-ts $syslog
+ }
+
if {$ok} {
if {[jobdb::job-check-escaped-steps $flight $job]} {
set ok 0
Every job now gets a syslog server, which starts up after host allocation. The server's address and port are recorded by ts-syslog-server in a runvar and can be used by subsequent test steps. Signed-off-by: Ian Jackson <ian.jackson@eu.citrix.com> --- v2: Change mistaken TESTID `.' to `='. `.' means literally `.'. Do not start ts-syslog-server if !$ok. Do not start ts-syslog-server if job is being truncated now. Use new | (stdin pipe) spawn-ts feature; avoids total failure. --- sg-run-job | 6 ++++++ 1 file changed, 6 insertions(+)