Temporarily disable error detection for response_start.

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}
Committed: https://chromium.googlesource.com/chromium/src/+/e6ac8702b2d7c32e3a59f52ce9d9ceb34d7de8a3

[Bryan McQuade, 2017-04-28 20:11:46]

The CQ bit was checked by bmcquade@chromium.org to run a CQ dry run

[Bryan McQuade, 2017-04-28 20:12:28]

Description was changed from

==========
Temporarily disable error detection for response_start.

BUG=
==========

to

==========
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
==========

[commit-bot: I haz the power, 2017-04-28 20:12:58]

Dry run: CQ is trying da patch.

Follow status at:
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-04-28 21:36:39]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2017-04-28 21:36:40]

Dry run: This issue passed the CQ dry run.

[Bryan McQuade, 2017-05-08 18:33:55]

bmcquade@chromium.org changed reviewers:
+ jkarlin@chromium.org

[Bryan McQuade, 2017-05-08 18:34:11]

PTAL, thanks!

[nasko, 2017-05-08 18:43:06]

nasko@chromium.org changed reviewers:
+ nasko@chromium.org

[nasko, 2017-05-08 18:43:06]

LGTM

[jkarlin, 2017-05-10 14:43:20]

lgtm

[Bryan McQuade, 2017-05-10 15:12:51]

The CQ bit was checked by bmcquade@chromium.org

[commit-bot: I haz the power, 2017-05-10 15:13:46]

CQ is trying da patch.

Follow status at:
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-05-10 16:12:48]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1494429171974250, "parent_rev":
"2b22fb640f88f055ab951a8fdc18bf073a2af90f", "commit_rev":
"e6ac8702b2d7c32e3a59f52ce9d9ceb34d7de8a3"}

[commit-bot: I haz the power, 2017-05-10 16:12:56]

Description was changed from

==========
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
==========

to

==========
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}
Committed:
https://chromium.googlesource.com/chromium/src/+/e6ac8702b2d7c32e3a59f52ce9d9...
==========

[commit-bot: I haz the power, 2017-05-10 16:12:57]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/chromium/src/+/e6ac8702b2d7c32e3a59f52ce9d9...