New issue
Advanced search Search tips

Issue 842939 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: May 2018
Cc:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

HWTest [bvt-arc] failing on veyron_minnie-tot-chrome-pfq-informational with "Android did not boot!" errors

Project Member Reported by derat@chromium.org, May 14 2018

Issue description

Various tests in HWTest [bvt-arc] are failing on veyron_minnie-tot-chrome-pfq-informational with "Android did not boot!" errors. See e.g.

https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?buildbucketId=8946540922518545552
https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?buildbucketId=8946525663650721360

I would copy-and-paste a list of the failing tests here, but I can't find any way to do that because of http://b/79705373.

From https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/200103382-chromeos-test:

05/14 15:12:49.447 INFO |               job:0200| Writing results to /usr/local/autotest/results/default
05/14 15:12:49.772 INFO |               job:0232| START	----	----	timestamp=1526335969	localtime=May 14 15:12:49	
05/14 15:12:49.818 INFO |          packages:0190| Fetching packages.checksum from http://100.115.245.201:8082/static/veyron_minnie-tot-chrome-pfq-informational/R68-10679.0.0-b2570321/autotest/packages to /usr/local/autotest/packages.checksum
05/14 15:12:49.862 INFO |          packages:0207| Successfully fetched packages.checksum from http://100.115.245.201:8082/static/veyron_minnie-tot-chrome-pfq-informational/R68-10679.0.0-b2570321/autotest/packages/packages.checksum
05/14 15:12:49.924 INFO |               job:0232| 	START	cheets_FileSystemPermissions	cheets_FileSystemPermissions	timestamp=1526335969	localtime=May 14 15:12:49	
05/14 15:12:50.027 INFO |          packages:0190| Fetching test-cheets_FileSystemPermissions.tar.bz2 from http://100.115.245.201:8082/static/veyron_minnie-tot-chrome-pfq-informational/R68-10679.0.0-b2570321/autotest/packages to /usr/local/autotest/packages/test-cheets_FileSystemPermissions.tar.bz2
05/14 15:12:50.090 INFO |          packages:0207| Successfully fetched test-cheets_FileSystemPermissions.tar.bz2 from http://100.115.245.201:8082/static/veyron_minnie-tot-chrome-pfq-informational/R68-10679.0.0-b2570321/autotest/packages/test-cheets_FileSystemPermissions.tar.bz2
05/14 15:12:51.193 WARNI|  external_modules:0057| Unable to import cv2 due to: Incorrect cv2 version found, expected 2.4.8 <= version < 3.0.0, found version $Rev: 4557 $
05/14 15:12:51.436 INFO |              test:0907| Starting before_hook for cheets_FileSystemPermissions
05/14 15:12:51.454 INFO |              test:0911| before_hook completed
05/14 15:12:51.676 INFO |    battor_wrapper:0039| BattOr power monitor is not connected.
05/14 15:12:51.704 INFO |    battor_wrapper:0039| BattOr power monitor is not connected.
05/14 15:12:51.705 INFO |    browser_finder:0123| Chose browser: PossibleCrOSBrowser(browser_type=system)
05/14 15:12:51.748 INFO |    cros_interface:0575| (Re)starting the ui (logs the user out)
05/14 15:12:55.323 INFO |cros_browser_backe:0068| Restarting Chrome (pid=19170) with remote port
05/14 15:12:55.325 INFO |cros_browser_backe:0076| dbus-send --system --type=method_call --dest=org.chromium.SessionManager /org/chromium/SessionManager org.chromium.SessionManagerInterface.EnableChromeTesting boolean:true array:string:"--disable-arc-opt-in-verification,--enable-net-benchmarking,--metrics-recording-only,--no-default-browser-check,--no-first-run,--enable-gpu-benchmarking,--deny-permission-prompts,--autoplay-policy=no-user-gesture-required,--disable-component-extensions-with-background-pages,--disable-default-apps,--disable-search-geolocation-disclosure,--load-extension=/tmp/extension_DjMUW/autotest_private_ext,--enable-smooth-scrolling,--enable-threaded-compositing,--remote-debugging-port=0,--start-maximized,--ash-disable-system-sounds,--oobe-skip-postlogin,--disable-logging-redirect,--vmodule=*/chromeos/net/*=2\,*/chromeos/login/*=2\,chrome_browser_main_posix=2,--allow-failed-policy-fetch-for-test,--disable-gaia-services" array:string:
05/14 15:12:57.270 INFO |          __init__:0047| DoNothingForwarder started between 127.0.0.1:35145 and 35145
05/14 15:12:57.271 INFO |chrome_browser_bac:0118| Got devtools config: ws://127.0.0.1:35145/devtools/browser/1b4d60ae-0345-4740-b011-cecc9d3bc0b7
05/14 15:12:58.037 INFO |              oobe:0035| Invoking Oobe.loginForTesting
05/14 15:13:02.073 INFO |chrome_browser_bac:0118| Got devtools config: ws://127.0.0.1:35145/devtools/browser/1b4d60ae-0345-4740-b011-cecc9d3bc0b7
05/14 15:13:07.524 INFO |cros_browser_backe:0112| Browser is up!
05/14 15:13:07.587 INFO |           browser:0099| Browser started (pid=19215).
05/14 15:13:07.588 INFO |           browser:0102| OS: chromeos 
...
05/14 15:13:07.841 INFO |        arc_common:0037| Waiting for Android to boot completely.
05/14 15:15:06.802 ERROR|             utils:2730| Will raise error TestFail('Android did not boot!',) due to unexpected return: False
05/14 15:15:06.812 INFO |          arc_util:0104| Saving Android dumpstate.
05/14 15:15:16.480 INFO |          arc_util:0124| Android dumpstate successfully saved.
05/14 15:15:16.482 WARNI|              test:0637| The test failed with the following exception
Traceback (most recent call last):
  File "/usr/local/autotest/common_lib/test.py", line 598, in _exec
    _cherry_pick_call(self.initialize, *args, **dargs)
  File "/usr/local/autotest/common_lib/test.py", line 746, in _cherry_pick_call
    return func(*p_args, **p_dargs)
  File "/usr/local/autotest/common_lib/cros/arc.py", line 599, in initialize
    **chrome_kargs)
  File "/usr/local/autotest/common_lib/cros/chrome.py", line 185, in __init__
    arc_util.post_processing_after_browser(self)
  File "/usr/local/autotest/common_lib/cros/arc_util.py", line 67, in post_processing_after_browser
    arc_common.wait_for_android_boot()
  File "/usr/local/autotest/common_lib/cros/arc_common.py", line 42, in wait_for_android_boot
    sleep_interval=_BOOT_CHECK_INTERVAL_SECONDS)
  File "/usr/local/autotest/common_lib/utils.py", line 2731, in poll_for_condition
    raise exception
