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 Stephen> Adrian's build-report already does a lot of this. If we have to do it Stephen> by post-processing the logs, then porting Adrian's regexps to Perl is Stephen> probably a good way to go. Perl starts up a good deal faster than Stephen> XEmacs. let me know what/how you want it done and i will give it a go :) Stephen> What would be nice is if we could get the error-reporting mechanism Stephen> tweaked so as not to warn about intentional features. This would Stephen> benefit both developers and others following the smoketests, and Stephen> ordinary users who just are building the packages. definatly the mozilla tinderbox thingy springs to mind it shouldnt be too tricky to implement maybe this would be a use for PHP ?? -- XEmacs Advocate | Do not try the patience of Wizards, Gentoo Devotee | for they are subtle and quick to anger. Perl Hacker | - Elric (Technomage) , Babylon 5. Apache God | <mailto:rendhalver at xemacs.org> <GnuPG KeyID: AE51D190>