desktopui_KillRestart fails on eve-tot-chrome-pfq-informational |
||||||
Issue descriptioneve-tot-chrome-pfq-informational: https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?buildbucketId=8938564560115149424 desktopui_KillRestart.session FAIL: Autotest client terminated unexpectedly: DUT is no longer pingable, it may have rebooted or hung. There's a bunch of ARC related errors: 2018-08-10T19:55:52.927734+00:00 ERR arc-lifetime[27302]: [ERROR:arc_setup_util.cc(372)] Failed to lazy-umount /run/arc/shared_mounts/cache: No such file or directory 2018-08-10T19:55:52.927768+00:00 ERR arc-lifetime[27302]: [ERROR:arc_setup_util.cc(372)] Failed to lazy-umount /run/arc/shared_mounts/data: No such file or directory 2018-08-10T19:55:52.927794+00:00 ERR arc-lifetime[27302]: [ERROR:arc_setup_util.cc(381)] Failed to stat /run/arc/shared_mounts/demo_apps: No such file or directory 2018-08-10T19:55:52.935835+00:00 ERR arc-lifetime[27302]: [ERROR:arc_setup_util.cc(372)] Failed to lazy-umount /run/arc/media/removable: Invalid argument 2018-08-10T19:55:52.969945+00:00 ERR arc-lifetime[27302]: [ERROR:arc_setup_util.cc(372)] Failed to lazy-umount /opt/google/containers/android/rootfs/android-data: Invalid argument 2018-08-10T19:55:52.983325+00:00 ERR arc-lifetime[27302]: [ERROR:arc_setup_util.cc(372)] Failed to lazy-umount /proc/sys/fs/binfmt_misc: Invalid argument 2018-08-10T19:55:52.984061+00:00 ERR arc-lifetime[27302]: [ERROR:arc_setup_util.cc(372)] Failed to lazy-umount /opt/google/containers/android/rootfs/root/system/lib/arm: Invalid argument selinux_violation: type=1400 avc: denied { sigchld } for pid=1 comm="init" scontext=u:r:init:s0 tcontext=u:r:cros_init:s0 tclass=process permissive=0 And a crash of coreutils: Operating system: Linux 0.0.0 Linux 4.4.146-14679-g93e093804ba9 #1 SMP PREEMPT Fri Aug 10 10:22:04 PDT 2018 x86_64 CPU: amd64 family 6 model 142 stepping 9 1 CPU GPU: UNKNOWN Crash reason: SIGSYS Crash address: 0x0 Process uptime: not available Thread 0 (crashed) 0 libc-2.23.so!__statfs + 0x7 1 libselinux.so.1!init_lib [init.c : 38 + 0xb] 2 ld-2.23.so!call_init [dl-init.c : 72 + 0xb] 3 ld-2.23.so!_dl_init [dl-init.c : 30 + 0x17] 4 ld-2.23.so + 0xd9a 5 coreutils!_init + 0x1420 Loaded modules: 0x57c83122d000 - 0x57c831329fff coreutils ??? (main) 0x7999003d5000 - 0x7999003d6fff libdl-2.23.so ??? 0x7999005d9000 - 0x799900779fff libc-2.23.so ??? 0x799900984000 - 0x79990099afff libpthread-2.23.so ??? 0x799900ba1000 - 0x799900ba6fff librt-2.23.so ??? 0x799900da9000 - 0x799900dcdfff ld-2.23.so ??? 0x799900efb000 - 0x799900f8bfff libpcre.so.1.2.9 ??? 0x799900f8f000 - 0x799900f92fff libattr.so.1.1.0 ??? 0x799900f96000 - 0x799900fb8fff libselinux.so.1 ??? 0x7ffd09789000 - 0x7ffd0978afff linux-gate.so ???
,
Aug 10
It just failed, not sure if it'll fail again. jkop@ could you please take a look to see if there's something on this DUT?
,
Aug 13
It's been fine for a few days.
,
Aug 17
It's failed in the last two runs: https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?buildbucketId=8937979427588344416 https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?buildbucketId=8937957916953313744
,
Sep 10
,
Nov 28
Seeing the same failure for Nasher board - https://screenshot.googleplex.com/T4xcGriyt2o
,
Jan 7
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by derat@chromium.org
, Aug 10