Remove extra call to TimeUntilNextProcess from within Process.

Remove extra call to TimeUntilNextProcess from within Process.

I noticed while profiling calls to TimeUntilNextProcess.
It's benign, but the implementation seems to be done to accomodate the
test rather than the other way around, so I'm making the test behave
more like a ProcessThread would.

BUG=None

Review-Url: https://codereview.webrtc.org/2715133002
Cr-Commit-Position: refs/heads/master@{#16867}
Committed: https://chromium.googlesource.com/external/webrtc/+/ea5f06f7e6b317debb3030fd3b73ca5926eec0dd

[tommi, 2017-02-26 17:43:47]

tommi@webrtc.org changed reviewers:
+ stefan@webrtc.org

[tommi, 2017-02-26 17:43:53]

The CQ bit was checked by tommi@webrtc.org to run a CQ dry run

[commit-bot: I haz the power, 2017-02-26 17:44:00]

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

[commit-bot: I haz the power, 2017-02-26 18:19:08]

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

[commit-bot: I haz the power, 2017-02-26 18:19:09]

Dry run: This issue passed the CQ dry run.

[tommi, 2017-02-27 12:45:38]

tommi@webrtc.org changed reviewers:
+ terelius@webrtc.org
- stefan@webrtc.org

[tommi, 2017-02-27 12:45:38]

bjorn - since stefan is out, can you take a look?

[terelius, 2017-02-27 13:13:14]

lgtm

https://codereview.webrtc.org/2715133002/diff/1/webrtc/modules/remote_bitrate...
File
webrtc/modules/remote_bitrate_estimator/remote_bitrate_estimator_single_stream.cc
(left):

https://codereview.webrtc.org/2715133002/diff/1/webrtc/modules/remote_bitrate...
webrtc/modules/remote_bitrate_estimator/remote_bitrate_estimator_single_stream.cc:148:
}
So we can rely on the ProcessThread not calling Process too early?

[tommi, 2017-02-27 13:39:03]

https://codereview.webrtc.org/2715133002/diff/1/webrtc/modules/remote_bitrate...
File
webrtc/modules/remote_bitrate_estimator/remote_bitrate_estimator_single_stream.cc
(left):

https://codereview.webrtc.org/2715133002/diff/1/webrtc/modules/remote_bitrate...
webrtc/modules/remote_bitrate_estimator/remote_bitrate_estimator_single_stream.cc:148:
}
On 2017/02/27 13:13:14, terelius wrote:
> So we can rely on the ProcessThread not calling Process too early?

Yes. If Process() gets called when its not supposed to, then that would be a bug
in ProcessThread and all Module implementations should not have to protect
against such a bug.

[tommi, 2017-02-27 13:39:07]

The CQ bit was checked by tommi@webrtc.org

[commit-bot: I haz the power, 2017-02-27 13:39:09]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.webrtc.org/...

[commit-bot: I haz the power, 2017-02-27 13:41:24]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1488202747323590, "parent_rev":
"c20b9950ef8ba5202eb1c459ae0f03eeeb94545e", "commit_rev":
"ea5f06f7e6b317debb3030fd3b73ca5926eec0dd"}

[commit-bot: I haz the power, 2017-02-27 13:41:26]

Description was changed from

==========
Remove extra call to TimeUntilNextProcess from within Process.

I noticed while profiling calls to TimeUntilNextProcess.
It's benign, but the implementation seems to be done to accomodate the
test rather than the other way around, so I'm making the test behave
more like a ProcessThread would.

BUG=None
==========

to

==========
Remove extra call to TimeUntilNextProcess from within Process.

I noticed while profiling calls to TimeUntilNextProcess.
It's benign, but the implementation seems to be done to accomodate the
test rather than the other way around, so I'm making the test behave
more like a ProcessThread would.

BUG=None

Review-Url: https://codereview.webrtc.org/2715133002
Cr-Commit-Position: refs/heads/master@{#16867}
Committed:
https://chromium.googlesource.com/external/webrtc/+/ea5f06f7e6b317debb3030fd3...
==========

[commit-bot: I haz the power, 2017-02-27 13:41:27]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/external/webrtc/+/ea5f06f7e6b317debb3030fd3...