browse:shopping:avito flaky on android-nexus6 |
||||
Issue descriptionsystem_health.memory_mobile failing on chromium.perf/Android Nexus6 Perf Builders failed on: - Android Nexus6 Perf: https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus6%20Perf https://chromium-swarm.appspot.com/task?id=36eed509062ba510&refresh=10&show_raw=1 is a sample task. The story seems to be crashing chrome. I'll disable the story.
,
Jun 26 2017
Ok, I won't disable it.
,
Jun 28 2017
Hmm, the story keeps being flaky but with a low rate:
config story build history
0 android-nexus6 common browse:shopping:avito 205 ----1-1-----1---1---
1 android-nexus6 memory browse:shopping:avito 205 -3------?-1~-----?--
Most recent failure in:
https://luci-milo.appspot.com/buildbot/chromium.perf/Android%20Nexus6%20Perf/201
Highlights from the log:
F/libc ( 3651): Fatal signal 6 (SIGABRT), code -6 in tid 3793 (Thread-1366)
I/DEBUG ( 357): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 357): Build fingerprint: 'google/shamu/shamu:5.1.1/LMY47Z/1860966:userdebug/dev-keys'
I/DEBUG ( 357): Revision: '33696'
I/DEBUG ( 357): ABI: 'arm'
I/DEBUG ( 357): pid: 3651, tid: 3793, name: Thread-1366 >>> org.chromium.chrome <<<
I/DEBUG ( 357): signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
I/DEBUG ( 357): Abort message: '[FATAL:jni_android.cc(243)] Please include Java exception stack in crash report
I/DEBUG ( 357): '
I/DEBUG ( 357): r0 00000000 r1 00000ed1 r2 00000006 r3 00000000
I/DEBUG ( 357): r4 95e4fdb8 r5 00000006 r6 0000000b r7 0000010c
I/DEBUG ( 357): r8 0000004f r9 aecd94c0 sl 95e4f958 fp aed69ab0
I/DEBUG ( 357): ip 00000ed1 sp 95e4f2e0 lr b6e003c5 pc b6e2329c cpsr 600f0010
I/DEBUG ( 357):
I/DEBUG ( 357): backtrace:
I/DEBUG ( 357): #00 pc 0003a29c /system/lib/libc.so (tgkill+12)
I/DEBUG ( 357): #01 pc 000173c1 /system/lib/libc.so (pthread_kill+52)
I/DEBUG ( 357): #02 pc 00017fd3 /system/lib/libc.so (raise+10)
I/DEBUG ( 357): #03 pc 00014795 /system/lib/libc.so (__libc_android_abort+36)
I/DEBUG ( 357): #04 pc 00012f44 /system/lib/libc.so (abort+4)
I/DEBUG ( 357): #05 pc 000773c7 /data/app/org.chromium.chrome-1/lib/arm/libchrome.so
I/DEBUG ( 357):
I/DEBUG ( 357): Tombstone written to: /data/tombstones/tombstone_03
I/BootReceiver( 845): Copying /data/tombstones/tombstone_03 to DropBox (SYSTEM_TOMBSTONE)
W/ActivityManager( 845): Force finishing activity 1 org.chromium.chrome/.browser.ChromeTabbedActivity
E/JavaBinder( 845): !!! FAILED BINDER TRANSACTION !!!
W/ActivityManager( 845): Exception thrown during pause
W/ActivityManager( 845): android.os.TransactionTooLargeException
W/ActivityManager( 845): at android.os.BinderProxy.transactNative(Native Method)
W/ActivityManager( 845): at android.os.BinderProxy.transact(Binder.java:496)
W/ActivityManager( 845): at android.app.ApplicationThreadProxy.schedulePauseActivity(ApplicationThreadNative.java:704)
W/ActivityManager( 845): at com.android.server.am.ActivityStack.startPausingLocked(ActivityStack.java:825)
W/ActivityManager( 845): at com.android.server.am.ActivityStack.finishActivityLocked(ActivityStack.java:2726)
W/ActivityManager( 845): at com.android.server.am.ActivityStack.finishTopRunningActivityLocked(ActivityStack.java:2583)
W/ActivityManager( 845): at com.android.server.am.ActivityStackSupervisor.finishTopRunningActivityLocked(ActivityStackSupervisor.java:2497)
W/ActivityManager( 845): at com.android.server.am.ActivityManagerService.handleAppCrashLocked(ActivityManagerService.java:11500)
W/ActivityManager( 845): at com.android.server.am.ActivityManagerService.makeAppCrashingLocked(ActivityManagerService.java:11397)
W/ActivityManager( 845): at com.android.server.am.ActivityManagerService.crashApplication(ActivityManagerService.java:12081)
W/ActivityManager( 845): at com.android.server.am.ActivityManagerService.handleApplicationCrashInner(ActivityManagerService.java:11592)
W/ActivityManager( 845): at com.android.server.am.NativeCrashListener$NativeCrashReporter.run(NativeCrashListener.java:86)
E/lowmemorykiller( 255): Error writing /proc/3651/oom_score_adj; errno=22
https://luci-logdog.appspot.com/v/?s=chrome%2Fbb%2Fchromium.perf%2FAndroid_Nexus6_Perf%2F201%2F%2B%2Frecipes%2Fsteps%2Fsystem_health.common_mobile_on_Android%2F0%2Fstdout
Only seems to reproduce on this bot. ssid, could you have a look?
,
Aug 16 2017
I'm going to disable this on Nexus 6: it's failed something like 4 out of the last 10 runs, which is far too high of a failure rate.
,
Aug 16 2017
Recent failures include: https://uberchromegw.corp.google.com/i/chromium.perf/builders/Android%20Nexus6%20Perf/builds/408 https://uberchromegw.corp.google.com/i/chromium.perf/builders/Android%20Nexus6%20Perf/builds/402 https://uberchromegw.corp.google.com/i/chromium.perf/builders/Android%20Nexus6%20Perf/builds/401
,
Aug 16 2017
Disabling sgtm Do we still see the same errors as in #3?
,
Aug 16 2017
Yep, looks like it.
,
Aug 16 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/a0d9166d6bba3289fbceb866cdb26891cfb4256c commit a0d9166d6bba3289fbceb866cdb26891cfb4256c Author: Charlie Andrews <charliea@chromium.org> Date: Wed Aug 16 17:06:25 2017 Disable browse:shopping:avito on Nexus6 due to flakiness TBR=nednguyen@google.com,ssid@chromium.org Bug: 736497 Change-Id: I6b43cfce7dad9a3f9e2d0f256ff867c93b2c51a0 Reviewed-on: https://chromium-review.googlesource.com/617041 Reviewed-by: Charlie Andrews <charliea@chromium.org> Commit-Queue: Charlie Andrews <charliea@chromium.org> Cr-Commit-Position: refs/heads/master@{#494834} [modify] https://crrev.com/a0d9166d6bba3289fbceb866cdb26891cfb4256c/tools/perf/page_sets/system_health/expectations.py
,
Aug 16 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/e52fea44724e9de0b8b480ddb6ba3ca0737a4966 commit e52fea44724e9de0b8b480ddb6ba3ca0737a4966 Author: Charlie Andrews <charliea@chromium.org> Date: Wed Aug 16 18:06:06 2017 Disable browse:shopping:avito on Nexus6 due to flakiness TBR=simonhatch@chromium.org,ssid@chromium.org Bug: 736497 Change-Id: Icd291f318fcca8a5aa5ff9f53e1ac5c5bbf7c115 Reviewed-on: https://chromium-review.googlesource.com/617040 Reviewed-by: Charlie Andrews <charliea@chromium.org> Reviewed-by: Simon Hatch <simonhatch@chromium.org> Commit-Queue: Charlie Andrews <charliea@chromium.org> Cr-Commit-Position: refs/heads/master@{#494859}
,
Oct 5 2017
I've seen this test time out recently in the CQ on android_n5x_swarming_rel https://luci-milo.appspot.com/buildbot/tryserver.chromium.android/android_n5x_swarming_rel/276150 https://chromium-swarm.appspot.com/task?id=39066a1d81b72610&refresh=10&show_raw=1 At least, the last line of the log is this: [9/21] benchmarks.system_health_smoke_test.SystemHealthBenchmarkSmokeTest.system_health.memory_mobile.browse:shopping:avito queued Then the bot times out.
,
Jul 19
From the swarming logs:
Exception raised when cleaning story run:
Traceback (most recent call last):
_RunStoryAndProcessErrorIfNeeded at /b/swarming/w/ir/third_party/catapult/telemetry/telemetry/internal/story_runner.py:124
test.DidRunStory(state.platform, results)
DidRunStory at /b/swarming/w/ir/third_party/catapult/telemetry/telemetry/web_perf/timeline_based_measurement.py:309
trace_result = platform.tracing_controller.StopTracing()
StopTracing at /b/swarming/w/ir/third_party/catapult/telemetry/telemetry/core/tracing_controller.py:47
return self._tracing_controller_backend.StopTracing()
StopTracing at /b/swarming/w/ir/third_party/catapult/telemetry/telemetry/internal/platform/tracing_controller_backend.py:109
self._IssueClockSyncMarker()
_IssueClockSyncMarker at /b/swarming/w/ir/third_party/catapult/telemetry/telemetry/internal/platform/tracing_controller_backend.py:213
self._RecordIssuerClockSyncMarker)
RecordClockSyncMarker at /b/swarming/w/ir/third_party/catapult/telemetry/telemetry/internal/platform/tracing_agent/chrome_tracing_agent.py:177
raise ChromeClockSyncError('Cannot issue clock sync. No devtools clients')
ChromeClockSyncError: Cannot issue clock sync. No devtools clients
Locals:
devtools_clients : []
record_controller_clock_sync_marker_callback : <bound method TracingControllerBackend._RecordIssuerClockSyncMarker of <telemetry.internal.platform.tracing_controller_backend.TracingControllerBackend object at 0x7f3c67c26a90>>
sync_id : 'df95875d-dd98-4c14-aa37-cc7391c77b56'
,
Jul 19
Looks like the tab crashed.
,
Jul 24
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/983b0e40fd3fb79e482bde546b948dcccb1e1e04 commit 983b0e40fd3fb79e482bde546b948dcccb1e1e04 Author: Tim Dresser <tdresser@chromium.org> Date: Tue Jul 24 00:37:01 2018 Remove Nexus 6 from expectations.config. We no longer test non-webview Nexus 6. Bug: 736497 Change-Id: I22942bb8a57c63e3b295f6f71df570c3a3fc014d Reviewed-on: https://chromium-review.googlesource.com/1143584 Commit-Queue: Timothy Dresser <tdresser@chromium.org> Reviewed-by: Charlie Andrews <charliea@chromium.org> Cr-Commit-Position: refs/heads/master@{#577374} [modify] https://crrev.com/983b0e40fd3fb79e482bde546b948dcccb1e1e04/tools/perf/expectations.config
,
Oct 17
|
||||
►
Sign in to add a comment |
||||
Comment 1 by perezju@chromium.org
, Jun 26 2017The story (browse:shopping:avito) has only flaked a few times: config story build history 0 android-nexus6 common browse:shopping:avito 194 -1---1----------1--- 1 android-nexus6 memory browse:shopping:avito 194 ~-----?-----?3------ I think it shouldn't be disabled, but I'll keep an eye on it.