On Thu, Mar 15, 2007 at 01:22:42PM +0000, Shaun McDonald wrote: > > On 15 Mar 2007, at 13:08, Frank Schönheit - Sun Microsystems Germany > wrote: > > >>I saw many CWS in the last weeks and only some of them are green on > >>all platforms. But I couldn't found one, without an error. > >>So what should be the rules to reject a CWS, when 50 errors are > >>shown, > >>but the color is green, or when 20 errors are shown and it is violet > >>or when 10 errors exists and it is red. > > > >That's in fact a problem. Those tinderbox stati in EIS have been > >introduced without extensive explanation. And personally, I don't > >believe in those stati when *all* platforms tell me about errors, wiht > >some fancy different colors, and I don't have a chance judging what > >errors there actually are (the link to the tinderbox doesn't really > >help, since the TB page doesn't show me the actual errors, nor does it > >tell me somebody I could ask about the errors. > > > >Ergo: Tinderbox in EIS is not really useful ATM, sorry. > > > Frank raises a very good point. If a CWS hasn't had a commit in the > last 400 hours, then you cannot find any information about the last > build that was completed.
That is not true. You still see the result (passed/failed). The log might not be available anymore, since that gets cleared using a cronjob that wipes out the files from the harddisk. But that doesn't matter either, since the buildslaves will rebuild the failed ones after 7-10 days anyway. And every cws that had a commit will be rebuilt as well. AND: you can use the "show previous # hours" multiple times to go even further back in time. > I would like to see on the status pages a > list of the last n builds produced on each platform, so that I can > easily see the information about any errors. the last #n builds are useless. Either your buildresult is still valid (no commit after the last build started), then you can see the status from the column heading (the color) By clicking on it you see when the last built was run. Or there have been commits in the meantime and in that case the results are no longer valid anyway. > I'll take an example for you: <http://go-oo.org/tinderbox/ > readme4macintel/status.html> from <http://eis.services.openoffice.org/ > EIS2/cws.ShowCWS?Path=SRC680%2Freadme4macintel> Everything green = no problems, and no commits in the meantime. Why would you want to rebuild that? http://go-oo.org/tinderbox/tinder.cgi?tree=readme4macintel&start-time=1170545401&display-hours=500 Will show the last builds Again: the logs are no longer available, but: If that cws would have had a failure or a commit, it would have been rebuilt in the meantime > The buildbot/tinderbox system is a great idea, but lacks in some very > important ways. These problems can be fixed, if we work together to > find the problems and then re-design the system to make it useful. Please name those problems. ciao Christian -- NP: Pantera - Regular People (Conceit) Join #qa.OpenOffice.org on irc.freenode.net --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
