chrome_public_test_apk failing on chromium.linux/Android Tests (dbg) |
|||||
Issue descriptionchrome_public_test_apk failing on chromium.linux/Android Tests (dbg) Builders failed on: - Android Tests (dbg): https://build.chromium.org/p/chromium.linux/builders/Android%20Tests%20%28dbg%29 First failed build: https://build.chromium.org/p/chromium.linux/builders/Android%20Tests%20%28dbg%29/builds/44387 Error message: I 728.601s Main All tests completed. C 728.602s Main ******************************************************************************** C 728.602s Main Detailed Logs C 728.602s Main ******************************************************************************** C 728.602s Main [FAIL] org.chromium.chrome.browser.download.DownloadManagerServiceTest#testDownloadCompletedIsCalled: C 728.602s Main java.lang.AssertionError: Unexpected call:, no call expected, but got: DOWNLOAD_SUCCESSFUL C 728.602s Main at org.junit.Assert.fail(Assert.java:88) C 728.602s Main at org.junit.Assert.assertTrue(Assert.java:41) C 728.602s Main at org.junit.Assert.assertFalse(Assert.java:64) C 728.602s Main at org.chromium.chrome.browser.download.DownloadManagerServiceTest$MockDownloadNotifier.assertCorrectExpectedCall(DownloadManagerServiceTest.java:130) C 728.602s Main at org.chromium.chrome.browser.download.DownloadManagerServiceTest$MockDownloadNotifier.notifyDownloadSuccessful(DownloadManagerServiceTest.java:144) C 728.602s Main at org.chromium.chrome.browser.download.DownloadManagerService$3.onPostExecute(DownloadManagerService.java:491) C 728.602s Main at org.chromium.chrome.browser.download.DownloadManagerService$3.onPostExecute(DownloadManagerService.java:478) C 728.602s Main at android.os.AsyncTask.finish(AsyncTask.java:632) C 728.602s Main at android.os.AsyncTask.access$600(AsyncTask.java:177) C 728.602s Main at android.os.AsyncTask$InternalHandler.handleMessage(AsyncTask.java:645) C 728.602s Main at android.os.Handler.dispatchMessage(Handler.java:102) C 728.602s Main at android.os.Looper.loop(Looper.java:136) C 728.602s Main at android.app.ActivityThread.main(ActivityThread.java:5001) C 728.602s Main at java.lang.reflect.Method.invokeNative(Native Method) C 728.602s Main at java.lang.reflect.Method.invoke(Method.java:515) C 728.602s Main at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:785) C 728.603s Main at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:601) I couldn't find any CLs in the range given by the bots, so assigning people who seem to work on Android Download Manager. Could you PTAL? Thanks!
,
Aug 2 2017
Another failed run: https://build.chromium.org/p/chromium.linux/builders/Android%20Tests%20%28dbg%29/builds/44439 Adding @RetryOnError.
,
Aug 2 2017
,
Aug 2 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/74ab9f06477c5ffd681c6e6e9d16f17551db0dc0 commit 74ab9f06477c5ffd681c6e6e9d16f17551db0dc0 Author: Guido Urdaneta <guidou@chromium.org> Date: Wed Aug 02 13:22:09 2017 Add @RetryOnFailure to DownloadManagerServiceTest#testDownloadCompletedIsCalled This test has flaked sometimes on Android bots. BUG=750566 TBR=jming@chromium.org Change-Id: I2b347ba3d055abe8b93a5a2df6a63e32d72f1a24 Reviewed-on: https://chromium-review.googlesource.com/597851 Reviewed-by: Guido Urdaneta <guidou@chromium.org> Commit-Queue: Guido Urdaneta <guidou@chromium.org> Cr-Commit-Position: refs/heads/master@{#491355} [modify] https://crrev.com/74ab9f06477c5ffd681c6e6e9d16f17551db0dc0/chrome/android/javatests/src/org/chromium/chrome/browser/download/DownloadManagerServiceTest.java
,
Aug 15 2017
I ran the tests on the CQ without @RetryOnFailure, was not able to reproduce the failures. Thoughts? https://chromium-review.googlesource.com/c/613666
,
Aug 17 2017
I'd probably try to figure out which bots fail and in particular the exact device they have and which version of Android they have, and then flash that to your local device. Then you could re-run all tests or just that test with a high repeat-counter maybe?
,
Apr 25 2018
,
May 17 2018
,
Jan 11
Setting defect without priority to Pri-2. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by jming@chromium.org
, Jul 31 2017