|
|
Created:
3 years, 10 months ago by Navid Zolghadr Modified:
3 years, 9 months ago CC:
chromium-reviews, blink-reviews Target Ref:
refs/pending/heads/master Project:
chromium Visibility:
Public. |
DescriptionRe-enable DCHECK for pointertypes of coalesced events
The modified DCHECK was failing on MAC when mouse was
leaving window due to the missing pointer type from
the event Chrome was receiveing from the OS. So we
were setting the pointerType to Unknown.
After the following fix:
https://chromium.googlesource.com/chromium/src/+/e97eb52977dd7ed3936227f0d240cfeed865e520
we have a heuristic in place to set the type to either
pen or mouse. So this DCHECK can be enabled again.
BUG=684292
Review-Url: https://codereview.chromium.org/2688793003
Cr-Commit-Position: refs/heads/master@{#450075}
Committed: https://chromium.googlesource.com/chromium/src/+/6b4cb83ed1e58193e8f3935ff406ce0ddb6310c6
Patch Set 1 #
Messages
Total messages: 38 (20 generated)
The CQ bit was checked by nzolghadr@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...
nzolghadr@chromium.org changed reviewers: + bokan@chromium.org, mustaq@chromium.org
lgtm
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: This issue passed the CQ dry run.
nzolghadr@chromium.org changed reviewers: + rbyers@chromium.org
LGTM
The CQ bit was checked by nzolghadr@chromium.org
Description was changed from ========== Re-enable DCHECK for pointertypes of coalesced events The modified DHECK was failing on MAC when mouse was leaving window due to the missing pointer type from the event Chrome was receiveing from the OS. So we were setting the pointerType to Unknown. After the following fix: https://chromium.googlesource.com/chromium/src/+/e97eb52977dd7ed3936227f0d240... we have a heuristic in place to set the type to either pen or mouse. So this DCHECK can be enabled again. BUG=684292 ========== to ========== Re-enable DCHECK for pointertypes of coalesced events The modified DCHECK was failing on MAC when mouse was leaving window due to the missing pointer type from the event Chrome was receiveing from the OS. So we were setting the pointerType to Unknown. After the following fix: https://chromium.googlesource.com/chromium/src/+/e97eb52977dd7ed3936227f0d240... we have a heuristic in place to set the type to either pen or mouse. So this DCHECK can be enabled again. BUG=684292 ==========
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": 1, "attempt_start_ts": 1487012853139900, "parent_rev": "853ae34d50f8322dbc272b7d92382a6a3ce3a0ab", "commit_rev": "6b4cb83ed1e58193e8f3935ff406ce0ddb6310c6"}
Message was sent while issue was closed.
Description was changed from ========== Re-enable DCHECK for pointertypes of coalesced events The modified DCHECK was failing on MAC when mouse was leaving window due to the missing pointer type from the event Chrome was receiveing from the OS. So we were setting the pointerType to Unknown. After the following fix: https://chromium.googlesource.com/chromium/src/+/e97eb52977dd7ed3936227f0d240... we have a heuristic in place to set the type to either pen or mouse. So this DCHECK can be enabled again. BUG=684292 ========== to ========== Re-enable DCHECK for pointertypes of coalesced events The modified DCHECK was failing on MAC when mouse was leaving window due to the missing pointer type from the event Chrome was receiveing from the OS. So we were setting the pointerType to Unknown. After the following fix: https://chromium.googlesource.com/chromium/src/+/e97eb52977dd7ed3936227f0d240... we have a heuristic in place to set the type to either pen or mouse. So this DCHECK can be enabled again. BUG=684292 Review-Url: https://codereview.chromium.org/2688793003 Cr-Commit-Position: refs/heads/master@{#450075} Committed: https://chromium.googlesource.com/chromium/src/+/6b4cb83ed1e58193e8f3935ff406... ==========
Message was sent while issue was closed.
Committed patchset #1 (id:1) as https://chromium.googlesource.com/chromium/src/+/6b4cb83ed1e58193e8f3935ff406...
Message was sent while issue was closed.
A revert of this CL (patchset #1 id:1) has been created in https://codereview.chromium.org/2706513002/ by alph@chromium.org. The reason for reverting is: Caused flakiness of WebRtcFromWebAccessibleResourceTest.GetUserMediaInWebAccessibleResourceFail https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9....
Message was sent while issue was closed.
Description was changed from ========== Re-enable DCHECK for pointertypes of coalesced events The modified DCHECK was failing on MAC when mouse was leaving window due to the missing pointer type from the event Chrome was receiveing from the OS. So we were setting the pointerType to Unknown. After the following fix: https://chromium.googlesource.com/chromium/src/+/e97eb52977dd7ed3936227f0d240... we have a heuristic in place to set the type to either pen or mouse. So this DCHECK can be enabled again. BUG=684292 Review-Url: https://codereview.chromium.org/2688793003 Cr-Commit-Position: refs/heads/master@{#450075} Committed: https://chromium.googlesource.com/chromium/src/+/6b4cb83ed1e58193e8f3935ff406... ========== to ========== Re-enable DCHECK for pointertypes of coalesced events The modified DCHECK was failing on MAC when mouse was leaving window due to the missing pointer type from the event Chrome was receiveing from the OS. So we were setting the pointerType to Unknown. After the following fix: https://chromium.googlesource.com/chromium/src/+/e97eb52977dd7ed3936227f0d240... we have a heuristic in place to set the type to either pen or mouse. So this DCHECK can be enabled again. BUG=684292 Review-Url: https://codereview.chromium.org/2688793003 Cr-Commit-Position: refs/heads/master@{#450075} Committed: https://chromium.googlesource.com/chromium/src/+/6b4cb83ed1e58193e8f3935ff406... ==========
On 2017/02/17 19:35:07, alph wrote: > A revert of this CL (patchset #1 id:1) has been created in > https://codereview.chromium.org/2706513002/ by mailto:alph@chromium.org. > > The reason for reverting is: Caused flakiness of > WebRtcFromWebAccessibleResourceTest.GetUserMediaInWebAccessibleResourceFail > > https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9.... Turned out that it was other DCHECK was failing, the one about matching ids. So I'm relanding the patch.
The CQ bit was checked by alph@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
alph@chromium.org changed reviewers: - alph@chromium.org
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: cast_shell_linux on master.tryserver.chromium.linux (JOB_TIMED_OUT, no build URL) chromeos_amd64-generic_chromium_compile_only_ng on master.tryserver.chromium.linux (JOB_TIMED_OUT, no build URL) chromeos_daisy_chromium_compile_only_ng on master.tryserver.chromium.linux (JOB_TIMED_OUT, no build URL) linux_chromium_asan_rel_ng on master.tryserver.chromium.linux (JOB_TIMED_OUT, no build URL) linux_chromium_chromeos_rel_ng on master.tryserver.chromium.linux (JOB_TIMED_OUT, no build URL) linux_chromium_rel_ng on master.tryserver.chromium.linux (JOB_TIMED_OUT, no build URL)
The CQ bit was checked by alph@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
Exceeded global retry quota
The CQ bit was checked by alph@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: chromium_presubmit on master.tryserver.chromium.linux (JOB_TIMED_OUT, no build URL)
On 2017/02/22 03:43:27, commit-bot: I haz the power wrote: > Try jobs failed on following builders: > chromium_presubmit on master.tryserver.chromium.linux (JOB_TIMED_OUT, no build > URL) alph@ any update on relanding this patch?
The CQ bit was checked by alph@chromium.org
On 2017/02/22 18:09:03, Navid Zolghadr wrote: > On 2017/02/22 03:43:27, commit-bot: I haz the power wrote: > > Try jobs failed on following builders: > > chromium_presubmit on master.tryserver.chromium.linux (JOB_TIMED_OUT, no > build > > URL) > > alph@ any update on relanding this patch? I'm trying to. CQ is flaky.
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: ios-device on master.tryserver.chromium.mac (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.mac/builders/ios-device/builds...) ios-device-xcode-clang on master.tryserver.chromium.mac (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.mac/builders/ios-device-xcode-...) ios-simulator on master.tryserver.chromium.mac (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.mac/builders/ios-simulator/bui...) ios-simulator-xcode-clang on master.tryserver.chromium.mac (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.mac/builders/ios-simulator-xco...) |