TestFail: Android did not boot!
05/14 15:15:16.497 INFO |               arc:0628| Skipping ARC cleanup: not initialized
05/14 15:15:16.509 INFO |              test:0924| Starting after_hook for cheets_FileSystemPermissions
05/14 15:15:17.493 INFO |              test:0928| after_hook completed
05/14 15:15:17.494 ERROR|          parallel:0026| child process failed
05/14 15:15:17.598 INFO |               job:0232| 		FAIL	cheets_FileSystemPermissions	cheets_FileSystemPermissions	timestamp=1526336117	localtime=May 14 15:15:17	Android did not boot!
05/14 15:15:17.617 INFO |               job:0232| 	END FAIL	cheets_FileSystemPermissions	cheets_FileSystemPermissions	timestamp=1526336117	localtime=May 14 15:15:17	
05/14 15:15:21.727 INFO |               job:0232| END GOOD	----	----	timestamp=1526336121	localtime=May 14 15:15:21
 
Cc: -kinaba@chromium.org yusukes@chromium.org
Owner: kinaba@chromium.org
Reassigning to non-PT constable as I don't have time to investigate today (meetings :/)

Comment 2 by kinaba@chromium.org, May 14 2018

Non-PST ARC Constable taking over.

Comment 3 by kinaba@chromium.org, May 15 2018

In https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/200103382-chromeos-test,
surfaceflinger is crashing first and then vold.


