Pierre van Rooden wrote:
> Michiel Meeuwissen wrote:
>
> >Sadly I sent a few too much yesterday, because I was testing the
> >script itself, and thinking that mailing did not work. I think it
> >sent all tests after I subscribed the nightly build user...
> >
> >
> I think it would be a good idea to send a periodical result of a run of
> the test cases.
I think it is senseless. If test-cases fail, they should be fixed the
next day. If that is not possible somewhy, we can see then. But to start
with, I think that must be the goal. Perhaps during heavy development we
could opt to turn the whole thing off again until a release is
approaching again.
> Preferably not too often though, once every two/three weeks or so?
> Also, it might be useful if the info is a bit more verbose.
Ok. Here's the bash I appended to the build script:
if [ -f last/tests-results.log ] ; then
if (( `cat last/tests-results.log | grep 'FAILURES' | wc -l` > 0 )) ; then
echo Failures, sending mail to ${MAILADDRESS}
cat last/tests-results.log | grep -E -A 1 '(FAILURES|^run\.)' | mutt
-s "Test cases failures on build ${version}" ${MAILADDRESS}
fi
else
echo Build failed, sending mail to ${MAILADDRESS}
echo -e "No test-cases available on build ${version}\n\nPerhaps the build
failed:\n\n" | tail -q -n 20 - last/messages.log last/errors.log | mutt -s
"Build failed ${version}" ${MAILADDRESS}
fi
Quite straight-forward. Improvements can be made. Go ahead. Send me the
(tested) script and I'll add it. Better yet, I think everyone can get the
account of the nightly build user and make it better themselves.
I'm not going to script statistical cumulation over two/three weeks
myself. I've better things to do, like e.g. fix those test-case failures
to make sure this mail does not appear tomorrow....
MIchiel
--
Michiel Meeuwissen mihxil'
Peperbus 111 MediaPark H'sum [] ()
+31 (0)35 6772979 nl_NL eo_XX en_US
_______________________________________________
Developers mailing list
[email protected]
http://lists.mmbase.org/mailman/listinfo/developers
