|
|
DescriptionFix flaky testWebView on Android
BUG=452266
Committed: https://crrev.com/db0e8ddf9c524249b40504e5de3ec36076aa6ce0
Cr-Commit-Position: refs/heads/master@{#313414}
Patch Set 1 #
Total comments: 2
Patch Set 2 : fix #Patch Set 3 : pydoc #
Total comments: 1
Patch Set 4 : review fix #
Messages
Total messages: 31 (8 generated)
zhenw@chromium.org changed reviewers: + chrishenry@google.com, nednguyen@google.com
ptal
https://codereview.chromium.org/858093003/diff/1/tools/telemetry/telemetry/co... File tools/telemetry/telemetry/core/android_app_unittest.py (right): https://codereview.chromium.org/858093003/diff/1/tools/telemetry/telemetry/co... tools/telemetry/telemetry/core/android_app_unittest.py:30: @decorators.Disabled('android') # crbug.com/452266 Would the right fix be simply adding a None check to the AndroidApp code? Looking briefly at the bug, that looks to be the case. In that case, you should just add a None check there.
The CQ bit was checked by nednguyen@google.com
lgtm
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/858093003/1
https://codereview.chromium.org/858093003/diff/1/tools/telemetry/telemetry/co... File tools/telemetry/telemetry/core/android_app_unittest.py (right): https://codereview.chromium.org/858093003/diff/1/tools/telemetry/telemetry/co... tools/telemetry/telemetry/core/android_app_unittest.py:30: @decorators.Disabled('android') # crbug.com/452266 Just realize that this disable decorator magic may not work in this case.
The CQ bit was unchecked by nednguyen@google.com
On 2015/01/27 18:48:07, nednguyen wrote: > https://codereview.chromium.org/858093003/diff/1/tools/telemetry/telemetry/co... > File tools/telemetry/telemetry/core/android_app_unittest.py (right): > > https://codereview.chromium.org/858093003/diff/1/tools/telemetry/telemetry/co... > tools/telemetry/telemetry/core/android_app_unittest.py:30: > @decorators.Disabled('android') # crbug.com/452266 > Just realize that this disable decorator magic may not work in this case. I am pretty sure that it doesn't work in this case. i.e: this test will run as long as you plugin the android device, unlike the normal browser test case which you have to specify --browser=.... You may want to use @Disable() completely.
On 2015/01/27 18:48:07, nednguyen wrote: > https://codereview.chromium.org/858093003/diff/1/tools/telemetry/telemetry/co... > File tools/telemetry/telemetry/core/android_app_unittest.py (right): > > https://codereview.chromium.org/858093003/diff/1/tools/telemetry/telemetry/co... > tools/telemetry/telemetry/core/android_app_unittest.py:30: > @decorators.Disabled('android') # crbug.com/452266 > Just realize that this disable decorator magic may not work in this case. I am pretty sure that it doesn't work in this case. i.e: this test will run as long as you plugin the android device, unlike the normal browser test case which you have to specify --browser=.... You may want to use @Disable() completely.
On 2015/01/27 18:53:13, nednguyen wrote: > On 2015/01/27 18:48:07, nednguyen wrote: > > > https://codereview.chromium.org/858093003/diff/1/tools/telemetry/telemetry/co... > > File tools/telemetry/telemetry/core/android_app_unittest.py (right): > > > > > https://codereview.chromium.org/858093003/diff/1/tools/telemetry/telemetry/co... > > tools/telemetry/telemetry/core/android_app_unittest.py:30: > > @decorators.Disabled('android') # crbug.com/452266 > > Just realize that this disable decorator magic may not work in this case. > > I am pretty sure that it doesn't work in this case. i.e: this test will run as > long as you plugin the android device, unlike the normal browser test case which > you have to specify --browser=.... You may want to use @Disable() completely. Will @Disable work? I use: @decorators.Disabled But when I use command "tools/telemetry/run_tests --browser=android-chrome-shell AndroidAppTest" for local testing. The test still run.
On 2015/01/27 19:02:51, Zhen Wang wrote: > On 2015/01/27 18:53:13, nednguyen wrote: > > On 2015/01/27 18:48:07, nednguyen wrote: > > > > > > https://codereview.chromium.org/858093003/diff/1/tools/telemetry/telemetry/co... > > > File tools/telemetry/telemetry/core/android_app_unittest.py (right): > > > > > > > > > https://codereview.chromium.org/858093003/diff/1/tools/telemetry/telemetry/co... > > > tools/telemetry/telemetry/core/android_app_unittest.py:30: > > > @decorators.Disabled('android') # crbug.com/452266 > > > Just realize that this disable decorator magic may not work in this case. > > > > I am pretty sure that it doesn't work in this case. i.e: this test will run as > > long as you plugin the android device, unlike the normal browser test case > which > > you have to specify --browser=.... You may want to use @Disable() completely. > > Will @Disable work? I use: > > @decorators.Disabled > > But when I use command "tools/telemetry/run_tests --browser=android-chrome-shell > AndroidAppTest" for local testing. The test still run. Hmh, probably just does the None check that Chris suggests then.
On 2015/01/27 19:02:51, Zhen Wang wrote: > On 2015/01/27 18:53:13, nednguyen wrote: > > On 2015/01/27 18:48:07, nednguyen wrote: > > > > > > https://codereview.chromium.org/858093003/diff/1/tools/telemetry/telemetry/co... > > > File tools/telemetry/telemetry/core/android_app_unittest.py (right): > > > > > > > > > https://codereview.chromium.org/858093003/diff/1/tools/telemetry/telemetry/co... > > > tools/telemetry/telemetry/core/android_app_unittest.py:30: > > > @decorators.Disabled('android') # crbug.com/452266 > > > Just realize that this disable decorator magic may not work in this case. > > > > I am pretty sure that it doesn't work in this case. i.e: this test will run as > > long as you plugin the android device, unlike the normal browser test case > which > > you have to specify --browser=.... You may want to use @Disable() completely. > > Will @Disable work? I use: > > @decorators.Disabled > > But when I use command "tools/telemetry/run_tests --browser=android-chrome-shell > AndroidAppTest" for local testing. The test still run. Have you tried changing this: https://code.google.com/p/chromium/codesearch#chromium/src/tools/telemetry/te... to: def _IsAppReady(self): if self._is_app_ready_predicate is None: return True return self._is_app_ready_predicate(self.app) Would this fix the test?
None check fix the problem (locally tested). But I am not sure if it is the right thing to do in your context. If it is ok. I will just fix it in that way.
On 2015/01/27 19:16:13, Zhen Wang wrote: > None check fix the problem (locally tested). But I am not sure if it is the > right thing to do in your context. If it is ok. I will just fix it in that way. It is the right solution as ctor accepts None as default value, so it should do the reasonable thing in that case, not raising exception. An alternative would be to set the field in ctor to a function that returns True if the value is None. Either way works... When you're at it, please add ctor pydoc as to what happen if is_app_ready_predicate is not passed to the ctore.
I add the pydoc now. ptal
https://codereview.chromium.org/858093003/diff/40001/tools/telemetry/telemetr... File tools/telemetry/telemetry/core/backends/android_app_backend.py (right): https://codereview.chromium.org/858093003/diff/40001/tools/telemetry/telemetr... tools/telemetry/telemetry/core/backends/android_app_backend.py:24: AndroidAppBackend is ready by default, i.e., _IsAppReady() returns True. This document should be moved to android_platform.LaunchAndroidApplication method, which is a public API.
On 2015/01/27 21:25:54, nednguyen wrote: > https://codereview.chromium.org/858093003/diff/40001/tools/telemetry/telemetr... > File tools/telemetry/telemetry/core/backends/android_app_backend.py (right): > > https://codereview.chromium.org/858093003/diff/40001/tools/telemetry/telemetr... > tools/telemetry/telemetry/core/backends/android_app_backend.py:24: > AndroidAppBackend is ready by default, i.e., _IsAppReady() returns True. > This document should be moved to android_platform.LaunchAndroidApplication > method, which is a public API. Ah, right. Fixed
lgtm
The CQ bit was checked by zhenw@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/858093003/60001
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: android_chromium_gn_compile_dbg on tryserver.chromium.linux (http://build.chromium.org/p/tryserver.chromium.linux/builders/android_chromiu...) Try jobs failed on following builders: android_chromium_gn_compile_dbg on tryserver.chromium.linux (http://build.chromium.org/p/tryserver.chromium.linux/builders/android_chromiu...)
The CQ bit was checked by nednguyen@google.com
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/858093003/60001
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: android_chromium_gn_compile_dbg on tryserver.chromium.linux (http://build.chromium.org/p/tryserver.chromium.linux/builders/android_chromiu...)
The CQ bit was checked by zhenw@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/858093003/60001
Message was sent while issue was closed.
Committed patchset #4 (id:60001)
Message was sent while issue was closed.
Patchset 4 (id:??) landed as https://crrev.com/db0e8ddf9c524249b40504e5de3ec36076aa6ce0 Cr-Commit-Position: refs/heads/master@{#313414} |