2018-05-14T15:13:13.704165-07:00 WARNING crash_reporter[20283]: [user] Received crash notification for surfaceflinger[19652] sig 6, user 656360 (ignoring - PID filtered out)
2018-05-14T15:13:13.704856-07:00 WARNING crash_reporter[20283]: [ARC] Received crash notification for surfaceflinger[19652] sig 6, user 656360 (developer build - not testing - always dumping)
2018-05-14T15:13:13.707773-07:00 INFO crash_reporter[20283]: State of crashed process [19652]: D (disk sleep)
2018-05-14T15:13:13.712270-07:00 INFO metrics_daemon[2778]: [INFO:metrics_daemon.cc(427)] Got org.chromium.CrashReporter.UserCrash D-Bus signal
2018-05-14T15:13:13.940431-07:00 INFO crash_reporter[20283]: Stored minidump to /home/user/e90684103dbf4433729b5acbd674f1e181492868/crash/surfaceflinger.20180514.151313.19652.dmp
2018-05-14T15:13:14.024174-07:00 INFO crash_reporter[20283]: Leaving core file at /home/user/e90684103dbf4433729b5acbd674f1e181492868/crash/surfaceflinger.20180514.151313.19652.core due to developer image
...
2018-05-14T15:13:23.063510-07:00 WARNING crash_reporter[20996]: [user] Received crash notification for surfaceflinger[20633] sig 6, user 656360 (ignoring - PID filtered out)
2018-05-14T15:13:23.064009-07:00 WARNING crash_reporter[20996]: [ARC] Received crash notification for surfaceflinger[20633] sig 6, user 656360 (developer build - not testing - always dumping)
...
2018-05-14T15:13:23.243653-07:00 WARNING crash_reporter[21005]: [user] Received crash notification for vold[19559] sig 6, user 655360 (ignoring - PID filtered out)
2018-05-14T15:13:23.244170-07:00 WARNING crash_reporter[21005]: [ARC] Received crash notification for vold[19559] sig 6, user 655360 (developer build - not testing - always dumping)



