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. 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.
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>
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.
--
Shaun
___________________________________________________________
Inbox full of spam? Get leading spam protection and 1GB storage with All New
Yahoo! Mail. http://uk.docs.yahoo.com/nowyoucan.html
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
