New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 795699 link

Starred by 1 user
Status: Assigned
Owner:
oysteine@chromium.org
Cc:
rockot@google.com
█ jcivelli@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: ----



Sign in to add a comment

smoothness.tough_animation_cases failing on Android

Project Member Reported by sheriff-...@appspot.gserviceaccount.com, Dec 18 2017 
Filed by sheriff-o-matic@appspot.gserviceaccount.com on behalf of oysteine@google.com

smoothness.tough_animation_cases failing on multiple builders

Builders failed on: 
- Android Nexus7v2 Perf: 
  https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus7v2%20Perf

Comment 1 by oysteine@chromium.org, Dec 18 2017

Cc: -oysteine@google.com roc...@chromium.org
Owner: oysteine@chromium.org
rockot@: Who knows about the Mojo java bindings?

Looking at Android specifically, it might be due to this:

E/System  (26557): Caused by: java.lang.Exception: AutocloseableRouter allocated at:
	E/System  (26557): 	at org.chromium.mojo.bindings.AutoCloseableRouter.<init>(AutoCloseableRouter.java:43)
	E/System  (26557): 	at org.chromium.mojo.bindings.Interface$Manager.attachProxy(Interface.java:1400)
	E/System  (26557): 	at org.chromium.chrome.browser.ChromeTabbedActivity$2.onPageLoadFinished(ChromeTabbedActivity.java:6380)
	E/System  (26557): 	at org.chromium.chrome.browser.tab.Tab.didFinishPageLoad(Tab.java:1695)
	E/System  (26557): 	at org.chromium.chrome.browser.tab.TabWebContentsObserver.didFinishLoad(TabWebContentsObserver.java:138)
	E/System  (26557): 	at org.chromium.content.browser.webcontents.WebContentsObserverProxy.didFinishLoad(WebContentsObserverProxy.java:169)
	E/System  (26557): 	at org.chromium.base.SystemMessageHandler.nativeDoRunLoopOnce(Native Method)
	E/System  (26557): 	at org.chromium.base.SystemMessageHandler.handleMessage(SystemMessageHandler.java:51)
	E/System  (26557): 	at android.os.Handler.dispatchMessage(Handler.java:102)
	E/System  (26557): 	at android.os.Looper.loop(Looper.java:136)
	E/System  (26557): 	at android.app.ActivityThread.main(ActivityThread.java:5017)
	E/System  (26557): 	at java.lang.reflect.Method.invokeNative(Native Method)
	E/System  (26557): 	at java.lang.reflect.Method.invoke(Method.java:515)
	E/System  (26557): 	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:779)
	E/System  (26557): 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:595)
	E/System  (26557): 	at dalvik.system.NativeStart.main(Native Method)

See:
https://logs.chromium.org/v/?s=chrome%2Fbb%2Fchromium.perf%2FAndroid_Nexus7v2_Perf%2F1009%2F%2B%2Frecipes%2Fsteps%2Fsmoothness.tough_animation_cases_on_Android%2F0%2Fstdout

Comment 2 by oysteine@chromium.org, Dec 18 2017

Description: Show this description

Comment 3 by oysteine@chromium.org, Dec 18 2017

Summary: smoothness.tough_animation_cases failing on Android (was: smoothness.tough_animation_cases failing on multiple builders)

Comment 4 by oysteine@chromium.org, Dec 18 2017

Labels: -Pri-2 Pri-1

Comment 5 by oysteine@chromium.org, Dec 18 2017

Labels: Performance-Sheriff-BotHealth

Comment 6 by roc...@chromium.org, Dec 18 2017

Cc: jcivelli@chromium.org
It is unlikely that the log spam is relevant to the source of failures, given that said spam has been around for a while. +jcivelli@ who knows things about stuff and might have some insight, just in case.

Comment 7 by benhenry@chromium.org, Aug 1

Status: Assigned (was: Available)

Comment 8 by roc...@chromium.org, Oct 17

Cc: -roc...@chromium.org rockot@google.com
►

Sign in to add a comment