On Mar 21, 2012, at 10:16 AM, Bruce Korb wrote:
> Patch welcome! I, myself, don't know what "emit DejaGnu-style
> fixincludes.{sum, log} files" would mean.
Rather simple... In a file called fixinclude.sum, put
PASS: unique string
or
FAIL: unique string
one per line, as many times as you want. The unique strings should be
meaningful to you in some way, and be stable over long periods of time (no
`pwd` or `date` in them for example). You can write a python script, a awk
script, a bash script or a c program to generate this. You can synthesize this
from any source you can pull from, for example, the existing testing code or
test report you might have.
Bonus points if you can total passes and failures:
exec >>$file
echo
echo "# of expected passes $(cat $file | grep 'PASS:' | wc -l)"
echo "# of expected failures $(cat $file | grep 'FAIL:' | wc -l)"
at the end of the file. The above by the way, will add it (/bin/sh style), if
you just create the $file. That's it, done. For example, if you just had a
single, it all worked flawlessly thing, you could do:
if check-cmd; then
echo "PASS: fixinclude"
else
echo "FAIL: fixinclude"
fi
and then the code above, and viola, you're done. To create the .log file, cp
fixincludes.sum fixincludes.log, if you have nothing better to do.
