If configure fails before config.fate is generated, these values will be
used and thus the generated report will be accepted by the FATE server.
---
This will address the issues I have had with Martin's fate instances.
tests/fate.sh | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/tests/fate.sh b/tests/fate.sh
index c93e20a464..03a3728006 100755
--- a/tests/fate.sh
+++ b/tests/fate.sh
@@ -84,7 +84,10 @@ clean(){
report(){
date=$(date -u +%Y%m%d%H%M%S)
echo "fate:1:${date}:${slot}:${version}:$1:$2:${branch}:${comment}" >report
- cat ${build}/avbuild/config.fate ${build}/tests/data/fate/*.rep >> report
2> /dev/null
+ test -e ${build}/avbuild/config.fate &&
+ cat ${build}/avbuild/config.fate >> report 2> /dev/null ||
+ echo config:unknown:unknown:unknown:unknown:unknown:unknown >> report
2> /dev/null
+ cat ${build}/tests/data/fate/*.rep >> report 2> /dev/null
test -n "$fate_recv" && $tar report *.log | gzip | $fate_recv
}
--
2.11.0
_______________________________________________
libav-devel mailing list
[email protected]
https://lists.libav.org/mailman/listinfo/libav-devel
