Whoops. I included the script this time. Might be nice in contrib. Or
better yet, in sanity.sh so that the script automatically goes back and
runs a line-by-line pattern check when the first one fails. Maybe I'll
go back and do that later.
Derek
--
Derek Price CVS Solutions Architect ( http://CVSHome.org )
mailto:[EMAIL PROTECTED] OpenAvenue ( http://OpenAvenue.com )
--
Don't confuse me with the facts, my mind's already made up!
I thought I was staring at the check.logs from some failed sanity.sh
runs for way too long before spotting the lines which failed to match.
Anyway, I wrote this script to solve the problem. It'll take the path
to a check.log as an argument and tell you what's wrong with one of the
patterns in it. It prints mismatched lines on top of each other too,
which usually makes them much easier to scan. Pass in -a if you want it
to try and match against the alternate pattern.
I banged on it a bit and it seems to be reliable.
Derek
--
Derek Price CVS Solutions Architect ( http://CVSHome.org )
mailto:[EMAIL PROTECTED] OpenAvenue ( http://OpenAvenue.com )
--
He who laughs last thinks slowest.
debug.check.log.sh
