I hotpatched the server to fix the exception but without the build steps, it's still not very useful. I'll try to get the build steps this week in.
Sample: http://build.chromium.org/buildbot/try-server/json/builders/linux/builds/10906?as_text=1 Remove the ?as_text=1 to receive it as application/json On Tue, Dec 8, 2009 at 4:22 PM, Marc-Antoine Ruel <mar...@chromium.org> wrote: > On Tue, Dec 8, 2009 at 4:13 PM, Evan Martin <e...@chromium.org> wrote: >> On Tue, Dec 8, 2009 at 11:21 AM, Bradley Nelson <bradnel...@google.com> >> wrote: >>> I've got a prototype summary view of the trybots up >>> at http://tryconsole.appspot.com/ >>> This will let you monitor/find your try jobs without digging through the >>> waterfall. >>> The text prompt lets you search (username / builder / change name). >>> The two summary graphs show load for the day, load for the hour. >>> I'd love suggestions on how to make this more useful. >> >> Not sure if it's exactly in this space, but it'd be nice to have the >> try script dump the URLs of the try servers involved. I would use >> this when trying a patch from someone else, so I could paste the try >> server URls into the code review. > > Will give you one soon. I'd have given it but I just realized it > throws an exception server side. > > M-A > -- Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev
