provision metrics not working |
||||||
Issue descriptionSeems 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'>).
,
Nov 22 2016
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
,
Nov 22 2016
This is for all instances of resolving devservers, not just for provision, but for, e.g., staging artifacts.
,
Nov 23 2016
,
Mar 4 2017
,
Apr 17 2017
,
May 30 2017
,
Aug 1 2017
,
Oct 14 2017
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by akes...@chromium.org
, Nov 22 2016Status: Assigned (was: Untriaged)