Autotests now log the chrome version as a test keyval.
For performance dashboards, it's helpful to know both the chromeOS version
number and the associated chrome version number for which a perf metric
was measured. For example, from the chrome version number, we can look up
the CL difference between two different chrome versions, helping in
debugging perf regressions that might have happened in chrome.
This change adds a new test keyval so that we can easily look up in the
autotest database to find the chrome version associated with an autotest
run (e.g., "CHROME_VERSION=27.0.1448.0").
BUG=chromium:190489
TEST=Verified on a local device that an autotest run with this change
properly logs the CHROME_VERSION into the test keyval file.
Change-Id: I6b0da1c6a9e28293214d3e2e01e71a62e4d78762
Reviewed-on: https://gerrit.chromium.org/gerrit/46202
Commit-Queue: Dennis Jeffrey <dennisjeffrey@chromium.org>
Reviewed-by: Dennis Jeffrey <dennisjeffrey@chromium.org>
Tested-by: Dennis Jeffrey <dennisjeffrey@chromium.org>
1 file changed