Failure log -

[40/295] telemetry.internal.actions.repeatable_scroll_unittest.RepeatableScrollActionTest.testRepeatableScrollActionNoRepeats failed unexpectedly 4.5948s:
  Chrome build location for linux_x86_64 not found. Browser will be run without Flash.
  Traceback (most recent call last):
    File "/b/s/w/ir/third_party/catapult/telemetry/telemetry/testing/browser_test_case.py", line 39, in WrappedMethod
      method(self)
    File "/b/s/w/ir/third_party/catapult/telemetry/telemetry/internal/actions/repeatable_scroll_unittest.py", line 52, in testRepeatableScrollActionNoRepeats
      expected_scroll))
  AssertionError: scroll_position=96;expected 302

This hasn't been flaking on the CrOS bot for a while now. Marking as Untriaged and removing the sheriff label.

The test is flaky again:

https://ci.chromium.org/buildbot/chromium.chromiumos/linux-chromeos-rel/6948
https://ci.chromium.org/buildbot/chromium.chromiumos/linux-chromeos-rel/6941
https://ci.chromium.org/buildbot/chromium.chromiumos/linux-chromeos-rel/6914
https://ci.chromium.org/buildbot/chromium.chromiumos/linux-chromeos-rel/6911

It is already marked disabled via
"@decorators.Disabled('android', 'chromeos')".
I don't understand why the test is running.

I believe we're using the linux backend on linux-chromeos-rel

This is just another example of where telemetry running on linux-chromeos does not have an appropriate backend. It's using a linux backend when it needs a new one that supports chromeos on linux.

This should be revisited once we have a solution to that.

The plan is to get actual Chrome OS devices available as a part of the waterfall. We no longer wish to support a linux-chromeos configuration.