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

Issue 853804 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Jul 9
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

security_SandboxedServices fails on Pyro "One or more processes failed sandboxing: ['evemu-device']"

Project Member Reported by bhthompson@google.com, Jun 18 2018

Issue description

security_SandboxedServices failed on 68:

https://stainless.corp.google.com/search?exclude_retried=false&first_date=2018-06-10&master_builder_name=&builder_name_number=&shard=&exclude_acts=true&builder_name=&master_builder_name_number=&owner=chromeos-test&retry=&exclude_cts=false&exclude_non_production=false&hostname=&board=&test=%5Esecurity_SandboxedServices%24&suite=%5CQbvt-inline%5CE&build=%5ER68%5C-10718%5C.26%5C.0%24&status=FAIL&status=ERROR&status=ABORT&reason=&waterfall=chromeos(_release%7C)&exclude_not_run=false&last_date=2018-06-24&exclude_non_release=true&exclude_au=false&model=pyro&view=list

...
06/18 07:54:45.824 INFO |security_Sandboxed:0208| Loading baseline /usr/local/autotest/tests/security_SandboxedServices/baseline
06/18 07:54:47.020 WARNI|security_Sandboxed:0108| Failed to read mountinfo for pid 25976: [Errno 2] No such file or directory: '/proc/25976/mountinfo'
06/18 07:54:47.059 WARNI|security_Sandboxed:0365| Stale baselines: set(['thermal.sh', 'daisydog', 'cros_camera_service', 'brcm_patchram_p', 'tcsd', 'netfilter-queue', 'firewalld', 'app_process', 'wimax-manager', 'arc-networkd', 'upstart-udev-br', 'cromo', 'cros_camera_algo', 'arc-obb-mounter', 'lid_touchpad_he'])
06/18 07:54:47.065 WARNI|security_Sandboxed:0368| New services: set(['main', 'newblued', 'evemu-device', 'btdispatch', 'cat'])
06/18 07:54:47.072 ERROR|security_Sandboxed:0379| New services are not allowed to run as root, but these are: ['evemu-device']
06/18 07:54:47.078 ERROR|security_Sandboxed:0383| Failed sandboxing: ['evemu-device']
06/18 07:54:47.174 WARNI|              test:0637| The test failed with the following exception
Traceback (most recent call last):
  File "/usr/local/autotest/common_lib/test.py", line 631, in _exec
    _call_test_function(self.execute, *p_args, **p_dargs)
  File "/usr/local/autotest/common_lib/test.py", line 831, in _call_test_function
    return func(*args, **dargs)
  File "/usr/local/autotest/common_lib/test.py", line 495, in execute
    dargs)
  File "/usr/local/autotest/common_lib/test.py", line 362, in _call_run_once_with_retry
    postprocess_profiled_run, args, dargs)
  File "/usr/local/autotest/common_lib/test.py", line 400, in _call_run_once
    self.run_once(*args, **dargs)
  File "/usr/local/autotest/tests/security_SandboxedServices/security_SandboxedServices.py", line 385, in run_once
    sandbox_delta)
TestFail: One or more processes failed sandboxing: ['evemu-device']
06/18 07:54:47.197 INFO |              test:0924| Starting after_hook for security_SandboxedServices
...
 
Cc: bhthompson@chromium.org
Owner: kathrelk...@chromium.org
Summary: security_SandboxedServices fails on Pyro "One or more processes failed sandboxing: ['evemu-device']" (was: security_SandboxedServices fails One or more processes failed sandboxing: ['evemu-device'])
Maybe a flake? Nothing changed interesting for Chrome OS from a passing run. 

Looks like this process is part of a test?

Is this in your jurisdiction Katherine?
Cc: jorgelo@chromium.org kathrelk...@chromium.org
Components: Infra>Client>ChromeOS>Test
Owner: derat@chromium.org
Status: Started (was: Untriaged)
I tried to fix all of the tests I could find that were leaking evemu-device in  issue 795128 , but I think we can still see this (with no good workaround) when tests get aborted. I see in  issue 792541  that we just whitelisted adb to get around this, so I'm planning to do the same thing with evemu-device here.
That is reasonable.
Project Member

Comment 4 by bugdroid1@chromium.org, Jul 9

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/autotest/+/3defff0054ea6590ae07889e366c324e715e862b

commit 3defff0054ea6590ae07889e366c324e715e862b
Author: Daniel Erat <derat@chromium.org>
Date: Mon Jul 09 19:42:43 2018

autotest: Add proc exclusions to security_SandboxedServices.

Exclude "cras_test_clien" and "evemu-device" in
security_SandboxedServices. These processes can be left
behind by earlier misbehaving or aborted tests.

BUG= chromium:795128 , chromium:853804 , chromium:860107 
TEST=none

Change-Id: I5db939d08ddda1709fde0b2b671d0389f66d8e33
Reviewed-on: https://chromium-review.googlesource.com/1125513
Commit-Ready: Dan Erat <derat@chromium.org>
Tested-by: Dan Erat <derat@chromium.org>
Reviewed-by: Jorge Lucangeli Obes <jorgelo@chromium.org>

[modify] https://crrev.com/3defff0054ea6590ae07889e366c324e715e862b/client/site_tests/security_SandboxedServices/exclude

Status: Fixed (was: Started)

Sign in to add a comment