commit	d374e92693a8352daccd772e2b724f1f9fd14f21	[log] [tgz]
author	Micah Morton <mortonm@chromium.org>	Wed Aug 01 22:53:12 2018 +0000
committer	chrome-bot <chrome-bot@chromium.org>	Thu Aug 02 17:58:23 2018 -0700
tree	a6a05f45dc48b62fe274570e6c7bbcecce79ae9a
parent	6bd67eaa6bb27f610e1902e992e5c6e07a703e78 [diff]

Revert "Reland "security_SandboxedServices: reflect shill sandboxing changes""

This reverts commit a248a9ab77c19be3afff948de8151e03b25fd619.

Reason for revert: Reverting this so the revert can be merged back into M69. We believe we have
all the networking stuff fixed as of
https://chromium-review.googlesource.com/c/aosp/platform/system/connectivity/shill/+/1153841,
but are doing this revert just to give us some breathing room by punting landing the shill
sandboxing from M69 to M70, in case there's anything thats still broken that we don't know about.

Original change's description:
> Reland "security_SandboxedServices: reflect shill sandboxing changes"
>
> This is a reland of aa6a1634eeb3751f2b10fc40a8b31d19c0ea0c8a
>
> The 2 known issues which caused problems the first time around have been
> addressed by CL:1130017 and CL:1130474. I've done some more thorough
> testing (including with elm board, which is arm processor and marvell wifi)
> and haven't discovered any new issues.
>
> CQ-DEPEND=CL:1130017,CL:1130474
>
> Original change's description:
> > security_SandboxedServices: reflect shill sandboxing changes
> >
> > This CL should land along with enabling spawning of shill in a minijail
> > as a non-root user with -n (no_new_privs). This change and the dependent
> > CL are the only 2 things that need to be reverted to go back to running
> > the shill process tree as root.
> >
> > CQ-DEPEND=CL:1087540
> > BUG=chromium:649417
> > TEST=tests passes alongside larger sandbox shill debug CL
> >
> > Change-Id: I7a1145ff8ad9f0a2d39d1c432220dc628f3d39e5
> > Reviewed-on: https://chromium-review.googlesource.com/1082958
> > Commit-Ready: Micah Morton <mortonm@chromium.org>
> > Tested-by: Micah Morton <mortonm@chromium.org>
> > Reviewed-by: Mattias Nissler <mnissler@chromium.org>
>
> Bug: chromium:649417
> Change-Id: I98ecbe6b7af10a9c5af208f964d03807e95a9253
> Reviewed-on: https://chromium-review.googlesource.com/1132194
> Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com>
> Tested-by: Micah Morton <mortonm@chromium.org>
> Reviewed-by: Jorge Lucangeli Obes <jorgelo@chromium.org>

Bug: chromium:649417, chromium:870076
CQ-DEPEND=CL:1159481
Change-Id: I4589919143cde10a288d000309b17b3b0dd7b3ee
Reviewed-on: https://chromium-review.googlesource.com/1159403
Commit-Ready: Micah Morton <mortonm@chromium.org>
Tested-by: Micah Morton <mortonm@chromium.org>
Reviewed-by: Brian Norris <briannorris@chromium.org>

client/site_tests/security_SandboxedServices/baseline[diff]

1 file changed

tree: a6a05f45dc48b62fe274570e6c7bbcecce79ae9a

README.md

Autotest: Automated integration testing for Android and Chrome OS Devices

Autotest is a framework for fully automated testing. It was originally designed to test the Linux kernel, and expanded by the Chrome OS team to validate complete system images of Chrome OS and Android.

Autotest is composed of a number of modules that will help you to do stand alone tests or setup a fully automated test grid, depending on what you are up to. A non extensive list of functionality is:

A body of code to run tests on the device under test. In this setup, test logic executes on the machine being tested, and results are written to files for later collection from a development machine or lab infrastructure.
A body of code to run tests against a remote device under test. In this setup, test logic executes on a development machine or piece of lab infrastructure, and the device under test is controlled remotely via SSH/adb/some combination of the above.
Developer tools to execute one or more tests. test_that for Chrome OS and test_droid for Android allow developers to run tests against a device connected to their development machine on their desk. These tools are written so that the same test logic that runs in the lab will run at their desk, reducing the number of configurations under which tests are run.
Lab infrastructure to automate the running of tests. This infrastructure is capable of managing and running tests against thousands of devices in various lab environments. This includes code for both synchronous and asynchronous scheduling of tests. Tests are run against this hardware daily to validate every build of Chrome OS.
Infrastructure to set up miniature replicas of a full lab. A full lab does entail a certain amount of administrative work which isn't appropriate for a work group interested in automated tests against a small set of devices. Since this scale is common during device bringup, a special setup, called Moblab, allows a natural progressing from desk -> mini lab -> full lab.