chrome_public_test_apk fails on clang tot bots |
|||
Issue descriptionExample builds: https://ci.chromium.org/buildbot/chromium.clang/ToTAndroid/5320 https://ci.chromium.org/buildbot/chromium.clang/ToTAndroidCFI/3473 From the first one: java.lang.NullPointerException at org.chromium.base.UserDataHost.getUserData(UserDataHost.java:90) at org.chromium.chrome.browser.tab.TabBrowserControlsOffsetHelper.from(TabBrowserControlsOffsetHelper.java:67) at org.chromium.chrome.browser.fullscreen.FullscreenManager.setFullscreenManager(FullscreenManager.java:126) at org.chromium.chrome.browser.fullscreen.FullscreenManager.setTab(FullscreenManager.java:115) at org.chromium.chrome.browser.fullscreen.ChromeFullscreenManager.setTab(ChromeFullscreenManager.java:242) at org.chromium.chrome.browser.fullscreen.FullscreenManager.destroy(FullscreenManager.java:196) at org.chromium.chrome.browser.fullscreen.ChromeFullscreenManager.destroy(ChromeFullscreenManager.java:705) at org.chromium.chrome.browser.ChromeActivity.onDestroy(ChromeActivity.java:1332) at android.app.Activity.performDestroy(Activity.java:5403) at android.app.Instrumentation.callActivityOnDestroy(Instrumentation.java:1117) at android.support.test.runner.MonitoringInstrumentation.callActivityOnDestroy(MonitoringInstrumentation.java:519) at android.app.ActivityThread.performDestroyActivity(ActivityThread.java:3470) at android.app.ActivityThread.handleDestroyActivity(ActivityThread.java:3501) at android.app.ActivityThread.access$1400(ActivityThread.java:135) at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1249) at android.os.Handler.dispatchMessage(Handler.java:102) at android.os.Looper.loop(Looper.java:136) at android.app.ActivityThread.main(ActivityThread.java:5001) at java.lang.reflect.Method.invokeNative(Method.java) at java.lang.reflect.Method.invoke(Method.java:515) at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:785) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:601) at dalvik.system.NativeStart.main(NativeStart.java)
,
Nov 8
I think something is being flaky. Here are two recently failed builds from the same bot: https://ci.chromium.org/buildbot/chromium.clang/ToTAndroid/5382 org.chromium.chrome.browser.partnercustomizations.PartnerHomepageUnitTest#testHomepageFeatureFlag https://ci.chromium.org/buildbot/chromium.clang/ToTAndroid/5383 org.chromium.chrome.browser.partnercustomizations.PartnerHomepageUnitTest#testHomepageFeatureFlag The same test also fails in tryjobs (see step 221) https://ci.chromium.org/p/chromium/builders/luci.chromium.try/android-kitkat-arm-rel/121035
,
Nov 8
,
Nov 8
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/6405b4cf461a04174c290b9bb8b5334283f56f90 commit 6405b4cf461a04174c290b9bb8b5334283f56f90 Author: Hans Wennborg <hans@chromium.org> Date: Thu Nov 08 15:12:11 2018 Disable flaky test org.chromium.chrome.browser.partnercustomizations.PartnerHomepageUnitTest#testHomepageFeatureFlag TBR=danielpark Bug: 901769 Change-Id: I3b6b67f3381f77cc3520139eea3c11d5a189ae8c Reviewed-on: https://chromium-review.googlesource.com/c/1326485 Reviewed-by: Hans Wennborg <hans@chromium.org> Commit-Queue: Hans Wennborg <hans@chromium.org> Cr-Commit-Position: refs/heads/master@{#606469} [modify] https://crrev.com/6405b4cf461a04174c290b9bb8b5334283f56f90/chrome/android/javatests/src/org/chromium/chrome/browser/partnercustomizations/PartnerHomepageUnitTest.java
,
Nov 12
The bot is greener now. |
|||
►
Sign in to add a comment |
|||
Comment 1 by h...@chromium.org
, Nov 6