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

Issue 842857 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: May 2018
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

caroline-arcnext: No such file or directory: '/run/arc/bugreport/pipe

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

Issue description

Seems to be a reoccurring failure where the arc tests can't run because this file is missing. Here are a few examples:


https://luci-milo.appspot.com/buildbot/chromeos/caroline-arcnext-paladin/260
https://luci-milo.appspot.com/buildbot/chromeos/caroline-arcnext-paladin/455
https://luci-milo.appspot.com/buildbot/chromeos/caroline-arcnext-paladin/410




05/07 23:59:33.700 ERROR|             utils:2730| Will raise error TestFail('Android did not boot!',) due to unexpected return: False
05/07 23:59:33.704 ERROR|          arc_util:0127| Failed to save Android dumpstate.
Traceback (most recent call last):
  File "/usr/local/autotest/common_lib/cros/arc_util.py", line 110, in _save_android_dumpstate
    fd = os.open(_DUMPSTATE_PIPE_PATH, os.O_RDONLY | os.O_NONBLOCK)
OSError: [Errno 2] No such file or directory: '/run/arc/bugreport/pipe'
05/07 23:59:33.751 ERROR|              test:0645| Ignoring exception during cleanup() phase:
05/07 23:59:33.755 ERROR|         traceback:0013| Traceback (most recent call last):
05/07 23:59:33.759 ERROR|         traceback:0013|   File "/usr/local/autotest/common_lib/test.py", line 643, in _exec
05/07 23:59:33.763 ERROR|         traceback:0013|     _cherry_pick_call(self.cleanup, *args, **dargs)
05/07 23:59:33.768 ERROR|         traceback:0013|   File "/usr/local/autotest/common_lib/test.py", line 746, in _cherry_pick_call
05/07 23:59:33.772 ERROR|         traceback:0013|     return func(*p_args, **p_dargs)
05/07 23:59:33.776 ERROR|         traceback:0013|   File "/usr/local/autotest/tests/cheets_StartAndroid_P/cheets_StartAndroid_P.py", line 35, in cleanup
05/07 23:59:33.780 ERROR|         traceback:0013|     value=self._run_times[index],
05/07 23:59:33.784 ERROR|         traceback:0013| IndexError: list index out of range
05/07 23:59:33.788 ERROR|              test:0649| Now raising the earlier <class 'autotest_lib.client.common_lib.error.TestFail'> error
 
Cc: mtyin@chromium.org dgreid@chromium.org

Comment 2 by uekawa@google.com, May 15 2018

Cc: yusukes@chromium.org lhchavez@chromium.org kinaba@chromium.org
Labels: ArcConstable
hmmm did we miss something when we got 3.18 working ?

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

If I remember correctly the mentioned failure is not the cause but rather a consequence of some other failure.

_save_android_dumpstate() is a log-collection method called after a test is failed.

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

Took a look at one instance:
https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/199909694-chromeos-test/chromeos6-row2-rack21-host20/cheets_StartAndroid_P.stress/
It is a android-run_oci failure.


2018-05-14T04:30:38.823712+00:00 WARNING crash_reporter[5963]: [user] Received crash notification for run_oci[5961] sig 11, user 655360 (developer build - not testing - always dumping)
2018-05-14T04:30:38.824993+00:00 INFO crash_reporter[5963]: State of crashed process [5961]: S (sleeping)
2018-05-14T04:30:38.826480+00:00 INFO metrics_daemon[3171]: [INFO:metrics_daemon.cc(427)] Got org.chromium.CrashReporter.UserCrash D-Bus signal
2018-05-14T04:30:38.835014+00:00 INFO crash_reporter[5963]: Stored minidump to /var/spool/crash/run_oci.20180513.213038.5961.dmp
2018-05-14T04:30:38.835252+00:00 INFO crash_reporter[5963]: Leaving core file at /var/spool/crash/run_oci.20180513.213038.5961.core due to developer image
2018-05-14T04:30:38.881222+00:00 ERR session_manager[5302]: [ERROR:android_oci_wrapper.cc(154)] run_oci failed to launch Android container. WIFEXITED: 1 WEXITSTATUS: 255


https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/199909694-chromeos-test/chromeos6-row2-rack21-host20/cheets_StartAndroid_P.stress/sysinfo/var/log_diff/android/
...
libminijail[5904]: mount /run/arc/properties/default.prop -> /default.prop type 'bind'
libminijail[5904]: mount /run/arc/properties/build.prop -> /system/build.prop type 'bind'
libminijail[5904]: mount tmpfs -> /mnt type 'tmpfs'
libminijail[5904]: mount tmpfs -> /mnt/vendor type 'tmpfs'
libminijail[5904]: mount: /sys/kernel/config/sdcardfs -> /opt/google/containers/android/rootfs/root/config/sdcardfs: No such file or directory
libminijail[5904]: mount_one failed: No such file or directory
[5968:0513/213038:ERROR:libcontainer_util.cc(95)] Failed to open /proc/5961/ns/mnt: No such file or directory
libminijail[5904]: child process 5961 received signal 11
[5904:0513/213038:ERROR:libcontainer.cc(483)] Failed to unmount /opt/google/containers/android/rootfs/root/: Invalid argument
[5904:0513/213038:ERROR:run_oci.cc(773)] start failed: /run/containers/android-run_oci: Operation not permitted

Comment 5 by dgreid@google.com, May 15 2018

Labels: -Pri-3 Pri-2
Did sdcardfs get added to 4.4 and not 3.18 and 3.14?

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

Status: WontFix (was: Untriaged)
WontFix. Everything looks working as intended.

* "No such file or directory: '/run/arc/bugreport/pipe'" happens only after there were some other failure that already made the test failing. If the failure aborted the Android container, it's the normal state that the file does not exist.

* The latest instance is from the CQ run https://luci-milo.appspot.com/buildbot/chromeos/caroline-arcnext-paladin/455 that is exactly exercising the esdfs support CLs, which are causing the failure. Hence we correctly blocked the faulty CLs.

Sign in to add a comment