Allow users more control over variations |
|
Issue descriptionThere have been a number of situations where teams have spent days digging into reported issues only to eventually discover that the problem was triggered by a variation. Currently there's no easy way to work with users to isolate if a variation might be responsible for a problem or to figure out which one. We're frequently seeing cases where users (especially on dev) have dozens of variations enabled. That's awesome, as it means people are trying things and improving Chromium in data-driven ways, but it comes with a cost. I've had several instances lately where people on my team spent days investigating user reports only to find that a variation was responsible. Things that would be useful: An option/policy to allow users to disable all variations. Some ability to turn individual variations on/off or do a bisect. An easy way to track down the owner of a variation if it causes problems.
,
Aug 3 2016
Can you link to the cases? In the current world, chrome://version lists a user's variations and so when the contents of this page is provided in bug reports, at least the information is there. I agree that more could be done to make this better. An option to disable all variations actually exists via the --enable-benchmarking flag. (It has other side effects, but it's by design we don't have one that's just to disable variations as there's a risk someone will blog about it and a non trivial number of users start using it, causing issues for our ability to data driven development). In terms of turning on/off individual variations, we do have this ability, via --force-fieldtrials and --enable-features/--disable-features command line, but you need to know which ones you specifically want to target it. |
|
►
Sign in to add a comment |
|
Comment 1 by abodenha@chromium.org
, Aug 3 2016