New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 796660 link

Starred by 2 users

Issue metadata

Status: Untriaged
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

Migrate chrome-branded ToT clang builds to either chromium.perf.fyi or chrome.fyi

Project Member Reported by dpranke@chromium.org, Dec 20 2017

Issue description

Currently there are some official/chrome_branded builders on the chromium.clang waterfall, which are used to test ToT clang in the official configuration, and to look for size differences (compared to pinned clang); ideally they'd be testing perf regressions as well.

The logs from these bots need to be made non-public; this is easily done now by tweaking logdog configurations. As part of the LUCI build, we'll need to migrate these to "chrome" buckets (instead of chromium buckets) as well.

We'll still probably want official/non-chrome-branded public bots as well.
 
Project Member

Comment 1 by sheriffbot@chromium.org, Dec 21

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
This is still an issue, I think.
I think Eric put the new LUCI bots for our branded clang tot configs on a separate waterfall, so this may get fixed soon. I still hope we can have one dashboard that shows all the tot bots at once in the end, though.
I believe Milo supports internal-only consoles (dashboards) that show a mix of internal and external bots. jbudorick may be able to point at an existing one.
https://ci.chromium.org/p/chromium/g/chromium.perf/console is one, though I believe that's only because it's mixing public buildbots and private luci bots.

If your builder names can be public (and just the names), then your console configuration would live in https://chromium.googlesource.com/chromium/src/+/HEAD/infra/config/global/luci-milo.cfg and would reference builders from both the luci.chromium.ci and luci.chrome.ci buckets, with the latter being private and only visible to signed-in users.

Sign in to add a comment