Fixing a syntax error in desktopui_AudioFeedback disabling it from bvt. Using an IP address instead of localhost due to dns resolution problem in the lab.

TEST=None
BUG=None

Change-Id: I2d1075fb77724e4bfe6318eedca27f1f820c544f
Reviewed-on: https://gerrit.chromium.org/gerrit/13964
Reviewed-by: Nirnimesh <nirnimesh@chromium.org>
Commit-Ready: Rohit Makasana <rohitbm@chromium.org>
Reviewed-by: Rohit Makasana <rohitbm@chromium.org>
Tested-by: Rohit Makasana <rohitbm@chromium.org>
[autotest] Make autotest setup script put readonly_* into shadow_config.ini

Turns out that, when contacting the TKO database, some code
in autotest uses the readonly_* fields in the config, if present.
Since we set these in global_config.ini, we need to clobber them
in shadow_config.ini when running a local setup.

BUG=None
TEST=manual

Change-Id: I35ff26452fc9d979dc9bdb6a86b7e9cb8beb5909
Reviewed-on: https://gerrit.chromium.org/gerrit/13968
Tested-by: Chris Masone <cmasone@chromium.org>
Reviewed-by: Scott Zawalski <scottz@chromium.org>
Commit-Ready: Chris Masone <cmasone@chromium.org>
new dev-libs/glib renamed their libs

dev-libs/glib-2.30.0 installs libxxx-2.0.so.0.3000.0, while new
dev-libs/glib-2.30.2 installs libxxx-2.0.so.0.3000.2.  Update
the paths accordingly.

BUG=None
TEST=None; make tree go green!

Change-Id: I3f384c8c668085265a39e72236265c66ff9686dd
Reviewed-on: https://gerrit.chromium.org/gerrit/14008
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Added chapsd to the white-list.

BUG=chromium-os:24310
TEST=Run the platform_CleanShutdown autotest.

Change-Id: Id36aa8ca8253373491d92d42c3f8a05cf745b636
Reviewed-on: https://gerrit.chromium.org/gerrit/13118
Reviewed-by: Gaurav Shah <gauravsh@chromium.org>
Tested-by: Darren Krahn <dkrahn@chromium.org>
Commit-Ready: Darren Krahn <dkrahn@chromium.org>
Add a basic sanity check for seccomp_filter in Minijail.

BUG=chromium-os:20917
TEST=run_remote_tests against x86-alex

Change-Id: I9f0806350fdde7d9898914a7675d5735fdb6df6c
Reviewed-on: https://gerrit.chromium.org/gerrit/13965
Reviewed-by: Jim Hebert <jimhebert@chromium.org>
Reviewed-by: Will Drewry <wad@chromium.org>
Tested-by: Jorge Lucangeli Obes <jorgelo@chromium.org>
Commit-Ready: Jorge Lucangeli Obes <jorgelo@chromium.org>
whitelist both new and old glib files during transition period

The PFQ/cros-workon flow means we need both whitelisted.

BUG=None
TEST=None

Change-Id: I27eabbc5a5caf1e96750c4c621de34c2c33b436f
Reviewed-on: https://gerrit.chromium.org/gerrit/14026
Reviewed-by: David James <davidjames@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
Merge branch 'master' of http://git.chromium.org/chromiumos/third_party/autotest into chromium
Mark the directory site_utils as containing packages.

Because we want to import these packages in the CL:
  https://gerrit.chromium.org/gerrit/13865

BUG=chromium-os:22339
TEST=run_remote_tests.sh --remote=$REMOTE_IP -a "xml_config=$OVERLAY_XML \
        servo_vid=0x18d1 servo_pid=0x5001 image=$TEST_IMAGE" \
        firmware_RecoveryButton

Change-Id: I5f7c89a129364cbd745fdb99dcca67ca0c5424ac
Reviewed-on: https://gerrit.chromium.org/gerrit/13973
Reviewed-by: Scott Zawalski <scottz@chromium.org>
Reviewed-by: Todd Broch <tbroch@chromium.org>
Tested-by: Tom Wai-Hong Tam <waihong@chromium.org>
Commit-Ready: Tom Wai-Hong Tam <waihong@chromium.org>
Install the image to USB and DUT disk when given an image argument in FAFT.

