New issue
Advanced search Search tips

Issue 754856 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 758065
Owner:
Closed: Aug 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug

Blocking:
issue 758065



Sign in to add a comment

Get Ozone Cros coverage of telemetry_unittests and telemetry_perf_unittests

Project Member Reported by jonr...@chromium.org, Aug 11 2017

Issue description

Currently the Mojo Chromium OS FYI bot is running both the telemetry_unittests and telemetry_perf_unittests:

https://build.chromium.org/p/chromium.fyi/builders/Mojo%20ChromiumOS?numbuilds=100

We would like to get both of these fully running under the correct CrOS config. Then we would bring them up on CrOS bots on the CQ.

Eventually we will enable them to also be ran with --mash and --mus, so that we can compare each of the configurations.
 
Blocking: 758065
Cc: achuith@chromium.org
Components: Tests>Telemetry
Labels: -Pri-3 Pri-2
moblab devices apparently aren't being properly detected as chromeos devices, and end up using LinuxPlatformBackend instead of CrOSPlatformBackend.

Comment 3 by sadrul@chromium.org, Aug 24 2017

These tests are not running on chromeos devices. They are running a chromeos build of chrome on linux (similar to a developer's workstation)
What are we trying to achieve here? Telemetry will (correctly) treat this browser as linux chrome, but it seems like this is not what we want?
Blocking: -758065
Mergedinto: 758065
Status: Duplicate (was: Available)
Blocking: 758065
Components: -MUS Internals>Services>WindowService

Sign in to add a comment