remove QA scripts
QA related scripts should be either maintained out of the tree or come as enhancements to the sanity check scripts. Change-Id: I6dceed81f66b84cedad2dd84fd42d6b388de3468 Signed-off-by: Anas Nashif <anas.nashif@intel.com>
This commit is contained in:
parent
c0eaa66a5c
commit
edb24ef6eb
|
@ -1,2 +1,3 @@
|
|||
# Use standard security profile. (=> no need for a random number generator)
|
||||
CONFIG_ENHANCED_SECURITY=n
|
||||
CONFIG_STDOUT_CONSOLE=y
|
||||
|
|
|
@ -1,11 +0,0 @@
|
|||
sanity_chk/QA directory contains some scripts to be
|
||||
used by QA.
|
||||
|
||||
All the scripts are related to the output of the
|
||||
sanity_chk script.
|
||||
|
||||
See individual scripts for documentation.
|
||||
|
||||
Provides scripts used by QA engineers to speed
|
||||
analysis.
|
||||
|
|
@ -1,58 +0,0 @@
|
|||
#!/bin/bash
|
||||
#
|
||||
# chk_sanity
|
||||
#
|
||||
# first paramter is a file that has been captured by:
|
||||
# sanity_chk -A x86 -T gcc > sanity.out.txt 2>&1
|
||||
# or equivalent
|
||||
# second parameter contains the name of the data file.
|
||||
# The data file has the items to check.
|
||||
# Each line of the file is a different check.
|
||||
# The format is:
|
||||
# regular expression|count
|
||||
# for example:
|
||||
# ^VXMICRO EXECUTION PROJECT SUCCESSFUL$|114
|
||||
#
|
||||
# The expectation is that many different pattern
|
||||
# files will be created for different
|
||||
# configurations.
|
||||
#
|
||||
# usage example:
|
||||
# sanity_chk -A x86 -T gcc > sanity.out.txt
|
||||
# ./chk_sanity.sh sanity.out.txt patterns_sanity_x86_gcc.txt
|
||||
#
|
||||
# return code
|
||||
# 0 = no failures
|
||||
# non-zero = number of failures
|
||||
#
|
||||
usage()
|
||||
{
|
||||
echo Usage: chk_sanity captured_output_file pattern_file
|
||||
echo \tpattern file contains: regular expression\|count
|
||||
}
|
||||
|
||||
if [ ! -e "$1" ] ; then
|
||||
echo "ERROR input specifies an output file that does not exist"
|
||||
usage
|
||||
exit 1
|
||||
fi
|
||||
|
||||
if [ ! -e "$2" ] ; then
|
||||
echo "ERROR pattern file does not exist"
|
||||
usage
|
||||
exit 1
|
||||
fi
|
||||
|
||||
RTNCODE=0
|
||||
while read f; do
|
||||
RE_STR=`echo $f | cut -d "|" -f 1`
|
||||
COUNT=`echo $f | cut -d "|" -f 2`
|
||||
FOUND=`grep "${RE_STR}" $1 | wc -l`
|
||||
if [ $FOUND -ne $COUNT ] ; then
|
||||
echo FAIL for expression $RE_STR expected $COUNT instances but found $FOUND
|
||||
let "RTNCODE+=1"
|
||||
else
|
||||
echo PASS for expression $RE_STR
|
||||
fi
|
||||
done < $2
|
||||
exit $RTNCODE
|
|
@ -1,5 +0,0 @@
|
|||
VXMICRO PROJECT EXECUTION SUCCESSFUL$|82
|
||||
^Build complete\.$|110
|
||||
sysgen.*Generating.*node|89
|
||||
Fatal task error! Aborting task\.$|28
|
||||
Fatal fiber error! Aborting fiber\.$|2
|
|
@ -1,25 +0,0 @@
|
|||
#!/bin/bash
|
||||
#
|
||||
# reduce_sanity.sh
|
||||
#
|
||||
# There are lots of lines that are output
|
||||
# by sanity_chk that are not needed if the
|
||||
# reader is just skimming for errors.
|
||||
# This script removes lots of the most
|
||||
# obvious ones.
|
||||
#
|
||||
# Parameter one: input filename
|
||||
# Output to stdout
|
||||
#
|
||||
if [ ! -e "${1}" ] ; then
|
||||
echo ERROR filename with content required as parameter
|
||||
exit 1
|
||||
fi
|
||||
grep -v "^\[gcc\]" $1 | \
|
||||
grep -v "^\[Compiling\]" | \
|
||||
grep -v "^\[Linking\]" | \
|
||||
grep -v "^make\[.\]: Entering" | \
|
||||
grep -v "^make\[.\]: Leaving" | \
|
||||
grep -v "^Build complete\.$" | \
|
||||
grep -v "^Using [0-9]* threads" | \
|
||||
grep -v "\*-=\*-="
|
Loading…
Reference in a new issue