05-14 22:13:22.489   632   632 F DEBUG   : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
05-14 22:13:22.489   632   632 F DEBUG   : Build fingerprint: 'google/minnie/minnie_cheets:7.1.1/R68-10679.0.0/4779309:user/release-keys'
05-14 22:13:22.489   632   632 F DEBUG   : Revision: '0'
05-14 22:13:22.489   632   632 F DEBUG   : ABI: 'arm'
05-14 22:13:22.489   632   632 F DEBUG   : pid: 459, tid: 475, name: wayland-service  >>> /system/bin/surfaceflinger <<<
05-14 22:13:22.489   632   632 F DEBUG   : signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
05-14 22:13:22.494   632   632 F DEBUG   : Abort message: 'Assertion failed: !app_task_id'
05-14 22:13:22.494   632   632 F DEBUG   :     r0 00000000  r1 000001db  r2 00000006  r3 00000008
05-14 22:13:22.494   632   632 F DEBUG   :     r4 b1f7f978  r5 00000006  r6 b1f7f920  r7 0000010c
05-14 22:13:22.494   632   632 F DEBUG   :     r8 00000000  r9 00000007  sl ffffff9f  fp b1f7f588
05-14 22:13:22.495   632   632 F DEBUG   :     ip 0000000b  sp b1f7efc8  lr b39e4887  pc b39e70f0  cpsr 600f0010
05-14 22:13:22.545   632   632 F DEBUG   : 
05-14 22:13:22.545   632   632 F DEBUG   : backtrace:
05-14 22:13:22.546   632   632 F DEBUG   :     #00 pc 0004a0f0  /system/lib/libc.so (tgkill+12)
05-14 22:13:22.546   632   632 F DEBUG   :     #01 pc 00047883  /system/lib/libc.so (pthread_kill+34)
05-14 22:13:22.546   632   632 F DEBUG   :     #02 pc 0001d8f5  /system/lib/libc.so (raise+10)
05-14 22:13:22.546   632   632 F DEBUG   :     #03 pc 00019441  /system/lib/libc.so (__libc_android_abort+34)
05-14 22:13:22.546   632   632 F DEBUG   :     #04 pc 00017088  /system/lib/libc.so (abort+4)
05-14 22:13:22.546   632   632 F DEBUG   :     #05 pc 0000d495  /system/lib/libcutils.so (__android_log_assert+140)
05-14 22:13:22.546   632   632 F DEBUG   :     #06 pc 0001a44f  /system/lib/libwayland_service.so
05-14 22:13:22.546   632   632 F DEBUG   :     #07 pc 00019b8b  /system/lib/libwayland_service.so
05-14 22:13:22.546   632   632 F DEBUG   :     #08 pc 00034b0c  /system/lib/libwayland_service.so (ffi_call_SYSV+44)
05-14 22:13:22.546   632   632 F DEBUG   :     #09 pc 000345f7  /system/lib/libwayland_service.so (ffi_call+142)
05-14 22:13:22.546   632   632 F DEBUG   :     #10 pc 00033a21  /system/lib/libwayland_service.so
05-14 22:13:22.546   632   632 F DEBUG   :     #11 pc 0003263b  /system/lib/libwayland_service.so
05-14 22:13:22.546   632   632 F DEBUG   :     #12 pc 000322c1  /system/lib/libwayland_service.so (wl_display_dispatch_queue_pending+78)
05-14 22:13:22.546   632   632 F DEBUG   :     #13 pc 0002db75  /system/lib/libwayland_service.so
05-14 22:13:22.546   632   632 F DEBUG   :     #14 pc 00011fc7  /system/lib/libutils.so (_ZN7android6Looper9pollInnerEi+614)
05-14 22:13:22.546   632   632 F DEBUG   :     #15 pc 00011cd3  /system/lib/libutils.so (_ZN7android6Looper8pollOnceEiPiS1_PPv+26)
05-14 22:13:22.546   632   632 F DEBUG   :     #16 pc 0002d931  /system/lib/libwayland_service.so
05-14 22:13:22.546   632   632 F DEBUG   :     #17 pc 0000e47b  /system/lib/libutils.so (_ZN7android6Thread11_threadLoopEPv+270)
05-14 22:13:22.546   632   632 F DEBUG   :     #18 pc 00047353  /system/lib/libc.so (_ZL15__pthread_startPv+22)
05-14 22:13:22.546   632   632 F DEBUG   :     #19 pc 00019e9d  /system/lib/libc.so (__start_thread+6)



