VEA Test: revert timestamp test

VEA Test: revert timestamp test

Reverting timestamp unit test in VEA would make the broken VEA tests
pass. I will fix the test in another CL.

BUG=614925
TEST=VEA tests pass

Committed: https://crrev.com/02baad155bcc05e6bac4034aa7897408dbee5260
Cr-Commit-Position: refs/heads/master@{#398521}

[shenghao, 2016-06-08 10:27:21]

Description was changed from

==========
VEA Test: revert timestamp test

Reverting timestamp unit test in VEA would make the broken VEA tests
pass. I will fix the test in another CL.

BUG=614925
TEST=VEA tests pass
==========

to

==========
VEA Test: revert timestamp test

Reverting timestamp unit test in VEA would make the broken VEA tests
pass. I will fix the test in another CL.

BUG=614925
TEST=VEA tests pass
==========

[shenghao, 2016-06-08 10:27:21]

shenghao@chromium.org changed reviewers:
+ kcwu@chromium.org, owenlin@chromium.org, posciak@chromium.org

[Pawel Osciak, 2016-06-08 10:38:18]

The CQ bit was checked by posciak@chromium.org

[Pawel Osciak, 2016-06-08 10:38:18]

lgtm

[commit-bot: I haz the power, 2016-06-08 10:38:25]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/2044203003/1

[commit-bot: I haz the power, 2016-06-08 11:53:17]

Description was changed from

==========
VEA Test: revert timestamp test

Reverting timestamp unit test in VEA would make the broken VEA tests
pass. I will fix the test in another CL.

BUG=614925
TEST=VEA tests pass
==========

to

==========
VEA Test: revert timestamp test

Reverting timestamp unit test in VEA would make the broken VEA tests
pass. I will fix the test in another CL.

BUG=614925
TEST=VEA tests pass
==========

[commit-bot: I haz the power, 2016-06-08 11:53:18]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-06-08 11:54:27]

Description was changed from

==========
VEA Test: revert timestamp test

Reverting timestamp unit test in VEA would make the broken VEA tests
pass. I will fix the test in another CL.

BUG=614925
TEST=VEA tests pass
==========

to

==========
VEA Test: revert timestamp test

Reverting timestamp unit test in VEA would make the broken VEA tests
pass. I will fix the test in another CL.

BUG=614925
TEST=VEA tests pass

Committed: https://crrev.com/02baad155bcc05e6bac4034aa7897408dbee5260
Cr-Commit-Position: refs/heads/master@{#398521}
==========

[commit-bot: I haz the power, 2016-06-08 11:54:28]

Patchset 1 (id:??) landed as
https://crrev.com/02baad155bcc05e6bac4034aa7897408dbee5260
Cr-Commit-Position: refs/heads/master@{#398521}

[wuchengli, 2016-06-15 08:59:19]

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

[wuchengli, 2016-06-15 08:59:21]

https://codereview.chromium.org/2044203003/diff/1/media/gpu/video_encode_acce...
File media/gpu/video_encode_accelerator_unittest.cc (left):

https://codereview.chromium.org/2044203003/diff/1/media/gpu/video_encode_acce...
media/gpu/video_encode_accelerator_unittest.cc:1240: ASSERT_EQ(timestamp,
frame_timestamps_.front());
Use EXPECT so the rest of this function can be run. We need to run the rest when
the timestamp is wrong.

EXPECT_FALSE(frame_timestamps_.empty());
if (!frame_timestamps_.empty()) {
  EXPECT_EQ(timestamp, frame_timestamps_.front());
  frame_timestamps_.pop();
}

https://codereview.chromium.org/2044203003/diff/1/media/gpu/video_encode_acce...
media/gpu/video_encode_accelerator_unittest.cc:1241: frame_timestamps_.pop();
One input buffer can generate more than one output buffers.

Say there are three input buffers -- 0, 0.033ms, 0.066ms. It generates four
output buffers. Both cases should pass: (1) 0, 0, 0.033, 0.066 and (2) 0, 0.033,
0.033, 0.066. But 0, 0.066, 0.033, 0.066 should fail.

https://codereview.chromium.org/2044203003/diff/1/media/gpu/video_encode_acce...
File media/gpu/video_encode_accelerator_unittest.cc (right):

https://codereview.chromium.org/2044203003/diff/1/media/gpu/video_encode_acce...
media/gpu/video_encode_accelerator_unittest.cc:1320: next_input_id_ *
base::Time::kMillisecondsPerSecond /
Better to use (next_input_id_ + 1) so the timestamp is not 0. By default,
timestamp is 0 and we won't catch if the first timestamp is wrong.