It's unclear who the correct owner of this is, so assigning to stevenjb to see if he can find one.

I have managed to avoid learning too much about waterfall configuration, so I cc'd a bunch of people who might be able to help?

dnj@ may be the best person to advise on how to do this, but I am not volunteering him to do the work :).

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chrome/tools/build/+/1862351ab6c7762bd7577d1fedaeae93fe405d46

commit 1862351ab6c7762bd7577d1fedaeae93fe405d46
Author: Dan Jacques <dnj@chromium.org>
Date: Wed Apr 05 02:00:26 2017

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chrome/tools/build_limited/scripts/slave/+/4dd8a7e2092b4001cce23dc89aa59cbc2ce4f585

commit 4dd8a7e2092b4001cce23dc89aa59cbc2ce4f585
Author: Dan Jacques <dnj@chromium.org>
Date: Thu Apr 06 21:10:36 2017

This has landed. stevenjb@, I did all of the legwork to set up the initial framework. Can you take over and tweak as-needed to make sure everything works as intended?

Um... I've only been following this from the distant sidelines.

dgarett@, are you in the loop here? Right now it looks like https://uberchromegw.corp.google.com/i/chromeos.chrome/waterfall is pretty badly broken?

It's not as bad as it looks. The currently running build set is looking good so far, actually. All previous ones were b/c the recipe roller was stuck; I unstuck it around 1PM.

@stevenjb, what is the status of this bug?

Looks like this was resolved? It's really beyond my ken, assigning to dnj@ since he knows the most about it as near as I can tell (not really sure why this was ever assigned to me), but marking fix because the waterfall seems to be working fine.