Diego Biurrun <[email protected]> writes: > In case of build failures accessing these files will generate error messages > that are annoying when running the FATE client through cron and add no value > since the build failure implies that these files will not get created. > --- > tests/fate.sh | 3 ++- > 1 files changed, 2 insertions(+), 1 deletions(-) > > diff --git a/tests/fate.sh b/tests/fate.sh > index 7519a06..b0df4df 100755 > --- a/tests/fate.sh > +++ b/tests/fate.sh > @@ -76,7 +76,8 @@ clean(){ > report(){ > date=$(date -u +%Y%m%d%H%M%S) > echo "fate:0:${date}:${slot}:${version}:$1:$2:${comment}" > report > - cat ${build}/config.fate ${build}/tests/data/fate/*.rep >> report > + cat ${build}/config.fate >> report > + cat ${build}/tests/data/fate/*.rep >> report 2> > /dev/null > test -n "$fate_recv" && $tar report *.log | gzip | $fate_recv > } > > --
This is done on top of a rejected whitespace patch. -- Måns Rullgård [email protected] _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
