Bug 85903 - Show the chromium non-layout test bots in garden-o-matic
Summary: Show the chromium non-layout test bots in garden-o-matic
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: New Bugs (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Ojan Vafai
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-05-08 11:46 PDT by Ojan Vafai
Modified: 2012-05-08 19:37 PDT (History)
3 users (show)

See Also:


Attachments
Patch (6.80 KB, patch)
2012-05-08 11:47 PDT, Ojan Vafai
no flags Details | Formatted Diff | Diff
screenshot (8.94 KB, image/png)
2012-05-08 11:48 PDT, Ojan Vafai
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ojan Vafai 2012-05-08 11:46:07 PDT
Show the chromium non-layout test bots in garden-o-matic
Comment 1 Ojan Vafai 2012-05-08 11:47:17 PDT
Created attachment 140755 [details]
Patch
Comment 2 Ojan Vafai 2012-05-08 11:48:12 PDT
Created attachment 140756 [details]
screenshot
Comment 3 Eric Seidel (no email) 2012-05-08 15:26:48 PDT
Comment on attachment 140755 [details]
Patch

Seems reasonable to me.  Adam is your best reviewer of course.
Comment 4 Adam Barth 2012-05-08 16:54:08 PDT
I like the approach of iframing buildbot.  The label text seems a bit long, but maybe that's just because the screen shot is narrow?

Another approach is to just list the names of the bots when they fail (like we do for compile failures).  The gtest bots should already be in the JSON blob we fetch from the server, so it might just be a matter of grabbing the information out of there.

That said, if you the green/red approach better, that's fine too.  :)
Comment 5 Ojan Vafai 2012-05-08 18:39:58 PDT
(In reply to comment #4)
> I like the approach of iframing buildbot.  The label text seems a bit long, but maybe that's just because the screen shot is narrow?

I think it's just the screenshot being narrow.

> Another approach is to just list the names of the bots when they fail (like we do for compile failures).  The gtest bots should already be in the JSON blob we fetch from the server, so it might just be a matter of grabbing the information out of there.
> 
> That said, if you the green/red approach better, that's fine too.  :)

We could do that. I just did this because it was easy and visual. Text is more likely to get overlooked. I'll leave it like this for now, but if it bugs you, we can change it.
Comment 6 Ojan Vafai 2012-05-08 18:49:27 PDT
(In reply to comment #4)
> Another approach is to just list the names of the bots when they fail (like we do for compile failures).

Do we do this for compile failures? The Mac bots are not compiling right now and I don't see anything in garden-o-matic (as a result I missed this for a couple of hours!).
Comment 7 Adam Barth 2012-05-08 18:57:19 PDT
> Do we do this for compile failures? The Mac bots are not compiling right now and I don't see anything in garden-o-matic (as a result I missed this for a couple of hours!).

It should say something about "losing test coverage" near the top.
Comment 8 Ojan Vafai 2012-05-08 19:01:00 PDT
(In reply to comment #7)
> > Do we do this for compile failures? The Mac bots are not compiling right now and I don't see anything in garden-o-matic (as a result I missed this for a couple of hours!).
> 
> It should say something about "losing test coverage" near the top.

Nope. Nothing. Looks like this broke at some point.
Comment 9 WebKit Review Bot 2012-05-08 19:37:14 PDT
Comment on attachment 140755 [details]
Patch

Clearing flags on attachment: 140755

Committed r116483: <http://trac.webkit.org/changeset/116483>
Comment 10 WebKit Review Bot 2012-05-08 19:37:18 PDT
All reviewed patches have been landed.  Closing bug.