Ignore start time values matching kNoTimestamp.

Ignore start time values matching kNoTimestamp.

ClusterFuzz seems to have honed in on providing a timestamp equal
to std::numeric_limits<int64_t>::min(), which we use as a sentinal
value meaning kNoTimestamp. These should be ignored, similarly to
how we ignore AV_NOPTS_VALUE values when estimating start times.

BUG=700501
TEST=clusterfuzz test case passes.

Review-Url: https://codereview.chromium.org/2792193002
Cr-Commit-Position: refs/heads/master@{#461633}
Committed: https://chromium.googlesource.com/chromium/src/+/ebc9c38753d2c3736fa96018bea462c64d1e6602

[DaleCurtis, 2017-04-03 23:00:43]

dalecurtis@chromium.org changed reviewers:
+ tguilbert@chromium.org

[DaleCurtis, 2017-04-03 23:17:23]

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

[commit-bot: I haz the power, 2017-04-03 23:17:43]

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

[tguilbert, 2017-04-03 23:48:16]

LGTM

[DaleCurtis, 2017-04-04 00:09:47]

The CQ bit was unchecked by dalecurtis@chromium.org

[DaleCurtis, 2017-04-04 00:09:49]

The CQ bit was checked by dalecurtis@chromium.org

[commit-bot: I haz the power, 2017-04-04 00:10:04]

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-04 01:18:46]

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

[commit-bot: I haz the power, 2017-04-04 01:18:49]

Try jobs failed on following builders:
  linux_chromium_rel_ng on master.tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[DaleCurtis, 2017-04-04 01:52:43]

The CQ bit was checked by dalecurtis@chromium.org

[commit-bot: I haz the power, 2017-04-04 01:53:33]

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-04 05:03:14]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1491270763590520, "parent_rev":
"559bf6dabe17e1966e038175d43590cee78d6664", "commit_rev":
"ebc9c38753d2c3736fa96018bea462c64d1e6602"}

[commit-bot: I haz the power, 2017-04-04 05:04:13]

Description was changed from

==========
Ignore start time values matching kNoTimestamp.

ClusterFuzz seems to have honed in on providing a timestamp equal
to std::numeric_limits<int64_t>::min(), which we use as a sentinal
value meaning kNoTimestamp. These should be ignored, similarly to
how we ignore AV_NOPTS_VALUE values when estimating start times.

BUG=700501
TEST=clusterfuzz test case passes.
==========

to

==========
Ignore start time values matching kNoTimestamp.

ClusterFuzz seems to have honed in on providing a timestamp equal
to std::numeric_limits<int64_t>::min(), which we use as a sentinal
value meaning kNoTimestamp. These should be ignored, similarly to
how we ignore AV_NOPTS_VALUE values when estimating start times.

BUG=700501
TEST=clusterfuzz test case passes.

Review-Url: https://codereview.chromium.org/2792193002
Cr-Commit-Position: refs/heads/master@{#461633}
Committed:
https://chromium.googlesource.com/chromium/src/+/ebc9c38753d2c3736fa96018bea4...
==========

[commit-bot: I haz the power, 2017-04-04 05:04:14]

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