Re: Gnus automatic builds

[David Engster <deng@randomsample.de>]

Ted Zlatanov writes:
> On Wed, 06 Apr 2011 18:14:43 +0200 David Engster <deng@randomsample.de> wrote: 
>
> DE> OK, I've done that now. When invoking the rule 'fail-on-warning', the
> DE> build will be marked as failed for compile errors, and the most
> DE> important warnings are reported as errors as well. dgnushack will still
> DE> continue compiling, but in the end the build will be marked as failed.
>
> DE> The following warnings are currently enabled in dgnushack: 
>
> DE> 	  '(free-vars unresolved callargs redefine suspicious)
>
> DE> All other warnings will be ignored. If you want to see those, do 'make
> DE> warn' in the lisp subdirectory.
>
> Wonderful.  Can we set up a separate `make warn' build to go to just the
> Gnus developers individually, not the Ding mailing list?

I didn't plan on sending buildbot information to the ding mailing list,
but to the 'blamelist' only (meaning all people who committed since the
last build). I don't think failed builds are interesting enough for the
whole list. It's no problem to add people who always want to receive
mails, though.

As for 'make warn', I don't think it makes much sense to have a failed
builds for those warnings. There are simply too many (just try it).

> Also does it run the ERT tests?  I think it should, maybe as a separate
> target.  The registry.el and gnus-registry.el ERT tests write files to
> the filesystem (using `make-temp-file') but otherwise there are no side
> effects.

Not yet. I think we should use another Makefile rule for that. I'll see
to it that I add something, probably 'make check', which will then
depend on many smaller rules which run specific tests (like the registry
tests).

-David