|
|
Chromium Code Reviews|
Created:
4 years ago by nhiroki Modified:
4 years ago Reviewers:
falken CC:
chromium-reviews, shimazu+worker_chromium.org, kinuko+worker_chromium.org, blink-reviews, horo+watch_chromium.org, falken+watch_chromium.org, blink-worker-reviews_chromium.org Target Ref:
refs/pending/heads/master Project:
chromium Visibility:
Public. |
DescriptionWorker: Refine pending activity management on InProcessWorkerMessagingProxy
This CL...
(1) renames m_workerGlobalScopeMayHavePendingActivities to
m_workerGlobalScopeHasPendingActivities. InProcessWorkerMessagingProxy
cannot know the exact current state of pending activities on the worker
context because it's in a separate thread, so the field name contained
'may'. This would be confusing and pointless from caller's point of view.
(2) stops checking m_unconfirmedMessageCount in hasPendingActivity() in favor of
m_workerGlobalScopeHasPendingActivities. When the count is greater than 0,
m_workerGlobalScopeHasPendingActivities should be true.
(3) removes workerGlobalScopeMayHavePendingActivity() from
InProcessWorkerMessagingProxyForTest because it's the same with
hasPendingActivity() after (2).
Note that this CL does not change behavior.
BUG=655089
Committed: https://crrev.com/9d2e15b7c11d53baa8226bad662b26663838e035
Cr-Commit-Position: refs/heads/master@{#436549}
Patch Set 1 #
Dependent Patchsets: Messages
Total messages: 24 (16 generated)
Description was changed from
==========
Worker: Refine pending activity management on InProcessWorkerMessagingProxy
BUG=655089
==========
to
==========
Worker: Refine pending activity management on InProcessWorkerMessagingProxy
This CL...
(1) renames m_workerGlobalScopeMayHavePendingActivities to
m_workerGlobalScopeHasPendingActivities. InProcessWorkerMessagingProxy
cannot know the exact current state of pending activities on the worker
context because it's in a separate thread, so the field name contained
'may'. This would be confusing and pointless.
(2) stops checking m_unconfirmedMessageCount in hasPendingActivity() because
when it's greater than 0, m_workerGlobalScopeHasPendingActivities should be
true.
(3) removes workerGlobalScopeMayHavePendingActivity() from
InProcessWorkerMessagingProxyForTest because it's the same with
hasPendingActivity() after (2).
BUG=655089
==========
The CQ bit was checked by nhiroki@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
Description was changed from
==========
Worker: Refine pending activity management on InProcessWorkerMessagingProxy
This CL...
(1) renames m_workerGlobalScopeMayHavePendingActivities to
m_workerGlobalScopeHasPendingActivities. InProcessWorkerMessagingProxy
cannot know the exact current state of pending activities on the worker
context because it's in a separate thread, so the field name contained
'may'. This would be confusing and pointless.
(2) stops checking m_unconfirmedMessageCount in hasPendingActivity() because
when it's greater than 0, m_workerGlobalScopeHasPendingActivities should be
true.
(3) removes workerGlobalScopeMayHavePendingActivity() from
InProcessWorkerMessagingProxyForTest because it's the same with
hasPendingActivity() after (2).
BUG=655089
==========
to
==========
Worker: Refine pending activity management on InProcessWorkerMessagingProxy
This CL...
(1) renames m_workerGlobalScopeMayHavePendingActivities to
m_workerGlobalScopeHasPendingActivities. InProcessWorkerMessagingProxy
cannot know the exact current state of pending activities on the worker
context because it's in a separate thread, so the field name contained
'may'. This would be confusing and pointless from caller's point of view.
(2) stops checking m_unconfirmedMessageCount in hasPendingActivity() in favor of
m_workerGlobalScopeHasPendingActivities. When the count is greater than 0,
m_workerGlobalScopeHasPendingActivities should be true.
(3) removes workerGlobalScopeMayHavePendingActivity() from
InProcessWorkerMessagingProxyForTest because it's the same with
hasPendingActivity() after (2).
BUG=655089
==========
Patchset #1 (id:1) has been deleted
The CQ bit was checked by nhiroki@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
nhiroki@chromium.org changed reviewers: + falken@chromium.org
PTAL. This CL is inspired from https://codereview.chromium.org/2553973002/#msg6
lgtm. Thanks this is a bit clearer. Add "This patch does not change behavior" in the CL description?
Description was changed from
==========
Worker: Refine pending activity management on InProcessWorkerMessagingProxy
This CL...
(1) renames m_workerGlobalScopeMayHavePendingActivities to
m_workerGlobalScopeHasPendingActivities. InProcessWorkerMessagingProxy
cannot know the exact current state of pending activities on the worker
context because it's in a separate thread, so the field name contained
'may'. This would be confusing and pointless from caller's point of view.
(2) stops checking m_unconfirmedMessageCount in hasPendingActivity() in favor of
m_workerGlobalScopeHasPendingActivities. When the count is greater than 0,
m_workerGlobalScopeHasPendingActivities should be true.
(3) removes workerGlobalScopeMayHavePendingActivity() from
InProcessWorkerMessagingProxyForTest because it's the same with
hasPendingActivity() after (2).
BUG=655089
==========
to
==========
Worker: Refine pending activity management on InProcessWorkerMessagingProxy
This CL...
(1) renames m_workerGlobalScopeMayHavePendingActivities to
m_workerGlobalScopeHasPendingActivities. InProcessWorkerMessagingProxy
cannot know the exact current state of pending activities on the worker
context because it's in a separate thread, so the field name contained
'may'. This would be confusing and pointless from caller's point of view.
(2) stops checking m_unconfirmedMessageCount in hasPendingActivity() in favor of
m_workerGlobalScopeHasPendingActivities. When the count is greater than 0,
m_workerGlobalScopeHasPendingActivities should be true.
(3) removes workerGlobalScopeMayHavePendingActivity() from
InProcessWorkerMessagingProxyForTest because it's the same with
hasPendingActivity() after (2).
Note that this CL does not change behavior.
BUG=655089
==========
On 2016/12/06 06:51:54, falken wrote: > lgtm. Thanks this is a bit clearer. Add "This patch does not change behavior" in > the CL description? Thank you. Updated.
The CQ bit was unchecked by nhiroki@chromium.org
The CQ bit was checked by nhiroki@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: mac_chromium_rel_ng on master.tryserver.chromium.mac (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_rel_...)
The CQ bit was checked by nhiroki@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
CQ is committing da patch.
Bot data: {"patchset_id": 20001, "attempt_start_ts": 1481011636587070,
"parent_rev": "ac9dc90695147c775c28c7021f9ede646d9e61a2", "commit_rev":
"3df7bd6f511be99d96bd20e40a878c4d3c803671"}
Message was sent while issue was closed.
Description was changed from
==========
Worker: Refine pending activity management on InProcessWorkerMessagingProxy
This CL...
(1) renames m_workerGlobalScopeMayHavePendingActivities to
m_workerGlobalScopeHasPendingActivities. InProcessWorkerMessagingProxy
cannot know the exact current state of pending activities on the worker
context because it's in a separate thread, so the field name contained
'may'. This would be confusing and pointless from caller's point of view.
(2) stops checking m_unconfirmedMessageCount in hasPendingActivity() in favor of
m_workerGlobalScopeHasPendingActivities. When the count is greater than 0,
m_workerGlobalScopeHasPendingActivities should be true.
(3) removes workerGlobalScopeMayHavePendingActivity() from
InProcessWorkerMessagingProxyForTest because it's the same with
hasPendingActivity() after (2).
Note that this CL does not change behavior.
BUG=655089
==========
to
==========
Worker: Refine pending activity management on InProcessWorkerMessagingProxy
This CL...
(1) renames m_workerGlobalScopeMayHavePendingActivities to
m_workerGlobalScopeHasPendingActivities. InProcessWorkerMessagingProxy
cannot know the exact current state of pending activities on the worker
context because it's in a separate thread, so the field name contained
'may'. This would be confusing and pointless from caller's point of view.
(2) stops checking m_unconfirmedMessageCount in hasPendingActivity() in favor of
m_workerGlobalScopeHasPendingActivities. When the count is greater than 0,
m_workerGlobalScopeHasPendingActivities should be true.
(3) removes workerGlobalScopeMayHavePendingActivity() from
InProcessWorkerMessagingProxyForTest because it's the same with
hasPendingActivity() after (2).
Note that this CL does not change behavior.
BUG=655089
==========
Message was sent while issue was closed.
Committed patchset #1 (id:20001)
Message was sent while issue was closed.
Description was changed from
==========
Worker: Refine pending activity management on InProcessWorkerMessagingProxy
This CL...
(1) renames m_workerGlobalScopeMayHavePendingActivities to
m_workerGlobalScopeHasPendingActivities. InProcessWorkerMessagingProxy
cannot know the exact current state of pending activities on the worker
context because it's in a separate thread, so the field name contained
'may'. This would be confusing and pointless from caller's point of view.
(2) stops checking m_unconfirmedMessageCount in hasPendingActivity() in favor of
m_workerGlobalScopeHasPendingActivities. When the count is greater than 0,
m_workerGlobalScopeHasPendingActivities should be true.
(3) removes workerGlobalScopeMayHavePendingActivity() from
InProcessWorkerMessagingProxyForTest because it's the same with
hasPendingActivity() after (2).
Note that this CL does not change behavior.
BUG=655089
==========
to
==========
Worker: Refine pending activity management on InProcessWorkerMessagingProxy
This CL...
(1) renames m_workerGlobalScopeMayHavePendingActivities to
m_workerGlobalScopeHasPendingActivities. InProcessWorkerMessagingProxy
cannot know the exact current state of pending activities on the worker
context because it's in a separate thread, so the field name contained
'may'. This would be confusing and pointless from caller's point of view.
(2) stops checking m_unconfirmedMessageCount in hasPendingActivity() in favor of
m_workerGlobalScopeHasPendingActivities. When the count is greater than 0,
m_workerGlobalScopeHasPendingActivities should be true.
(3) removes workerGlobalScopeMayHavePendingActivity() from
InProcessWorkerMessagingProxyForTest because it's the same with
hasPendingActivity() after (2).
Note that this CL does not change behavior.
BUG=655089
Committed: https://crrev.com/9d2e15b7c11d53baa8226bad662b26663838e035
Cr-Commit-Position: refs/heads/master@{#436549}
==========
Message was sent while issue was closed.
Patchset 1 (id:??) landed as https://crrev.com/9d2e15b7c11d53baa8226bad662b26663838e035 Cr-Commit-Position: refs/heads/master@{#436549} |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
