FullscreenAppListPresenterDelegateTest failing on 3163 branch |
||||||||||
Issue description[ RUN ] FullscreenAppListPresenterDelegateTest.TapAndClickEnablesSearchBox/0 ../../ash/app_list/app_list_presenter_delegate_unittest.cc:713: Failure Value of: search_box_view->is_search_box_active() Actual: false Expected: true [ FAILED ] FullscreenAppListPresenterDelegateTest.TapAndClickEnablesSearchBox/0, where GetParam() = false (1545 ms) [1/2] FullscreenAppListPresenterDelegateTest.TapAndClickEnablesSearchBox/0 (1545 ms) [ RUN ] FullscreenAppListPresenterDelegateTest.TapAndClickEnablesSearchBox/1 ../../ash/app_list/app_list_presenter_delegate_unittest.cc:713: Failure Value of: search_box_view->is_search_box_active() Actual: false Expected: true [ FAILED ] FullscreenAppListPresenterDelegateTest.TapAndClickEnablesSearchBox/1, where GetParam() = true (599 ms) [2/2] FullscreenAppListPresenterDelegateTest.TapAndClickEnablesSearchBox/1 (599 ms)
,
Aug 17 2017
warx@ looks like tests weren't updated? Also shouldn't there be a new test that tests this new behavior?
,
Aug 17 2017
I am investigating. Weird that m61 has test failure. The modified tests should be no difference. New tests are added in app_list_unittests.
,
Aug 17 2017
My cl is not the culprit. My investigation is that SearchBoxView::OnMouseEvent is not triggered. If I change GetPointInsideSearchbox() in the test: from app_list_presenter_impl_.GetView()->search_box_view()->GetBoundsInScreen().origin() to app_list_presenter_impl_.GetView()->search_box_view()->GetBoundsInScreen().CenterPoint(), then the test could pass. The test file itself has no difference from tot. I checked several related files/dirs, cannot see obvious changes missed. Attached diffs between 3163 branch and tot: git diff origin/master -- ui/app_list/views/ git diff origin/master -- chrome/browser/ui/app_list/ git diff origin/master -- ash/app_list/
,
Aug 17 2017
+weidongg for SearchBox active related changes +xiyuan reviewer test is passed on tot, but failed on 3163
,
Aug 17 2017
There are no changes that we've made that I see as potential culprits either. We'll probably need to bisect and then try to figure out what needs to be merged from there.
,
Aug 17 2017
I just found the reason: it is because we didn't merge this back: https://chromium-review.googlesource.com/c/567486. We would like to know whether merging the whole cl back or just the changes in ui/app_list/views back.
,
Aug 17 2017
ok, the cl owner is actually varkha@.
,
Aug 17 2017
This bug requires manual review: M61 has already been promoted to the beta branch, so this requires manual review Please contact the milestone owner if you have questions. Owners: amineer@(Android), cmasso@(iOS), ketakid@(ChromeOS), govind@(Desktop) For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Aug 17 2017
btw, changing origin() to CenterPoint() is another option, IMO. I will delegate to the cl owner or xiyuan for decision : )
,
Aug 18 2017
Approving merge to M61 Chrome OS.
,
Aug 18 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/820a7a5574b570545f06f716c5b19c7f5f2a1360 commit 820a7a5574b570545f06f716c5b19c7f5f2a1360 Author: Qiang Xu <warx@chromium.org> Date: Fri Aug 18 20:50:43 2017 app_list: make GetPointInsideSearchbox picking CenterPoint changes: Mainly for addressing the issue in crbug.com/756516 , where in 3163 branch https://chromium-review.googlesource.com/c/567486 is not merged back. In that change, the whole search box is the event target rather than just the part inside the shadow. Contacted varkha@, better changing the tapping point, not the margin of search box. Bug: 756516 Test: covered by tests Change-Id: If66f70b223ffb1c53ddeb148b9a708def7385f41 Reviewed-on: https://chromium-review.googlesource.com/621533 Reviewed-by: Qiang(Joe) Xu <warx@chromium.org> Reviewed-by: Xiyuan Xia <xiyuan@chromium.org> Commit-Queue: Qiang(Joe) Xu <warx@chromium.org> Cr-Commit-Position: refs/heads/master@{#495673} [modify] https://crrev.com/820a7a5574b570545f06f716c5b19c7f5f2a1360/ash/app_list/app_list_presenter_delegate_unittest.cc
,
Aug 18 2017
as an FYI I'm holding off on merging further launcher changes to M61 until we can get this change merged back to M61 and confirm the tests pass at ToT on 3163. Joe, thanks for finding and taking up the fix!
,
Aug 18 2017
I will merge it right now. It should have no conflict.
,
Aug 18 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/5e671ba04d1450efda2a6f9c5b07b1d0925c1a68 commit 5e671ba04d1450efda2a6f9c5b07b1d0925c1a68 Author: Qiang Xu <warx@chromium.org> Date: Fri Aug 18 21:10:58 2017 m61 merge: app_list: make GetPointInsideSearchbox picking CenterPoint changes: Mainly for addressing the issue in crbug.com/756516 , where in 3163 branch https://chromium-review.googlesource.com/c/567486 is not merged back. In that change, the whole search box is the event target rather than just the part inside the shadow. Contacted varkha@, better changing the tapping point, not the margin of search box. TBR: xiyuan@chromium.org (cherry picked from commit 820a7a5574b570545f06f716c5b19c7f5f2a1360) Bug: 756516 Test: covered by tests Change-Id: If66f70b223ffb1c53ddeb148b9a708def7385f41 Reviewed-on: https://chromium-review.googlesource.com/621533 Reviewed-by: Qiang(Joe) Xu <warx@chromium.org> Reviewed-by: Xiyuan Xia <xiyuan@chromium.org> Commit-Queue: Qiang(Joe) Xu <warx@chromium.org> Cr-Original-Commit-Position: refs/heads/master@{#495673} Reviewed-on: https://chromium-review.googlesource.com/621195 Cr-Commit-Position: refs/branch-heads/3163@{#685} Cr-Branched-From: ff259bab28b35d242e10186cd63af7ed404fae0d-refs/heads/master@{#488528} [modify] https://crrev.com/5e671ba04d1450efda2a6f9c5b07b1d0925c1a68/ash/app_list/app_list_presenter_delegate_unittest.cc
,
Aug 18 2017
,
Aug 18 2017
Verified that tests pass on branch, going to start merges for launcher again. |
||||||||||
►
Sign in to add a comment |
||||||||||
Comment 1 by maajid@chromium.org
, Aug 17 2017