New issue
Advanced search Search tips

Issue 696560 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Feb 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Allow bisects to go over a range where a metric was not registered in Telemetry

Project Member Reported by pasko@chromium.org, Feb 27 2017

Issue description

Not sure $subj is worth doing, here are my thoughts:

We would need to have telemetry at the latest version in the whole process of bisecting, and chrome be built at revisions that the bisect chooses, I thought it works this way.

In issue 661939 we found that we probably cannot pinpoint a single regression, but if we could, a working bisect would have helped (see comment 23 there). Priority of this - I don't know.
 
Status: WontFix (was: Assigned)
Guess it's a tradeoff to always pin or not pin Telemetry to a specific revision, and I think bisect has just historically err'd on the side of not pinning. But it makes cases like this difficult to track down. This is a nice wishlist item and something I can see in Pinpoint, I'll move it to Github.

https://github.com/catapult-project/catapult/issues/3298

Sign in to add a comment