[test cleanup] touch_TouchscreenZoom fails consistently on 11 boards |
||||||||||||
Issue descriptionTest dashboard view: https://stainless.corp.google.com/search?view=matrix&row=build&col=board&days=15&suite=bvt-perbuild&test=touch_TouchscreenZoom&exclude_cts=false&exclude_not_run=true&exclude_non_release=true&exclude_au=true&exclude_acts=true&exclude_retried=true&exclude_non_production=true Failure reason: No page zoom occurred! Devices this issue is present: buddy,candy,clapper,cyan,nyan_big,nyan_blaze,pyro,samus,setzer,sumo,veyron_minnie Possible reasons: - bad test input files - non-touchscreen boards are tested - zoom verification is off AI: For each device name: - run test locally - find DUT in lab where test is passing - re-generate input file(s) If verification procedure issue is present, a fix will solve all in once.
,
Nov 16
Rerunning the test locally against multiple buddy and candy hosts failed. pbathini@, re-generate the zoom-in and zoom out data files for candy touch device. First check if there is a file path naming issue.
,
Dec 4
Another action item is to find the specific boards and see if test beds are having touchscreen in contact with any of the surroundings - I've seen objects put between TS and base to keep the lid open etc.
,
Dec 6
Checking on Candy example: - Only one board is having touchscreen and part of pool:bvt - chromeos4-row8-rack3-host5. No wonder it is the only one to run this test - https://screenshot.googleplex.com/AzPWvJnioVC - Need to - check the board physically, and add more touchscreen boards to the pool:bvt Checking on buddy(chromebase) example: - these are all 6 touchscreen boards in pool:bvt - https://screenshot.googleplex.com/L3yFDVz12wi - Need to check how are they positioned and if anything is touching the screens for all of them. Checking on nyan_big example: - These are the 5 boards with touchscreen on pool:bvt -https://screenshot.googleplex.com/bJ5uqjKQFiV Etc.
,
Dec 6
Observing devices(candy, setzer) in lab while test is running, I'd accept the test zoom data is wrong, having nothing was found to interfere with touchscreen at the testbed. Hi pramod, do you have the data generated?
,
Dec 7
Hi Kalin, Tied up with BT full release testing. PFA the gesture files for candy
,
Dec 8
I replaced the original files with the new in #6. Lets see if the test will improve on Candy board.
,
Dec 12
The new test files did not make the test pass - https://screenshot.googleplex.com/gW1nptXWNDm Possible scenarios: - zoom does not actually happen - verification is not sufficient
,
Dec 12
Picked up the device pbathini@ generated and played back the files in #6. Test failed - FAIL: No page zoom occurred! - Check if any of the passing boards are passing for real - Check what is wrong with check_zoom_in_one_direction()
,
Dec 12
Could not find boards that actually pass the test The test reads the value of window.innerWidth in TestPage.get_page_width() Before and after the zoom it returns one same value - 1366(for Candy) and test fails respectively. get_page_width() returns same value as even the content is zoomed, the chrome window is unchanged. AI - Implement zoom sensitive verification method.
,
Dec 17
Up for review - https://chromium-review.googlesource.com/c/chromiumos/third_party/autotest/+/1380719
,
Dec 18
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/third_party/autotest/+/3e505362fdd6e2773c8b0808a3d2eabb0c92cbb9 commit 3e505362fdd6e2773c8b0808a3d2eabb0c92cbb9 Author: Kalin Stoyanov <kalin@chromium.org> Date: Tue Dec 18 12:28:54 2018 Fix touchscreen zoom input test verification Replaced window.innerWidth with window.visualViewport.scale BUG= chromium:860818 TEST=Tested DUTs locally and in lab Change-Id: I63d7b71bd8fcec465527f44cfe7fcf2d66dae3ee Reviewed-on: https://chromium-review.googlesource.com/1380719 Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com> Tested-by: Kalin Stoyanov <kalin@chromium.org> Reviewed-by: Katherine Threlkeld <kathrelkeld@chromium.org> [modify] https://crrev.com/3e505362fdd6e2773c8b0808a3d2eabb0c92cbb9/client/site_tests/touch_TouchscreenZoom/touch_TouchscreenZoom.py [modify] https://crrev.com/3e505362fdd6e2773c8b0808a3d2eabb0c92cbb9/client/cros/touch_playback_test_base.py
,
Dec 18
,
Dec 18
This bug requires manual review: M72 has already been promoted to the beta branch, so this requires manual review Please contact the milestone owner if you have questions. Owners: govind@(Android), kariahda@(iOS), djmm@(ChromeOS), abdulsyed@(Desktop) For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Dec 18
,
Dec 18
,
Dec 18
,
Dec 19
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/third_party/autotest/+/ad766d0c01b555f98be8b4bb877e306620508252 commit ad766d0c01b555f98be8b4bb877e306620508252 Author: Kalin Stoyanov <kalin@chromium.org> Date: Wed Dec 19 18:47:35 2018 Fix touchscreen zoom input test verification Replaced window.innerWidth with window.visualViewport.scale BUG= chromium:860818 TEST=Tested DUTs locally and in lab Change-Id: I63d7b71bd8fcec465527f44cfe7fcf2d66dae3ee Reviewed-on: https://chromium-review.googlesource.com/1380719 Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com> Tested-by: Kalin Stoyanov <kalin@chromium.org> Reviewed-by: Katherine Threlkeld <kathrelkeld@chromium.org> (cherry picked from commit 3e505362fdd6e2773c8b0808a3d2eabb0c92cbb9) Reviewed-on: https://chromium-review.googlesource.com/c/1382805 Commit-Queue: Kalin Stoyanov <kalin@chromium.org> [modify] https://crrev.com/ad766d0c01b555f98be8b4bb877e306620508252/client/site_tests/touch_TouchscreenZoom/touch_TouchscreenZoom.py [modify] https://crrev.com/ad766d0c01b555f98be8b4bb877e306620508252/client/cros/touch_playback_test_base.py
,
Dec 24
This issue has been approved for a merge. Please merge the fix to any appropriate branches as soon as possible! If all merges have been completed, please remove any remaining Merge-Approved labels from this issue. Thanks for your time! To disable nags, add the Disable-Nags label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Dec 28
This issue has been approved for a merge. Please merge the fix to any appropriate branches as soon as possible! If all merges have been completed, please remove any remaining Merge-Approved labels from this issue. Thanks for your time! To disable nags, add the Disable-Nags label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jan 6
|
||||||||||||
►
Sign in to add a comment |
||||||||||||
Comment 1 by ka...@chromium.org
, Jul 24