The output from sg-report-flight might in principle contain long
lines, although this is not expected. So we are going to want to feed
it through the new cr-fold-long-lines.
Rather than piping, we are going to keep a copy of the .report file,
like is done in mg-execute-flight. So for now, just make that change.
No overall change other than to leave behind the tmp/$flight.report
file. It will be tidied up by the usual cleanup processes.
Signed-off-by: Ian Jackson <ian.jackson@eu.citrix.com>
./sg-report-flight --html-dir=$flight_html_dir/$flight/ \
--allow=allow.all --allow=allow.$branch \
- $sgr_args $flight
+ $sgr_args $flight >tmp/$flight.report
+ cat tmp/$flight.report
mkdir -p $host_html_dir
with-lock-ex -w $globallockdir/report-lock \
if [ "x$OSSTEST_HTMLPUB_DIR" != x ]; then
sgr_args+=" --html-dir=$OSSTEST_HTMLPUB_DIR/$flight/"
fi
- ./sg-report-flight $sgr_args >&3 $flight
+ ./sg-report-flight $sgr_args $flight >tmp/$flight.report
+ cat tmp/$flight.report >&3
./cr-publish-flight-logs --push-harness $flight
fi
exec 3>&-