New issue
Advanced search Search tips

Issue 667877 link

Starred by 1 user

Issue metadata

Status: Archived
Owner:
Closed: Nov 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

provision metrics not working

Project Member Reported by akes...@chromium.org, Nov 22 2016

Issue description

Seems to be due to an erroneous field value being given to the resolve metric

11/21 19:21:59.288 INFO |     ts_mon_config:0150| Waiting for ts_mon flushing process to finish...
11/21 19:22:31.225 ERROR|           metrics:0247| Caught exception while flushing: Metric "chrome/infra/chromeos/autotest/resolve_devserver" was given field "devserver" with invalid value "<autotest_lib.client.common_lib.cros.dev_server.ImageServer object at 0x7f79fe9f2410>" (<class 'autotest_lib.client.common_lib.cros.dev_server.ImageServer'>).
 
Owner: ayatane@chromium.org
Status: Assigned (was: Untriaged)
This was due to a change by ayatane@, reverting.
The revert is here: https://chromium-review.googlesource.com/#/c/413664/

Note, I'm not sure we even need those metrics that you tried to add, we already have a resolve metric withing provision jobs chromeos/autotest/provision/resolve
This is for all instances of resolving devservers, not just for provision, but for, e.g., staging artifacts.
Status: Fixed (was: Assigned)
Fixed. http://shortn/_y0z1XaYEqX

Comment 5 by dchan@google.com, Mar 4 2017

Labels: VerifyIn-58

Comment 6 by dchan@google.com, Apr 17 2017

Labels: VerifyIn-59

Comment 7 by dchan@google.com, May 30 2017

Labels: VerifyIn-60

Comment 8 by dchan@chromium.org, Aug 1 2017

Labels: VerifyIn-61

Comment 9 by dchan@chromium.org, Oct 14 2017

Status: Archived (was: Fixed)

Sign in to add a comment