The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/tools/build/+/dd13f45ea2951efc75182c72f30705d9c0c9e22a

commit dd13f45ea2951efc75182c72f30705d9c0c9e22a
Author: Michael Achenbach <machenbach@chromium.org>
Date: Thu Dec 20 14:22:44 2018

[V8] Make test data mastername independent

This will make it easier to move those recipes to other consoles.

Bug: 916980
Change-Id: I91743f3a5064ae255c82ec82ac360e30bc2b69d3
Reviewed-on: https://chromium-review.googlesource.com/c/1386844
Reviewed-by: Sergiy Belozorov <sergiyb@chromium.org>
Commit-Queue: Michael Achenbach <machenbach@chromium.org>

[modify] https://crrev.com/dd13f45ea2951efc75182c72f30705d9c0c9e22a/scripts/slave/recipes/v8/auto_roll_v8_deps.py
[modify] https://crrev.com/dd13f45ea2951efc75182c72f30705d9c0c9e22a/scripts/slave/recipes/v8/auto_roll_push.py
[modify] https://crrev.com/dd13f45ea2951efc75182c72f30705d9c0c9e22a/scripts/slave/recipes/v8/auto_tag.py
[modify] https://crrev.com/dd13f45ea2951efc75182c72f30705d9c0c9e22a/scripts/slave/recipes/v8/auto_roll_deps.py

How should we continue? I'd like to move the fyi builders away from the main console. I see two options:

1. Move them to current fyi console.
2. Move them to a new console called fyi. Split the old fyi into chromium and node.js. Rename old chromium into something else, e.g. chromium.fyi.

I don't have a strong opinion here. Whichever way works best for developers. Maybe ask on v8-staff?

I can also just start with 1. I can still split fyi later. That's optional.

Ah. Sorry, I haven't realized this was a choice question. I think we should have a single FYI console. If it becomes too big, we can split it later as you suggested. I think ideally, few people should be looking at the FYI console.

Additionally, I think it would be useful to have the 'lkgr' console that includes all LKGR blockers. This would make it easier to view what's blocking LKGR and allow to deprecate the old HTML doc generated on the bot. WDYT?