Hi CrOS (and ex-CrOS) folks; can any of you tell me if we still need this builder, given that it's been broken for 3 months? Please assign back to me once someone answers, otherwise I'll assume we don't need it in a few days ...

From my notes: "This runs browser_tests for buildspec pushes to Dev, Beta, and Release channels, so builds may alternate, e.g. between 50 and 51 (which is super confusing)."

-> ketakid@
+ more actual cros infra folks :)

It's probably bad that it has been failing since June 15...

Ping ... last call before I remove this builder from the master :).

This is the only builder that runs Chrome browser_tests on Dev/Beta/Release channels as near as I am aware. I would think that we would want to keep them?

Sounds like a scary thing to lose. I'd argue though that if it has been broken for 3 months and no one has fixed it, that it's not adding much value.

I'd also say that the last 3 months have been insane, so it's not surprising that we'd miss a bot going red. :-)

bhthompson@ and ketakid@ what do you think? Are TPMs making use of this bot?

If no one is up for owning it and keeping it green, we should kill it.

+josafat

I don't believe I have ever examined this builder before, I don't spend much time on the chromeos.chrome waterfall https://uberchromegw.corp.google.com/i/chromeos.chrome/waterfall is this waterfall watched more by the Chrome gardeners?

FWIW, if it can go purple for a few months without anyone notices, it is probably wasting electricity :(.

Let's kill it. stevenjb@ told me it's also really odd in how it bounces between channels and hard to interpret.

It sounds like having bots running these tests is something we might want, but if so we should staff it properly and build it correctly.

Souds OK to me. It was quite difficult to investigate failures and was often ignored for that reason even when it was working.

In theory, regular Chrome testing should include linux_chromeos (I would hope), so I'm not really sure what this was specifically designed to test, and since nobody seems to know or care, +1 to everything abodenha@ said.

Chrome gardeners (sheriffs) do not look at chromeos.* waterfalls.

I will assume the other bots on this waterfall are still needed, of course, but I will go ahead and remove this one.

The Chrome on Chrome OS gardeners (is there another context where 'gardener' is used?) do look at chromes.* waterfalls, and specifically look at this waterfall.

There used to be "WebKit gardeners", then there were "Blink gardeners", then we merged the repos, and now Chrome just has sheriffs and pixel wranglers :).

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

commit 37ca7442c790f5ff155820118a5faf8cb0d49b7c
Author: Dirk Pranke <dpranke@chromium.org>
Date: Thu Oct 05 01:23:09 2017

reassigning to dgarrett@ to restart the buildbot master so that the bot'll be gone.

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/infradata/master-manager/+/f9d164ef465e0e632229f6e1312ab16c13125529

commit f9d164ef465e0e632229f6e1312ab16c13125529
Author: Don Garrett <dgarrett@google.com>
Date: Mon Oct 09 20:25:11 2017

Restart is done, and the builder is gone.

Incidentally, a builder for caraline got added during the same restart.