Added more strict checks for fence sync counters.

Added more strict checks for fence sync counters.

R=piman@chromium.org
BUG=606112
CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:linux_optional_gpu_tests_rel;tryserver.chromium.mac:mac_optional_gpu_tests_rel;tryserver.chromium.win:win_optional_gpu_tests_rel

Committed: https://crrev.com/4d075d2b7a85c4c9c5fa8a0d5158f2e74f2d5b97
Cr-Commit-Position: refs/heads/master@{#390569}

[David Yen, 2016-04-28 21:22:35]

Description was changed from

==========
Added more strict checks for fence sync counters.

R=piman@chromium.org
BUG=606112
==========

to

==========
Added more strict checks for fence sync counters.

R=piman@chromium.org
BUG=606112
CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:linux_optional_gpu_tests_rel;tryserver.chromium.mac:mac_optional_gpu_tests_rel;tryserver.chromium.win:win_optional_gpu_tests_rel
==========

[David Yen, 2016-04-28 21:40:24]

This too didn't trigger any assertions locally, but I'll just leave them there
in case something happens flakily.

Is it possible we are not even setting up the lock in some case when we need it?

[David Yen, 2016-04-28 21:41:46]

On 2016/04/28 21:40:24, David Yen wrote:
> This too didn't trigger any assertions locally, but I'll just leave them there
> in case something happens flakily.
> 
> Is it possible we are not even setting up the lock in some case when we need
it?

Perhaps we should add a thread_checker when lock_ is NULL. What do you think
about this? This would not only work for contexts which are externally
synchronized, I don't think we have cases like that though do we?

[piman, 2016-04-28 23:29:48]

lgtm

[David Yen, 2016-04-29 00:37:26]

The CQ bit was checked by dyen@chromium.org

[David Yen, 2016-04-29 00:37:26]

The patchset sent to the CQ was uploaded after l-g-t-m from piman@chromium.org
Link to the patchset: https://codereview.chromium.org/1933473002/#ps60001
(title: "Add thread_checker header")

[commit-bot: I haz the power, 2016-04-29 00:37:42]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1933473002/60001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1933473002/60001

[commit-bot: I haz the power, 2016-04-29 01:54:07]

Committed patchset #4 (id:60001)

[commit-bot: I haz the power, 2016-04-30 17:23:39]

Patchset 4 (id:??) landed as
https://crrev.com/4d075d2b7a85c4c9c5fa8a0d5158f2e74f2d5b97
Cr-Commit-Position: refs/heads/master@{#390569}

[commit-bot: I haz the power, 2016-04-30 17:58:59]

Description was changed from

==========
Added more strict checks for fence sync counters.

R=piman@chromium.org
BUG=606112
CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:linux_optional_gpu_tests_rel;tryserver.chromium.mac:mac_optional_gpu_tests_rel;tryserver.chromium.win:win_optional_gpu_tests_rel
==========

to

==========
Added more strict checks for fence sync counters.

R=piman@chromium.org
BUG=606112
CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:linux_optional_gpu_tests_rel;tryserver.chromium.mac:mac_optional_gpu_tests_rel;tryserver.chromium.win:win_optional_gpu_tests_rel

Committed: https://crrev.com/4d075d2b7a85c4c9c5fa8a0d5158f2e74f2d5b97
Cr-Commit-Position: refs/heads/master@{#390569}
==========