Re: Automatic smoketests

Stephen> Actually, I think they would if (1) the filters are good Stephen> so that the reports are short and "interesting" and (2) Stephen> there was a summary page or frame or so that gave Stephen> statistics on number of packages, number of builds, Stephen> errors, packages that give the most errors, maintainers Stephen> whose packages _never_ throw errors :-) etc. Stephen> This is a fairly hard problem, it will take a lot of Stephen> tweaking. But something to aim for. Rendhalver> sounds like a job for perl :) i have perl skill's if Rendhalver> you need them Adrian's build-report already does a lot of this. If we have to do it by post-processing the logs, then porting Adrian's regexps to Perl is probably a good way to go. Perl starts up a good deal faster than XEmacs. What would be nice is if we could get the error-reporting mechanism tweaked so as not to warn about intentional features. This would benefit both developers and others following the smoketests, and ordinary users who just are building the packages. -- 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.