More detaield errors in log:

cautotest_lib.client.common_lib.error
UnhandledTestFail
p0
(S'Unhandled IOError: [Errno 2] No such file or directory: \'/proc/16531/maps\'\nTraceback (most recent call last):\n  File "/usr/local/autotest/common_lib/test.py", line 804, in _call_test_function\n    return func(*args, **dargs)\n  File "/usr/local/autotest/common_lib/test.py", line 461, in execute\n    dargs)\n  File "/usr/local/autotest/common_lib/test.py", line 347, in _call_run_once_with_retry\n    postprocess_profiled_run, args, dargs)\n  File "/usr/local/autotest/common_lib/test.py", line 376, in _call_run_once\n    self.run_once(*args, **dargs)\n  File "/usr/local/autotest/tests/security_ASLR/security_ASLR.py", line 333, in run_once\n    test_results = self.test_randomization(process)\n  File "/usr/local/autotest/tests/security_ASLR/security_ASLR.py", line 206, in test_randomization\n    mappings.append(self.map(pid))\n  File "/usr/local/autotest/tests/security_ASLR/security_ASLR.py", line 256, in map\n    maps_file = open("/proc/%s/maps" % pid)\nIOError: [Errno 2] No such file or directory: \'/proc/16531/maps\'\n'
p1
tp2
Rp3

Issue 618336 has been merged into this issue.

"No such file or directory: '/proc/16531/maps'" probably just means that the process with PID 16531 was already dead.

who owns this test script now?

The bot passed in the next build. So the previous failure could be caused by some flaky issues.

https://uberchromegw.corp.google.com/i/chromeos/builders/lumpy-chrome-pfq/builds/8736

[bvt-inline] security_ASLR Failure on falco-chrome-pfq/R57-9032.0.0-rc1

This report is automatically generated to track the following Failure:
Test: security_ASLR.
Suite: bvt-inline.
Chrome Version: 57.0.2936.0.
Build: falco-chrome-pfq/R57-9032.0.0-rc1.

Reason:
Unhandled IOError: [Errno 2] No such file or directory: '/proc/6652/maps'.
build artifacts: https://storage.cloud.google.com/?arg=chromeos-image-archive/falco-chrome-pfq/R57-9032.0.0-rc1.
results log: http://cautotest.corp.google.com/tko/retrieve_logs.cgi?job=/results/87925210-chromeos-test/chromeos2-row3-rack1-host19/debug/.
status log: http://cautotest.corp.google.com/tko/retrieve_logs.cgi?job=/results/87925210-chromeos-test/chromeos2-row3-rack1-host19/status.log.
buildbot stages: NA.
job link: http://cautotest.corp.google.com/afe/#tab_id=view_job&object_id=87925210.

You may want to check the test history on wmatrix: https://wmatrix.googleplex.com/unfiltered?hide_missing=True&tests=security_ASLR
You may also want to check the test retry dashboard in case this is a flakey test: https://wmatrix.googleplex.com/retry_teststats/?days_back=30&tests=security_ASLR


ANCHOR  TestFailure{bvt-inline,security_ASLR,Unhandled IOError: [Errno 2] No such file or directory: '/proc/6652/maps'}

[bvt-inline] security_ASLR Failure on tricky-tot-chrome-pfq-informational/R57-9062.0.0-b2853

This report is automatically generated to track the following Failure:
Test: security_ASLR.
Suite: bvt-inline.
Chrome Version: 57.0.2946.0.
Build: tricky-tot-chrome-pfq-informational/R57-9062.0.0-b2853.

Reason:
Unhandled IOError: [Errno 2] No such file or directory: '/proc/4767/maps'.
build artifacts: https://storage.cloud.google.com/?arg=chromeos-image-archive/tricky-tot-chrome-pfq-informational/R57-9062.0.0-b2853.
results log: http://cautotest.corp.google.com/tko/retrieve_logs.cgi?job=/results/89573437-chromeos-test/chromeos4-row2-rack3-host6/debug/.
status log: http://cautotest.corp.google.com/tko/retrieve_logs.cgi?job=/results/89573437-chromeos-test/chromeos4-row2-rack3-host6/status.log.
buildbot stages: NA.
job link: http://cautotest.corp.google.com/afe/#tab_id=view_job&object_id=89573437.

You may want to check the test history on wmatrix: https://wmatrix.googleplex.com/unfiltered?hide_missing=True&tests=security_ASLR
You may also want to check the test retry dashboard in case this is a flakey test: https://wmatrix.googleplex.com/retry_teststats/?days_back=30&tests=security_ASLR


ANCHOR  TestFailure{bvt-inline,security_ASLR,Unhandled IOError: [Errno 2] No such file or directory: '/proc/4767/maps'}

As in comment #10, we have another instance of this failure on the tricky-tot-chrome-pfq-informational. 
It might be a flake, but we ought to keep an eye on the next build run.

This is definitely flake. In the last test, debugd had pid 4765:

12/08 13:07:40.972 DEBUG|        base_utils:0280| [stdout] debugd start/running, process 4765

but apparently `pidof debugd` returned 4767 first. Maybe it had forked just at the time we were probing and went with that pid. It's probably much more robust to always require a parent process, that way we won't have noise due to child processes.

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

commit e04cc7967aba1652f1922bb04bafa7d417870210
Author: Luis Hector Chavez <lhchavez@google.com>
Date: Mon Dec 12 21:46:58 2016

security_ASLR: Make finding processes more robust

There have been a few flaky runs where the first line of `pidof ${name}`
is not the process we were looking for and goes away before we are able
to look for /proc/${pid}/maps. This change removes the code path where
we only look at `pidof` and instead always requires that the parent
process is specified to reduce flake.

BUG= chromium:618382 
TEST=test_that cyan security_ASLR
TEST=test_that lakitu security_ASLR

Change-Id: I5d296657da7c6561da86266724692f9659c15163
Reviewed-on: https://chromium-review.googlesource.com/419096
Commit-Ready: Luis Hector Chavez <lhchavez@chromium.org>
Tested-by: Luis Hector Chavez <lhchavez@chromium.org>
Reviewed-by: Jorge Lucangeli Obes <jorgelo@chromium.org>
Reviewed-by: Daniel Wang <wonderfly@google.com>
Reviewed-by: Andrey Ulanov <andreyu@google.com>

[modify] https://crrev.com/e04cc7967aba1652f1922bb04bafa7d417870210/client/site_tests/security_ASLR/security_ASLR.py

This should flake no more!

Closing. Please reopen it if its not fixed. Thanks!