05-14 22:13:22.915   689   689 F DEBUG   : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
05-14 22:13:22.915   689   689 F DEBUG   : Build fingerprint: 'google/minnie/minnie_cheets:7.1.1/R68-10679.0.0/4779309:user/release-keys'
05-14 22:13:22.915   689   689 F DEBUG   : Revision: '0'
05-14 22:13:22.915   689   689 F DEBUG   : ABI: 'arm'
05-14 22:13:22.915   689   689 F DEBUG   : pid: 6, tid: 387, name: MojoThread  >>> /system/bin/vold <<<
05-14 22:13:22.915   689   689 F DEBUG   : signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
05-14 22:13:22.919   689   689 F DEBUG   : Abort message: 'Volume mounter host connection error!'
05-14 22:13:22.919   689   689 F DEBUG   :     r0 00000000  r1 00000183  r2 00000006  r3 00000008
05-14 22:13:22.919   689   689 F DEBUG   :     r4 b4d83978  r5 00000006  r6 b4d83920  r7 0000010c
05-14 22:13:22.919   689   689 F DEBUG   :     r8 ffffffff  r9 00000000  sl b51e85b4  fp b5192120
05-14 22:13:22.919   689   689 F DEBUG   :     ip 00000000  sp b4d82fb0  lr b553d887  pc b55400f0  cpsr 600f0010
05-14 22:13:22.932   689   689 F DEBUG   : 
05-14 22:13:22.932   689   689 F DEBUG   : backtrace:
05-14 22:13:22.932   689   689 F DEBUG   :     #00 pc 0004a0f0  /system/lib/libc.so (tgkill+12)
05-14 22:13:22.932   689   689 F DEBUG   :     #01 pc 00047883  /system/lib/libc.so (pthread_kill+34)
05-14 22:13:22.932   689   689 F DEBUG   :     #02 pc 0001d8f5  /system/lib/libc.so (raise+10)
05-14 22:13:22.932   689   689 F DEBUG   :     #03 pc 00019441  /system/lib/libc.so (__libc_android_abort+34)
05-14 22:13:22.932   689   689 F DEBUG   :     #04 pc 00017088  /system/lib/libc.so (abort+4)
05-14 22:13:22.932   689   689 F DEBUG   :     #05 pc 0000d495  /system/lib/libcutils.so (__android_log_assert+140)
05-14 22:13:22.932   689   689 F DEBUG   :     #06 pc 000042e5  /system/lib/libarcmounter.so
05-14 22:13:22.932   689   689 F DEBUG   :     #07 pc 0007573f  /system/lib/libmojo.so (_ZN4mojo23InterfaceEndpointClient11NotifyErrorERKN4base8OptionalINS_16DisconnectReasonEEE+98)
05-14 22:13:22.932   689   689 F DEBUG   :     #08 pc 00078d53  /system/lib/libmojo.so (_ZN4mojo8internal15MultiplexRouter22ProcessNotifyErrorTaskEPNS1_4TaskENS1_18ClientCallBehaviorEPN4base22SingleThreadTaskRunnerE+78)
05-14 22:13:22.932   689   689 F DEBUG   :     #09 pc 00078287  /system/lib/libmojo.so (_ZN4mojo8internal15MultiplexRouter12ProcessTasksENS1_18ClientCallBehaviorEPN4base22SingleThreadTaskRunnerE+178)
05-14 22:13:22.932   689   689 F DEBUG   :     #10 pc 00077933  /system/lib/libmojo.so (_ZN4mojo8internal15MultiplexRouter21OnPipeConnectionErrorEv+174)
05-14 22:13:22.932   689   689 F DEBUG   :     #11 pc 00073737  /system/lib/libmojo.so (_ZN4mojo9Connector11HandleErrorEbb+174)
05-14 22:13:22.933   689   689 F DEBUG   :     #12 pc 0007cd3f  /system/lib/libmojo.so (_ZN4mojo7Watcher13OnHandleReadyEj+82)
05-14 22:13:22.933   689   689 F DEBUG   :     #13 pc 0009227f  /system/lib/libchrome.so (_ZN4base5debug13TaskAnnotator7RunTaskEPKcPNS_11PendingTaskE+158)
05-14 22:13:22.933   689   689 F DEBUG   :     #14 pc 000a3eeb  /system/lib/libchrome.so (_ZN4base11MessageLoop7RunTaskEPNS_11PendingTaskE+190)
05-14 22:13:22.933   689   689 F DEBUG   :     #15 pc 000a40f9  /system/lib/libchrome.so (_ZN4base11MessageLoop21DeferOrRunPendingTaskENS_11PendingTaskE+18)
05-14 22:13:22.933   689   689 F DEBUG   :     #16 pc 000a430b  /system/lib/libchrome.so (_ZN4base11MessageLoop6DoWorkEv+154)
05-14 22:13:22.933   689   689 F DEBUG   :     #17 pc 000a5033  /system/lib/libchrome.so (_ZN4base18MessagePumpDefault3RunEPNS_11MessagePump8DelegateE+98)
05-14 22:13:22.933   689   689 F DEBUG   :     #18 pc 000a3d8f  /system/lib/libchrome.so (_ZN4base11MessageLoop10RunHandlerEv+62)
05-14 22:13:22.933   689   689 F DEBUG   :     #19 pc 000b6463  /system/lib/libchrome.so (_ZN4base7RunLoop3RunEv+42)
05-14 22:13:22.933   689   689 F DEBUG   :     #20 pc 00010425  /system/lib/libarcbridgeservice.so (_ZN3arc10MojoThread10threadLoopEv+72)
05-14 22:13:22.933   689   689 F DEBUG   :     #21 pc 0000e3fd  /system/lib/libutils.so (_ZN7android6Thread11_threadLoopEPv+144)
05-14 22:13:22.933   689   689 F DEBUG   :     #22 pc 00047353  /system/lib/libc.so (_ZL15__pthread_startPv+22)
05-14 22:13:22.933   689   689 F DEBUG   :     #23 pc 00019e9d  /system/lib/libc.so (__start_thread+6)

