I've finally tracked down why it was failing to detect some try jobs. I've corrected it. Let me know if anyone sees evidence to the contrary.
-BradN On Tue, Dec 8, 2009 at 1: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. > -- Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev
