Re: Automatic smoketests

Stephen> Adrian's build-report already does a lot of this. If we Stephen> have to do it by post-processing the logs, then porting Stephen> Adrian's regexps to Perl is probably a good way to go. Stephen> Perl starts up a good deal faster than XEmacs. Mats> Where can I find the code? I looked in CVS module Mats> xemacs-builds but didn't find anything. (find-library "build-report") Stephen> What would be nice is if we could get the error-reporting Stephen> mechanism tweaked so as not to warn about intentional Stephen> features. Mats> Could you elaborate? I know the logs are a bit hard to read Mats> and thus so far I have just considered the exit status from Mats> make as something that can be relied upon. XEmacs (at least from 21.4) supports three separate mechanisms for controlling error/warning: {display,log}-warning-minimum-level, {display,log}-warning-suppressed-classes, and some byte-compiler options. We should use these to suppress the warnings at the source rather than filter them out. Mats> Does adrians regexps spot problems by examining the logs and Yes. Mats> does it now find a little to much? No, it's pretty good about choosing what to include in build reports. Check out the xemacs-buildreports archives, and compare to your own beta.err from logging core builds and judge for yourself. But it's only applicable to the core builds at the moment, and I think it would need to be generalized in some ways before it could work for the packages. Eg, individual packages will probably want to ignore different warnings. -- Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Ask not how you can "do" free software business; ask what your business can "do for" free software.