Add detailed tracking for causes of invalid PageLoadTimings.

Add detailed tracking for causes of invalid PageLoadTimings.

In https://codereview.chromium.org/2804093002 we added additional error codes
to understand the root cause of ERR_BAD_TIMING_IPC. New data shows that
ERR_BAD_TIMING_IPC_INVALID_TIMING is the primary cause.

We know we are receiving invalid PageLoadTiming structs, but we don't yet know
the specific cause. This change adds more detailed error codes to get insight
here.

BUG=712033
Review-Url: https://codereview.chromium.org/2820943002
Cr-Commit-Position: refs/heads/master@{#465108}
Committed: https://chromium.googlesource.com/chromium/src/+/0c3532027893052475cd87ac0f6c758046f34415

[Bryan McQuade, 2017-04-16 11:57:39]

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

[commit-bot: I haz the power, 2017-04-16 11:57:41]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[Bryan McQuade, 2017-04-16 12:28:55]

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

[commit-bot: I haz the power, 2017-04-16 12:30:49]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[Bryan McQuade, 2017-04-16 12:50:03]

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

[commit-bot: I haz the power, 2017-04-16 12:50:08]

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-16 13:57:48]

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

[commit-bot: I haz the power, 2017-04-16 13:57:49]

Dry run: This issue passed the CQ dry run.

[Bryan McQuade, 2017-04-16 18:21:10]

Description was changed from

==========
Add detailed tracking for causes of invalid PageLoadTimings.

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

to

==========
Add detailed tracking for causes of invalid PageLoadTimings.

In https://codereview.chromium.org/2804093002 we added additional error codes
to understand the root cause of ERR_BAD_TIMING_IPC. New data shows that
ERR_BAD_TIMING_IPC_INVALID_TIMING is the primary cause.

We know we are receiving invalid PageLoadTiming structs, but we don't yet know
the specific cause. This change adds more detailed error codes to get insight
here.

BUG=712033
==========

[Bryan McQuade, 2017-04-17 13:00:02]

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

[Bryan McQuade, 2017-04-17 13:00:10]

PTAL

[Charlie Harrison, 2017-04-17 13:10:23]

LGTM

[Bryan McQuade, 2017-04-17 13:22:47]

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

[Bryan McQuade, 2017-04-17 13:23:00]

isherman, PTAL for histograms.xml, thanks!

[Ilya Sherman, 2017-04-18 00:11:03]

metrics lgtm, thanks

[Ilya Sherman, 2017-04-18 00:11:08]

The CQ bit was checked by isherman@chromium.org

[commit-bot: I haz the power, 2017-04-18 00:11:44]

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-18 02:34:53]

CQ is committing da patch.

Bot data: {"patchset_id": 40001, "attempt_start_ts": 1492474268030890,
"parent_rev": "2005039aad5bc2f06af06d26c4153fe4c53d1436", "commit_rev":
"0c3532027893052475cd87ac0f6c758046f34415"}

[commit-bot: I haz the power, 2017-04-18 02:35:05]

Description was changed from

==========
Add detailed tracking for causes of invalid PageLoadTimings.

In https://codereview.chromium.org/2804093002 we added additional error codes
to understand the root cause of ERR_BAD_TIMING_IPC. New data shows that
ERR_BAD_TIMING_IPC_INVALID_TIMING is the primary cause.

We know we are receiving invalid PageLoadTiming structs, but we don't yet know
the specific cause. This change adds more detailed error codes to get insight
here.

BUG=712033
==========

to

==========
Add detailed tracking for causes of invalid PageLoadTimings.

In https://codereview.chromium.org/2804093002 we added additional error codes
to understand the root cause of ERR_BAD_TIMING_IPC. New data shows that
ERR_BAD_TIMING_IPC_INVALID_TIMING is the primary cause.

We know we are receiving invalid PageLoadTiming structs, but we don't yet know
the specific cause. This change adds more detailed error codes to get insight
here.

BUG=712033

Review-Url: https://codereview.chromium.org/2820943002
Cr-Commit-Position: refs/heads/master@{#465108}
Committed:
https://chromium.googlesource.com/chromium/src/+/0c3532027893052475cd87ac0f6c...
==========

[commit-bot: I haz the power, 2017-04-18 02:35:15]

Committed patchset #3 (id:40001) as
https://chromium.googlesource.com/chromium/src/+/0c3532027893052475cd87ac0f6c...