The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/e6ac8702b2d7c32e3a59f52ce9d9ceb34d7de8a3

commit e6ac8702b2d7c32e3a59f52ce9d9ceb34d7de8a3
Author: bmcquade <bmcquade@chromium.org>
Date: Wed May 10 16:12:42 2017

Temporarily disable error detection for response_start.

When browser side nav is enabled, we observe an increase in
INVALID_ORDER_RESPONSE_START_PARSE_START PageLoadTimingStatus errors,
indicating either that we have a parse start value, but no response start value
for a page load, or that we have both values, but response start is reported as
happening after parse start.

Either case is an error & we should figure out what's going on here and try to
fix.

As a first step, we'll disable this assertion just to see how much it corrects
other page load metrics to get us closer to metric counts being the same with
and without plznav being enabled.

BUG=716587

Review-Url: https://codereview.chromium.org/2851873002
Cr-Commit-Position: refs/heads/master@{#470595}

[modify] https://crrev.com/e6ac8702b2d7c32e3a59f52ce9d9ceb34d7de8a3/chrome/browser/page_load_metrics/page_load_tracker.cc