For FAFT test cases, if an image argument is given, it installs the
specified test image to the USB disk and reboot into it via recovery mode.
Then run 'chromeos-install' to install it to DUT disk. Such that both
USB and disk images are updated.

BUG=chromium-os:22339
TEST=run_remote_tests.sh --remote=$REMOTE_IP -a "xml_config=$OVERLAY_XML \
             servo_vid=0x18d1 servo_pid=0x5001 image=$TEST_IMAGE" \
             firmware_RecoveryButton

Change-Id: I0fbb988c14c7c8ab3e3cf0050dd63fbdcd2dc8e9
Reviewed-on: https://gerrit.chromium.org/gerrit/13865
Reviewed-by: Todd Broch <tbroch@chromium.org>
Commit-Ready: Tom Wai-Hong Tam <waihong@chromium.org>
Tested-by: Tom Wai-Hong Tam <waihong@chromium.org>
This will enable audio feedback testing on zgb, alex, stumpy, and lumpy.

BUG=None
TEST=ran downloader to check if it parsed correctly

Change-Id: I21fd11bd53366ba0faff721bc4bc47b82861a20f
Reviewed-on: https://gerrit.chromium.org/gerrit/14038
Reviewed-by: Nirnimesh <nirnimesh@chromium.org>
Reviewed-by: Scott Zawalski <scottz@chromium.org>
Commit-Ready: John D Hong <johndhong@chromium.org>
Tested-by: John D Hong <johndhong@chromium.org>
Separate generic and Gobi-specific 3G tests.

Right now, network_3g contains Gobi-specific tests.  We'd like to
start running ngihtly tests on non-Gobi modems, so I'm moving the
Gobi-specific ones into network_3g_gobi.

BUG=chromium-os:24428
TEST=None yet

Change-Id: Idb8f7fc03cabcc208ccd07a6ab26a19cd0bae4f3
Reviewed-on: https://gerrit.chromium.org/gerrit/13238
Commit-Ready: ttuttle <ttuttle@chromium.org>
Reviewed-by: ttuttle <ttuttle@chromium.org>
Tested-by: ttuttle <ttuttle@chromium.org>
Run generic and Gobi 3G test suites on Gobi modems.

Now that the generic and Gobi-specific tests are split up, run both
of them on the lab machines with Gobi modems.

BUG=chromium-os:24428
TEST=None yet

Change-Id: I919a90ffc49369a749f9d4a2177af7610ac6b79a
Reviewed-on: https://gerrit.chromium.org/gerrit/13239
Commit-Ready: ttuttle <ttuttle@chromium.org>
Reviewed-by: ttuttle <ttuttle@chromium.org>
Tested-by: ttuttle <ttuttle@chromium.org>
[autotest] Add DevServer class that uses the new HTTP API

Instead of working from the existing class that SSH's to the dev
server and runs shell commands, create a new class to work against the
new HTTP api for the dev server.  I do this because it's not clear
that we will want to continue using the interface of the existing
class, as it was built to do very different work than what we'd like
to do with the dev server now.

BUG=chromium-os:24985
TEST=dev_server_unittest.py

Change-Id: Ic776d72309bac30eb8362868370fd9f36616c3ba
Reviewed-on: https://gerrit.chromium.org/gerrit/14005
Commit-Ready: Chris Masone <cmasone@chromium.org>
Reviewed-by: Chris Masone <cmasone@chromium.org>
Tested-by: Chris Masone <cmasone@chromium.org>
Use power_short_press to boot the DUT instead of power_normal_press.

The power_normal_press delays 1.2 seconds. A fast machine boots to the
firmware screen in 1.2 seconds and it checks that the power button is pressed.
As a result, the machine is then shutdown. So we now change to use
power_short_press which is 0.1 second.

BUG=chromium-os:24754
TEST=run_remote_tests.sh --remote=$REMOTE_IP -a "xml_config=$OVERLAY_XML \
        servo_vid=0x18d1 servo_pid=0x5001" firmware_FwScreenPressPower

Change-Id: I60759d04e9453ebb04173f5933f383e03a6c9dca
Reviewed-on: https://gerrit.chromium.org/gerrit/14049
Reviewed-by: Tom Wai-Hong Tam <waihong@chromium.org>
Tested-by: Tom Wai-Hong Tam <waihong@chromium.org>
Commit-Ready: Tom Wai-Hong Tam <waihong@chromium.org>
Support firmware update after installing the specified image to DUT.

