New issue
Advanced search Search tips

Issue 821185 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 795128
Owner:
Closed: Mar 2018
Cc:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

[veyron_minnie-tot-chrome-pfq-informational] failed hwtest

Project Member Reported by wzang@chromium.org, Mar 12 2018

Issue description

Please see 
https://uberchromegw.corp.google.com/i/chromeos.chrome/builders/veyron_minnie-tot-chrome-pfq-informational/builds/7499 for an example.

security_SandboxedServices.ERROR:

03/12 11:38:16.353 ERROR|security_Sandboxed:0334| New services are not allowed to run as root, but these are: ['evemu-device']
03/12 11:38:16.359 ERROR|security_Sandboxed:0338| Failed sandboxing: ['evemu-device']

The test is flaky. The failure appeared in four of the builds since Mar 2nd.


 

Comment 1 by wzang@chromium.org, Mar 12 2018

Cc: glevin@chromium.org
Owner: jorgelo@chromium.org
Status: Assigned (was: Untriaged)
The error message comes from:

https://cs.corp.google.com/chromeos_public/src/third_party/autotest/files/client/site_tests/security_SandboxedServices/security_SandboxedServices.py?q=%22New+services+are+not+allowed+to+run+as+root%22&dr=C&l=333

jorgelo@, based on the git history, you should be familiar with this directory. Could you please suggest the right person to own this? Thanks so much.
This means somebody added a new service running as root. You should find
who added that.

Comment 3 by glevin@chromium.org, Mar 13 2018

This happened again today, but only seems to be intermittent:
https://uberchromegw.corp.google.com/i/chromeos.chrome/builders/veyron_minnie-tot-chrome-pfq-informational/builds/7510

The only code reference I see to "evemu-device" is here:
https://cs.corp.google.com/chromeos_public/src/third_party/autotest/files/client/cros/input_playback/input_playback.py?type=cs&q=evemu-device+file:%5Esrc/third_party/autotest/+package:%5Echromeos_public$&l=164

... but I don't see any recent changes in that folder that are likely culprits.  Also, looks like the same problem as  Issue 795128 ?

Comment 5 by vapier@chromium.org, Mar 17 2018

Mergedinto: 795128
Status: Duplicate (was: Assigned)

Sign in to add a comment