Comment 4 by kinaba@chromium.org, May 15 2018

By the way, where's the veyron_minnie-tot-chrome-pfq-informational builder lives?

https://luci-milo.appspot.com/search?q=veyron_minnie-tot-chrome-pfq-informational returns an empty search result,
or I cannot see the builder in the internal/external builder waterfall.

Comment 6 by kinaba@chromium.org, May 15 2018

Thanks!

Comment 8 by kinaba@chromium.org, May 15 2018

+Dom on multi-display.


Can there be a case that only this particular DUT is connected to an external display?

/var/log/chrome/* on chromeos2-row6-rack2-host3 always shows to "DRM configuring messages"

[6736:6748:0514/174307.168370:VERBOSE1:drm_display.cc(104)] DRM configuring: device=/sys/devices/display-subsystem.5/drm/card1 crtc=21 connector=32 origin=0,0 size=1280x800
[6736:6748:0514/174307.315002:VERBOSE1:drm_display.cc(104)] DRM configuring: device=/sys/devices/display-subsystem.5/drm/card1 crtc=27 connector=35 origin=0,860 size=1024x768

while on other Minnie DUTs I see only the first one.

I found some bugs in the past that inside wl_display_dispatch_queue_pending() a crash is hit with external displays: b/77328081

Comment 9 by kinaba@chromium.org, May 15 2018

Cc: kinaba@chromium.org
Owner: yusukes@chromium.org
(passing back to the PST constable)

my conclusion today is #8: one particular Minnie in the lab is (for whatever reasons) connected to an external display, and it seems we encounter a surfaceflinger crash when  an external display is connected.
Owner: domlasko...@chromium.org
kinaba's idea seems correct. If I connect an external display to my minnie with xbuddy://remote/veyron_minnie/R68-10681.0.0/test, the container crash-loops:

05-15 13:49:08.274   526   547 F wayland-service: Assertion failed: !app_task_id
05-15 13:49:08.275   526   547 F libc    : Fatal signal 6 (SIGABRT), code -6 in tid 547 (wayland-service)
05-15 13:49:08.275     5     5 W         : debuggerd: handling request: pid=526 uid=1000 gid=1003 tid=547
05-15 13:49:08.285   684   684 E         : debuggerd: Unable to connect to activity manager (connect failed: Connection refused)
05-15 13:49:08.285   684   684 F DEBUG   : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
05-15 13:49:08.285   684   684 F DEBUG   : Build fingerprint: 'google/minnie/minnie_cheets:7.1.1/R68-10681.0.0/4779680:user/release-keys'
05-15 13:49:08.285   684   684 F DEBUG   : Revision: '0'
05-15 13:49:08.285   684   684 F DEBUG   : ABI: 'arm'
05-15 13:49:08.286   684   684 F DEBUG   : pid: 526, tid: 547, name: wayland-service  >>> /system/bin/surfaceflinger <<<
05-15 13:49:08.286   684   684 F DEBUG   : signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
05-15 13:49:08.289   684   684 F DEBUG   : Abort message: 'Assertion failed: !app_task_id'
05-15 13:49:08.289   684   684 F DEBUG   :     r0 00000000  r1 00000223  r2 00000006  r3 00000008
05-15 13:49:08.289   684   684 F DEBUG   :     r4 ad0a5978  r5 00000006  r6 ad0a5920  r7 0000010c
05-15 13:49:08.289   684   684 F DEBUG   :     r8 00000000  r9 00000007  sl ffffff9f  fp ad0a5588
05-15 13:49:08.289   684   684 F DEBUG   :     ip 0000000b  sp ad0a4fc8  lr aecb2887  pc aecb50f0  cpsr 600f0010
05-15 13:49:08.308   684   684 F DEBUG   : 
05-15 13:49:08.308   684   684 F DEBUG   : backtrace:
05-15 13:49:08.308   684   684 F DEBUG   :     #00 pc 0004a0f0  /system/lib/libc.so (tgkill+12)
05-15 13:49:08.308   684   684 F DEBUG   :     #01 pc 00047883  /system/lib/libc.so (pthread_kill+34)
05-15 13:49:08.308   684   684 F DEBUG   :     #02 pc 0001d8f5  /system/lib/libc.so (raise+10)
05-15 13:49:08.308   684   684 F DEBUG   :     #03 pc 00019441  /system/lib/libc.so (__libc_android_abort+34)
05-15 13:49:08.308   684   684 F DEBUG   :     #04 pc 00017088  /system/lib/libc.so (abort+4)
05-15 13:49:08.308   684   684 F DEBUG   :     #05 pc 0000d495  /system/lib/libcutils.so (__android_log_assert+140)
05-15 13:49:08.308   684   684 F DEBUG   :     #06 pc 0001a44f  /system/lib/libwayland_service.so
05-15 13:49:08.308   684   684 F DEBUG   :     #07 pc 00019b8b  /system/lib/libwayland_service.so
05-15 13:49:08.308   684   684 F DEBUG   :     #08 pc 00034b0c  /system/lib/libwayland_service.so (ffi_call_SYSV+44)
05-15 13:49:08.308   684   684 F DEBUG   :     #09 pc 000345f7  /system/lib/libwayland_service.so (ffi_call+142)
05-15 13:49:08.309   684   684 F DEBUG   :     #10 pc 00033a21  /system/lib/libwayland_service.so
05-15 13:49:08.309   684   684 F DEBUG   :     #11 pc 0003263b  /system/lib/libwayland_service.so
05-15 13:49:08.309   684   684 F DEBUG   :     #12 pc 000322c1  /system/lib/libwayland_service.so (wl_display_dispatch_queue_pending+78)
05-15 13:49:08.309   684   684 F DEBUG   :     #13 pc 0002db75  /system/lib/libwayland_service.so
05-15 13:49:08.309   684   684 F DEBUG   :     #14 pc 00011fc7  /system/lib/libutils.so (_ZN7android6Looper9pollInnerEi+614)
05-15 13:49:08.309   684   684 F DEBUG   :     #15 pc 00011cd3  /system/lib/libutils.so (_ZN7android6Looper8pollOnceEiPiS1_PPv+26)
05-15 13:49:08.309   684   684 F DEBUG   :     #16 pc 0002d931  /system/lib/libwayland_service.so
05-15 13:49:08.309   684   684 F DEBUG   :     #17 pc 0000e47b  /system/lib/libutils.so (_ZN7android6Thread11_threadLoopEPv+270)
05-15 13:49:08.309   684   684 F DEBUG   :     #18 pc 00047353  /system/lib/libc.so (_ZL15__pthread_startPv+22)
05-15 13:49:08.309   684   684 F DEBUG   :     #19 pc 00019e9d  /system/lib/libc.so (__start_thread+6)


Dom who owns multi display stuff will take a look. Reassigning to him. Dom, you can download full logs from https://drive.google.com/open?id=1LTxK8C6fN__NmxND788BBFijtIQTskWY .




Comment 11 by derat@chromium.org, May 17 2018

Dom, please provide an update. This builder has been failing all week because of this.

If you can't fix the code quickly, can we just remove the display from this particular device or remove it from the pool?
Status: Started (was: Assigned)
I'm currently investigating and should have a fix today. I can reproduce on Caroline, so it's a general regression for multi-display ARC.
The regression was introduced by [1], though it will have to be fixed on the Android side. I will upload a CL soon.

[1] https://chromium.googlesource.com/chromium/src/+/f8f9b2ef64b225e7b6fdb21ec17a7a260eb06038
Status: Fixed (was: Started)
The fix (ag/4077380) just landed. The builder should turn green once the ARC image picks it up.

Comment 15 by derat@chromium.org, May 18 2018

Thanks! Well, it would turn green if it weren't for the video decoder failure that was introduced in the meantime. :-P
Labels: ArcConstable

Sign in to add a comment