Issue metadata
Sign in to add a comment
|
android_webview_test_apk (ClientOnPageFinishedTest#testCalledAfterError) on Android failing on chromium.linux/Android Tests |
||||||||||||||||||||||
Issue descriptionandroid_webview_test_apk on Android failing on chromium.linux/Android Tests Type: build-failure Builders failed on: - Android Tests: https://build.chromium.org/p/chromium.linux/builders/Android%20Tests https://uberchromegw.corp.google.com/i/chromium.linux/builders/Android%20Tests/builds/32832/steps/android_webview_test_apk%20on%20Android/logs/stdio I 140.377s run_tests_on_device(03d27f97006adbb7) detected failure in org.chromium.android_webview.test.ClientOnPageFinishedTest#testCalledAfterError. raw output: I 140.377s TimeoutThread-1-for-run_tests_on_device(05fc05a60ae4ffc7) [host]> /b/swarm_slave/w/irLAm9Dl/third_party/android_tools/sdk/platform-tools/adb -s 05fc05a60ae4ffc7 shell '( cat /data/local/tmp/android-webview-command-line );echo %$?' I 140.377s run_tests_on_device(03d27f97006adbb7) INSTRUMENTATION_STATUS: numtests=1 I 140.377s run_tests_on_device(03d27f97006adbb7) INSTRUMENTATION_STATUS: stream= I 140.377s run_tests_on_device(03d27f97006adbb7) org.chromium.android_webview.test.ClientOnPageFinishedTest: I 140.377s run_tests_on_device(03d27f97006adbb7) INSTRUMENTATION_STATUS: id=InstrumentationTestRunner I 140.377s run_tests_on_device(03d27f97006adbb7) INSTRUMENTATION_STATUS: test=testCalledAfterError I 140.377s run_tests_on_device(03d27f97006adbb7) INSTRUMENTATION_STATUS: class=org.chromium.android_webview.test.ClientOnPageFinishedTest I 140.377s run_tests_on_device(03d27f97006adbb7) INSTRUMENTATION_STATUS: current=1 I 140.379s run_tests_on_device(03d27f97006adbb7) INSTRUMENTATION_STATUS_CODE: 1 I 140.379s run_tests_on_device(03d27f97006adbb7) INSTRUMENTATION_RESULT: shortMsg=junit.framework.AssertionFailedError I 140.379s run_tests_on_device(03d27f97006adbb7) INSTRUMENTATION_RESULT: longMsg=junit.framework.AssertionFailedError: onPageFinished called twice for http://localhost:7/non_existent expected:<false> but was:<true> I 140.380s run_tests_on_device(03d27f97006adbb7) INSTRUMENTATION_CODE: 0
,
Oct 4 2016
hush@ Could you please take a look?
,
Oct 4 2016
,
Oct 4 2016
Anybody else want to take a look?
,
Oct 4 2016
add @RetryOnFailure first pls
,
Oct 4 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/7ef3e0dfcbb13b2347a5a8a75df277d17eb027bf commit 7ef3e0dfcbb13b2347a5a8a75df277d17eb027bf Author: imcheng <imcheng@chromium.org> Date: Tue Oct 04 21:27:56 2016 [android_webview test] Add @RetryOnFailure to testCalledAfterError ClientOnPageFinishedTest#testCalledAfterError is flaky. BUG= 652577 Review-Url: https://codereview.chromium.org/2397533002 Cr-Commit-Position: refs/heads/master@{#422933} [modify] https://crrev.com/7ef3e0dfcbb13b2347a5a8a75df277d17eb027bf/android_webview/javatests/src/org/chromium/android_webview/test/ClientOnPageFinishedTest.java
,
Oct 5 2016
,
Oct 27 2016
That test keeps failing on the CQ Trybots: Error: junit.framework.AssertionFailedError: onPageFinished called twice for http://localhost:7/non_existent expected:<false> but was:<true> Sample bot with flakes and pass after 2 tries: https://build.chromium.org/p/chromium.android/builders/Android%20N5X%20Swarm%20Builder/builds/5656/steps/android_webview_test_apk%20on%20Android/logs/stdio Trybot from the CQ where it fails quite often: https://build.chromium.org/p/tryserver.chromium.android/builders/android_n5x_swarming_rel?numbuilds=100 Sample failing build: https://build.chromium.org/p/tryserver.chromium.android/builders/android_n5x_swarming_rel/builds/56844 Maybe disable it completely?
,
Oct 27 2016
Yoland, would you be able to take a look at this?
,
Oct 28 2016
Sure!
,
Oct 28 2016
It's still failing very frequently. I'm disabling it.
,
Oct 28 2016
BTW, the guide about FlakyTest, DisabledTest at https://www.chromium.org/developers/testing/android-tests looks stale.
,
Oct 28 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/ada091bdbd7f8a6e085e291bed2e680fdf31ff6f commit ada091bdbd7f8a6e085e291bed2e680fdf31ff6f Author: tyoshino <tyoshino@chromium.org> Date: Fri Oct 28 07:41:54 2016 Disable flaky Android WebView test ClientOnPageFinishedTest.testCalledAfterError() TBR=michaelbai@chromium.org BUG= 652577 Review-Url: https://codereview.chromium.org/2455943004 Cr-Commit-Position: refs/heads/master@{#428311} [modify] https://crrev.com/ada091bdbd7f8a6e085e291bed2e680fdf31ff6f/android_webview/javatests/src/org/chromium/android_webview/test/ClientOnPageFinishedTest.java
,
Oct 28 2016
+tyoshino, ya, the guide is quite outdated. I will update the doc all together after doing a refactor on @Restriction and @DisableIf
,
Dec 21 2016
I think this issue no longer persist, in terms of updating the flaky/disabled test guide, I ll open a new bug for it
,
Aug 23
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by horo@chromium.org
, Oct 4 2016