Issue metadata
Sign in to add a comment
|
[veyron_minnie-tot-chrome-pfq-informational] failed hwtest |
||||||||||||||||||||||
Issue descriptionPlease 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.
,
Mar 13 2018
This means somebody added a new service running as root. You should find who added that.
,
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 ?
,
Mar 15 2018
Same flake observed on caroline-tot-chrome-pfq-informational: https://uberchromegw.corp.google.com/i/chromeos.chrome/builders/caroline-tot-chrome-pfq-informational/builds/1186
,
Mar 17 2018
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by wzang@chromium.org
, Mar 12 2018Owner: jorgelo@chromium.org
Status: Assigned (was: Untriaged)