daisy and daisy-skate builders frequently fail to execute sandbox_linux_unittests |
||
Issue descriptionThis daisy-release (https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?buildbucketId=8933514021121328336) build fails HWTest [bvt-inline] with the following in logs. Bad permissions? 10/05 07:25:44.638 WARNI| test:0606| The test failed with the following exception Traceback (most recent call last): File "/usr/local/autotest/common_lib/test.py", line 600, in _exec _call_test_function(self.execute, *p_args, **p_dargs) File "/usr/local/autotest/common_lib/test.py", line 800, in _call_test_function return func(*args, **dargs) File "/usr/local/autotest/common_lib/test.py", line 464, in execute postprocess_profiled_run, args, dargs) File "/usr/local/autotest/common_lib/test.py", line 371, in _call_run_once self.run_once(*args, **dargs) File "/usr/local/autotest/tests/security_SandboxLinuxUnittests/security_SandboxLinuxUnittests.py", line 21, in run_once self.run_chrome_test_binary(self.BINARY) File "/usr/local/autotest/cros/chrome_binary_test.py", line 161, in run_chrome_test_binary raise error.TestFail(fail_reason) TestFail: Cannot execute command /usr/local/autotest/deps/chrome_test/test_src/out/Release/sandbox_linux_unittests. Permissions: /usr/local/autotest/deps/chrome_test/test_src/out/Release/sandbox_linux_unittests 0100755; /usr/local/autotest/deps/chrome_test/test_src/out/Release 040755; /usr/local/autotest/deps/chrome_test/test_src/out 040755; /usr/local/autotest/deps/chrome_test/test_src 040755; /usr/local/autotest/deps/chrome_test 040755; /usr/local/autotest/deps 040755; /usr/local/autotest 040755; /usr/local 040700; /usr 040755; / 040755
,
Nov 24
I'm seeing similar errors on daisy and daisy_skate when the security.SandboxLinuxUnittests Tast test tries to run the binary. See e.g. http://stainless/browse/chromeos-autotest-results/259875885-chromeos-test/ : sudo: unable to execute /usr/local/libexec/chrome-binary-tests/sandbox_linux_unittests: Permission denied The executable is installed by the chrome-binary-tests ebuild, and I don't see anything weird there: src_install() { exeinto /usr/libexec/chrome-binary-tests # The binary tests in ${BINARY_DIR} are built by chrome-chrome. BINARY_DIR="${SYSROOT}/usr/local/build/autotest/client/deps/chrome_test/test_src/out/Release" doexe "${BINARY_DIR}/jpeg_decode_accelerator_unittest" doexe "${BINARY_DIR}/ozone_gl_unittests" doexe "${BINARY_DIR}/sandbox_linux_unittests" doexe "${BINARY_DIR}/video_decode_accelerator_unittest" doexe "${BINARY_DIR}/video_encode_accelerator_unittest" doexe "${BINARY_DIR}/wayland_client_perftests" } I also just SSH-ed to chromeos15-row3-rack9-host1.cros and successfully ran the following as root, which I believe is the same thing that this tests are doing: sudo -u chronos CHROME_DEVEL_SANDBOX=/opt/google/chrome/chrome-sandbox /usr/local/libexec/chrome-binary-tests/sandbox_linux_unittests I think that Jorge added this test, but he's out. Mattias, any ideas about why we're unable to execute this on daisy and daisy_skate? To be clear, I don't see this exec failure on *any* other boards.
,
Nov 24
And to be more clear, it also passes sometimes on daisy-based boards: http://stainless/search?view=list&first_date=2018-11-18&last_date=2018-11-24&test=tast.security.SandboxLinuxUnittests&board=%5Edaisy&status=GOOD&status=WARN&status=FAIL&status=ERROR&status=ABORT&exclude_cts=false&exclude_not_run=false&exclude_non_release=true&exclude_au=true&exclude_acts=true&exclude_retried=true&exclude_non_production=false |
||
►
Sign in to add a comment |
||
Comment 1 by apronin@chromium.org
, Oct 5