When running FAFT test cases, a new argument 'firmware_update=1' is introduced
if you also want to update the firmware using the local shellball inside the
image.

BUG=chromium-os:22339
TEST=run_remote_tests.sh --remote=$REMOTE_IP -a "xml_config=$OVERLAY_XML \
        servo_vid=0x18d1 servo_pid=0x5001 image=$TEST_IMAGE firmware_update=1" \
        firmware_RecoveryButton

Change-Id: I477b6465abd9dafad5e4d8aa977dfbd5578c6da8
Reviewed-on: https://gerrit.chromium.org/gerrit/14050
Reviewed-by: Tom Wai-Hong Tam <waihong@chromium.org>
Tested-by: Tom Wai-Hong Tam <waihong@chromium.org>
Commit-Ready: Tom Wai-Hong Tam <waihong@chromium.org>
[autotest] Remove dummy shadow_config.ini

It contains naught save commented-out lines, and for devs running
local autotest instances, it's a constant irritation to have to worry about
accidentally including it in a patch.

We also enable autotest to tolerate having a global_config.ini with no
associated shadow_config.ini

BUG=None
TEST=shadow_config.ini should not exist.

Change-Id: I500fa15dc74f545d8765f37d60b2d51a63fe3119
Reviewed-on: https://gerrit.chromium.org/gerrit/14011
Commit-Ready: Chris Masone <cmasone@chromium.org>
Tested-by: Chris Masone <cmasone@chromium.org>
Reviewed-by: Chris Masone <cmasone@chromium.org>
Updating for R17 now in beta-channel for mario,zgb, and alex

BUG=chromium-os:25073
TEST=downloader did not complain will check job queue

Change-Id: Ic13f5afdf78c6958eab157ca4a448b21dd91a6f8
Reviewed-on: https://gerrit.chromium.org/gerrit/14158
Commit-Ready: John D Hong <johndhong@chromium.org>
Reviewed-by: John D Hong <johndhong@chromium.org>
Tested-by: John D Hong <johndhong@chromium.org>
Reviewed-by: Scott Zawalski <scottz@chromium.org>
security_ptraceRestrictions: avoid startup race

When testing prctl() settings, it is possible for gdb to attach to the
sleeper process before it has executed the prctl() for the given test.
This adds a synchronization step where the test harness waits for the
sleeper to indicate it is ready.

BUG=chromium-os:25085
TEST=x86-alex build and pass security_ptraceRestrictions, even with
 manual delays added.
STATUS=Fixed

Change-Id: I100398253ca64fbeae23b6be7b1621a8e9baab58
Signed-off-by: Kees Cook <keescook@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/14163
Reviewed-by: Jim Hebert <jimhebert@chromium.org>
drop /usr/bin/{disk,label} from whitelists

These shouldn't be installed at all, and now that they aren't, drop
them from the whitelists.

BUG=chromium-os:24872
TEST=`ls /usr/bin/{disk,label}` showed nothing installed
TEST=build_packages x86-alex; `ls /build/x86-alex/usr/bin/{disk,label}` showed nothing installed

Change-Id: I86f160b1cd64146f1dc7f9db6db384063dcd696e
Reviewed-on: https://gerrit.chromium.org/gerrit/14161
Reviewed-by: David James <davidjames@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
Reviewed-by: asharif <asharif@chromium.org>
Change the firmware screen delay to 2 seconds.

When the DEV_SCREEN_SHORT_DELAY flag on GBB is enabled, the developer screen
will directly boot into the disk image after 2 seconds. So the original
delay 10 seconds is too long. Change it to 2 seconds, the time that the
developer screen is surely showed, and that the timeout is not happened.

BUG=chromium-os:19710
TEST=run_remote_tests.sh --remote=$REMOTE_IP -a "xml_config=$OVERLAY_XML \
        servo_vid=0x18d1 servo_pid=0x5001" firmware_DevMode

Change-Id: I9c0d687e6f7f9e7360e3f646aad5a3abf0608e92
Reviewed-on: https://gerrit.chromium.org/gerrit/14140
Reviewed-by: Todd Broch <tbroch@chromium.org>
Commit-Ready: Tom Wai-Hong Tam <waihong@chromium.org>
Tested-by: Tom Wai-Hong Tam <waihong@chromium.org>