WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED FIXED
85903
Show the chromium non-layout test bots in garden-o-matic
https://bugs.webkit.org/show_bug.cgi?id=85903
Summary
Show the chromium non-layout test bots in garden-o-matic
Ojan Vafai
Reported
2012-05-08 11:46:07 PDT
Show the chromium non-layout test bots in garden-o-matic
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
View All
Add attachment
proposed patch, testcase, etc.
Ojan Vafai
Comment 1
2012-05-08 11:47:17 PDT
Created
attachment 140755
[details]
Patch
Ojan Vafai
Comment 2
2012-05-08 11:48:12 PDT
Created
attachment 140756
[details]
screenshot
Eric Seidel (no email)
Comment 3
2012-05-08 15:26:48 PDT
Comment on
attachment 140755
[details]
Patch Seems reasonable to me. Adam is your best reviewer of course.
Adam Barth
Comment 4
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. :)
Ojan Vafai
Comment 5
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.
Ojan Vafai
Comment 6
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!).
Adam Barth
Comment 7
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.
Ojan Vafai
Comment 8
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.
WebKit Review Bot
Comment 9
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
>
WebKit Review Bot
Comment 10
2012-05-08 19:37:18 PDT
All reviewed patches have been landed. Closing bug.
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug