On Mon, Mar 9, 2009 at 11:12 AM, Nicolas Sylvain <[email protected]>wrote:
> > > On Mon, Mar 9, 2009 at 10:59 AM, Darin Fisher <[email protected]> wrote: > >> On Mon, Mar 9, 2009 at 9:45 AM, Nicolas Sylvain <[email protected]>wrote: >> >>> >>> >>> On Mon, Mar 9, 2009 at 9:39 AM, Darin Fisher <[email protected]> wrote: >>> >>>> On Mon, Mar 9, 2009 at 9:38 AM, <[email protected]> wrote: >>>> >>>>> On Mon, 9 Mar 2009, Nicolas Sylvain wrote: >>>>> >>>>> > On Mon, Mar 9, 2009 at 9:10 AM, Darin Fisher <[email protected]> >>>>> wrote: >>>>> > >>>>> > > On Sun, Mar 8, 2009 at 4:58 PM, Adam Langley <[email protected]> >>>>> wrote: >>>>> > > >>>>> > >> >>>>> > >> On Sun, Mar 8, 2009 at 4:54 PM, Nicolas Sylvain < >>>>> [email protected]> >>>>> > >> wrote: >>>>> > >> > Hello, over the weekend I made some changes to the waterfall, >>>>> and you >>>>> > >> > might be interested. >>>>> > >> >>>>> > >> Firstly, thank you! This is great. >>>>> > >> >>>>> > > >>>>> > > Yes, thank you Nicolas!! >>>>> > > >>>>> > >> >>>>> > >> > Webkit Linux (dbg) : failed to compile, seems to be a problem >>>>> with the >>>>> > >> > machine. Someone in the Linux team should look at it. >>>>> > >> >>>>> > >> This is a shared object build and, sadly, the shared build is >>>>> often >>>>> > >> broken. Someone will get it green this week. (i.e. I'll do it if >>>>> > >> nobody else does). >>>>> > >> >>>>> > > >>>>> > > Shouldn't we move this builder to the FYI buildbot then? >>>>> > > >>>>> > >>>>> > We could. "Compiling chrome on linux in debug" seems important enough >>>>> > though. >>>>> > Is this shared object something that is used only on the bot? >>>>> >>>>> The Modules Linux (dbg) builder covers this case. >>>>> >>>>> I agree that this should be moved to the FYI buildbot until it's >>>>> stable. >>>>> That's why it hasn't been in the top bar. >>>>> >>>>> >>>> Thanks Tony. So, if something doesn't go in the top bar, then perhaps >>>> it should go to the FYI waterfall? >>>> >>> >>> Yes, in theory it should like that. >>> >>> I thought Webkit Linux (dbg) was going to be added to the top bar really >>> soon. >>> >>> I think purify ui tests is just waiting for a new version of purify >>> maybe? After that it should be easy enough to turn it green. >>> >>> I could also move valgrind to the FYI waterfall if we don't plan to make >>> progress and add it to the top bar anytime soon. >>> >>> There are 2 exceptions : "XP Perf - Single Core" and "Vista Perf - Single >>> Core". They are important enough, but too slow to be in the top bar, and >>> the chances that we introduce a bug that is single core only is really >>> small. >>> >> >> >> i'm not sure i understand why it helps to have the top-bar differ from the >> main set of columns. it seems like the goal is to have everything on the >> main waterfall stay green all the time, and the purpose of the top-bar is to >> allow people to see if everything is green without having to scroll >> horizontally. is there some other purpose of the top-bar that i'm missing? >> > > This is something I made up, so feel free to disagree, but : > > Top bar is for what the people need to look at after they make changes. > Since the waterfall is too big, they can just click the header of the top > bars to see a minimal version of the waterfall (chromium, webkit, modules). > My job is to make sure all builders there can cycle really fast (except > Chromium XP and reliability).... the goal is 10 minutes. This is an > aggressive goal, we might not get there, but at least it's not going to be > 30 minutes to 1 hour like it was last week. > > But I agree in general, if it's not on the top bar, it should be in the FYI > waterfall. > > The exception was for something that will never turn red, like single-core, > and is really slow to run. (It *can* turn red, but dual-core will be red > too, and it's already in the top bars). > > Nicolas > > (There is also a technical reason: I can't move single-core to the FYI > waterfall because I can't share a build from the builder if it's not in the > same waterfall). > > OK... thanks for the details. -Darin --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
