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

Issue 714977 link

Starred by 1 user
Status: Assigned
Owner:
cywang@chromium.org
Cc:
cywang@chromium.org
█ bccheng@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

Run telemetry unittest for ChromeOS

Project Member Reported by cywang@chromium.org, Apr 25 2017 
As there will be more ChromeOS specific logic in telemetry(e.g.  crbug.com/714803 ), we should have unit test running either on VM or real DUT for ChromeOS.

Comment 1 by cywang@chromium.org, Apr 25 2017 

BTW, the telemetry unit test could be invoked by  /usr/local/telemetry/src/tools/perf/run_telemetry_tests on a DUT.

Comment 2 by cywang@chromium.org, Apr 25 2017 

My bad, we did have the unit test running under VM - for example, https://luci-milo.appspot.com/buildbot/chromiumos.chromium/amd64-generic-telemetry/11351, search for 'telemetry_UnitTests' under VMTest stage.

Comment 3 by cywang@chromium.org, Apr 25 2017 

Since there are more than 10 failed unit tests, we probably need to address them
 first to reduce the flakiness of CrOS benchmarks/autotests.

Comment 4 by wuchengli@chromium.org, May 3 2018

Owner: cywang@chromium.org

Comment 5 by benhenry@chromium.org, Aug 3

Status: Assigned (was: Untriaged)
This bug has an owner, thus, it's been triaged. Changing status to "assigned".
►

Sign in to add a comment