GitLab

So we could do "bisecting" and pin-point which experiment/feature triggers a
specific chrome behavior (say, a regression, a bug).

BUG=895142, 932197
TEST=unittest
R=mpearson@chromium.org

Change-Id: I2c76d73c72f093c8d884cc088495a04066e10687
Reviewed-on: https://chromium-review.googlesource.com/c/1335272
Commit-Queue: Zhenyao Mo <zmo@chromium.org>
Reviewed-by: Alexei Svitkine <asvitkine@chromium.org>
Cr-Commit-Position: refs/heads/master@{#636232}