History log of /external/autotest/site_utils/setup_dev_autotest.sh
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
50ab33eed41531d1d3850ec0c1a4136276500130 28-Aug-2015 MK Ryu <mkryu@google.com> [autotest] Allow remote access for shard DB

Sentinel service needs to access shards' DB remotely.
Change the semantics of -m option of setup_dev_autotest.sh.

BUG=chromium:497259
TEST=

Change-Id: I273e264b0e605c27ba17fc9c11aeb8d1ad9ac05b
Reviewed-on: https://chromium-review.googlesource.com/296070
Commit-Ready: Gwendal Grignou <gwendal@chromium.org>
Tested-by: Gwendal Grignou <gwendal@chromium.org>
Reviewed-by: Dan Shi <dshi@chromium.org>
/external/autotest/site_utils/setup_dev_autotest.sh
dca745ab6c6e6ca9fa89b39a0eec72093688e9ad 07-May-2015 Dan Shi <dshi@chromium.org> [autotest] Update setup_dev_autotest with SSP initialization

BUG=chromium:484942
TEST=local run the script, confirm lxc installed and base container is set up.

Change-Id: I523288090d640148f4e413c059101c69e9050823
Reviewed-on: https://chromium-review.googlesource.com/269977
Trybot-Ready: Dan Shi <dshi@chromium.org>
Tested-by: Dan Shi <dshi@chromium.org>
Reviewed-by: Simran Basi <sbasi@chromium.org>
Commit-Queue: Dan Shi <dshi@chromium.org>
/external/autotest/site_utils/setup_dev_autotest.sh
864de130dd082cd4121f74d69d88dddd9322fbcb 08-Apr-2015 Prathmesh Prabhu <pprabhu@chromium.org> [site_utils] Usability fixes to setup_dev_autotest.

- Fix help message
- Confirm that user wants to run as 'root'. This has the oft unintended
consequence that your autotest checkout ends up being chown'ed by
root.

BUG=None.
TEST=Tested all failure modes.

Change-Id: I79146ec7d4a1e17e9dd79f1129973a2776977979
Reviewed-on: https://chromium-review.googlesource.com/264851
Tested-by: Prathmesh Prabhu <pprabhu@chromium.org>
Reviewed-by: Richard Barnette <jrbarnette@chromium.org>
Commit-Queue: Prathmesh Prabhu <pprabhu@chromium.org>
/external/autotest/site_utils/setup_dev_autotest.sh
c96e9591f819f7a09a9d4a755652ac342feb2ba2 05-Mar-2015 MK Ryu <mkryu@google.com> [autotest] Fix setup_dev_autotest.sh for sharding on Trusty.

Apache 2.4.7, which is a default version on Trusty, does not
load the module, cgid, by default.
In the sharding system, master DB needs to enable connection
from remote shard nodes.
This script fixes such issues.

BUG=chromium:456270
DEPLOY=
TEST=Run site_utils/setup_dev_autotest.sh in VM that is clean state.

Change-Id: Ifc752f3042057605e7cc3a37b21e2ac97e6ee64a
Reviewed-on: https://chromium-review.googlesource.com/256590
Reviewed-by: Dan Shi <dshi@chromium.org>
Commit-Queue: Mungyung Ryu <mkryu@google.com>
Tested-by: Mungyung Ryu <mkryu@google.com>
/external/autotest/site_utils/setup_dev_autotest.sh
1e20b98f5cc455af261bd014db2853ea3fb25f08 07-Jan-2015 MK Ryu <mkryu@google.com> [autotest] Bug fix for setup_dev_autotest.sh

site_utils/setup_dev_autotest.sh uses mysqladmin without explicitly
specifying mysql account.
By default, mysqladmin uses the username of the current session
without password.
If the username is not registered in mysql, then it fails.
This is not an intented behavior and may cause a bug.

BUG=None
Test=Run setup_dev_autotest.sh on local machine

Change-Id: Id186cb947f66a1b823e422407d1712401af3d57c
Reviewed-on: https://chromium-review.googlesource.com/239241
Tested-by: Mungyung Ryu <mkryu@google.com>
Reviewed-by: Dan Shi <dshi@chromium.org>
Commit-Queue: Mungyung Ryu <mkryu@google.com>
/external/autotest/site_utils/setup_dev_autotest.sh
af82bca917ae08f81167bc6ce3912796574ec6ab 19-Nov-2014 Fang Deng <fdeng@chromium.org> [autotest] grant chromeos-test the right access in setup script

After mounting /usr/local/autotest, we need to grant
chromeos-test (or the current user) access to that folder.

TEST=Run the script and check file permission.
BUG=None

Change-Id: I81ef169966bb1e0da8a9dcc8989adb8b8f4942c1
Reviewed-on: https://chromium-review.googlesource.com/230630
Tested-by: Fang Deng <fdeng@chromium.org>
Reviewed-by: Prashanth B <beeps@chromium.org>
Commit-Queue: Prashanth B <beeps@chromium.org>
/external/autotest/site_utils/setup_dev_autotest.sh
a742761176ae9df932caa20f9ae6fae26ab3ea28 15-Nov-2014 Michael Janssen <jamuraa@chromium.org> [autotest] Fixes for install on trusty

- Apache default site is now named 000-default, try both
- a2enmod version fails on trusty because it's builtin
- libfreetype6-dev puts ft2build.h in a different place.

BUG=None
TEST=run on trusty vm, run on precise vm, goobuntu trusty, open
localhost to confirm AFE is up

Change-Id: I6ea818c873c4dabbafa6c6e2930d5186dfe25df6
Reviewed-on: https://chromium-review.googlesource.com/229940
Tested-by: Michael Janssen <jamuraa@chromium.org>
Reviewed-by: Dan Shi <dshi@chromium.org>
Commit-Queue: Michael Janssen <jamuraa@chromium.org>
/external/autotest/site_utils/setup_dev_autotest.sh
18808492a45be908fc4dda104c9425e6c7b3d3d5 05-Nov-2014 Dan Shi <dshi@chromium.org> [autotest] Add .conf to autotest-server apache site config file name.

Apache installed in Ubuntu 14 (trusty) does not recognize site config file
not ends with .conf.

BUG=None
TEST=tested in a trusty vm, test the script also works in Ubuntu 12.04
(chromeos-autotest.cbf)

Change-Id: I706c9c214ef3b5bd5b5912a901b6e6a37a7be8c4
Reviewed-on: https://chromium-review.googlesource.com/227611
Tested-by: Dan Shi <dshi@chromium.org>
Reviewed-by: Prashanth B <beeps@chromium.org>
Commit-Queue: Dan Shi <dshi@chromium.org>
/external/autotest/site_utils/setup_dev_autotest.sh
7f0c18389711aac386135aa4b60494966ae94fc1 28-Oct-2014 Dan Shi <dshi@chromium.org> [autotest] Setup chromeos_lab_servers database

This CL adds necessary script to create a chromeos_lab_servers database when
setting up Autotest.

This CL also changes the database_connection module so that any database
connection created by a given configure section will be force to use the
database credential defined in AUTOTEST_WEB (the AFE database).

design doc:
https://docs.google.com/a/google.com/document/d/1fqeXZElMkx5lVEh8xSdNMDn88LE6xJLkU-5vc3iVmOw/edit#

BUG=chromium:424700
TEST=locally run:
./site_utils/setup_dev_autotest.sh -p autotest -a /usr/local/autotest/
./database/migrate.py sync 0 -d AUTOTEST_SERVER_DB
./database/migrate.py sync 1 -d AUTOTEST_SERVER_DB

Confirm the database and tables are created for version 1 and deleted for version 0.

DEPLOY=migrate_server_db

Change-Id: Iea923b2bd5eca81689ac888322f7ae66e6938f10
Reviewed-on: https://chromium-review.googlesource.com/225971
Tested-by: Dan Shi <dshi@chromium.org>
Reviewed-by: Prashanth B <beeps@chromium.org>
Commit-Queue: Dan Shi <dshi@chromium.org>
/external/autotest/site_utils/setup_dev_autotest.sh
a85f6d86d7fe2ffe1b630f1d9dc0946ef5906570 01-Oct-2014 Dan Shi <dshi@chromium.org> [autotest] Enable module headers in setup script

This module is required to start Autotest afe.

BUG=None
TEST=local run the script

Change-Id: I4a43923ee04e9481e7110300cab1b71ad6e5b234
Reviewed-on: https://chromium-review.googlesource.com/220751
Tested-by: Dan Shi <dshi@chromium.org>
Reviewed-by: Simran Basi <sbasi@chromium.org>
Commit-Queue: Dan Shi <dshi@chromium.org>
/external/autotest/site_utils/setup_dev_autotest.sh
1c53ae736c604b93a46cf21d76eaab7d77a0c384 10-Sep-2014 Jakob Juelich <jakobjuelich@chromium.org> [autotest] Non-interactive mode for setup_dev_autotest

site_utils/setup_dev_autotest.sh asks for user input in the middle
of the process. This commit adds a non-interactive mode that skipps
all the questions.

BUG=None
TEST=Tested manually with database previously existing/not existing,
shadow_config.ini previously existing and different options.

Change-Id: I4df2da9058f7b7708d545fd939e217c86b6ab8a4
Reviewed-on: https://chromium-review.googlesource.com/217498
Reviewed-by: Richard Barnette <jrbarnette@chromium.org>
Tested-by: Jakob Jülich <jakobjuelich@chromium.org>
Commit-Queue: Jakob Jülich <jakobjuelich@chromium.org>
/external/autotest/site_utils/setup_dev_autotest.sh
b6a78f4bd544d0e1a837561b4a94f6ccbe9a556b 12-Jul-2014 Michael Liang <michaelliang@chromium.org> [autotest] Add verbose option to autotest setup script

Sometimes I have permission errors during when running
build_externals.py and compile_gwt_clients.py -a, but
they were suppressed and so errors were not reported
to stderr. This change adds an option -v so user running
script can see those errors.

BUG=None
TEST=ran setup_dev_autotest.sh
Change-Id: I6e0fda5325fec5ab8ff383ce00d174ea2f265730
Reviewed-on: https://chromium-review.googlesource.com/207474
Reviewed-by: Dan Shi <dshi@chromium.org>
Tested-by: Michael Liang <michaelliang@chromium.org>
Commit-Queue: Michael Liang <michaelliang@chromium.org>
Reviewed-by: Michael Liang <michaelliang@chromium.org>
/external/autotest/site_utils/setup_dev_autotest.sh
508ee928b6e4a9488fa493e6d76af4d0a6c0f251 18-Nov-2013 Simran Basi <sbasi@chromium.org> Autotest: create apache run folder in setup_dev_autotest.sh

If /etc/apache2/run does not exist create it.

BUG=None
TEST=moved the folder, got 503 errors, re-ran setup_dev_autotest.sh,
503 errors gone.

Change-Id: I7c1c419fe1c1e199d35c1e7c671922a4fdd914f4
Reviewed-on: https://chromium-review.googlesource.com/177242
Reviewed-by: Alex Miller <milleral@chromium.org>
Reviewed-by: Simran Basi <sbasi@chromium.org>
Commit-Queue: Simran Basi <sbasi@chromium.org>
Tested-by: Simran Basi <sbasi@chromium.org>
/external/autotest/site_utils/setup_dev_autotest.sh
2c603d846cb82b2e57adec73e44c10c111634237 24-May-2013 Aviv Keshet <akeshet@chromium.org> [autotest] setup_dev_autotest adds [CROS]/source_tree value to shadow_config

The [CROS]/source_tree attribute of global_config.ini is used (among
other places?) by tko/site_parse.py to find the generate_test_report
module, which resides in the chromeose checkout but outside of the
autotest repository. In prod, this points to /usr/local/google/chromeos,
but most developers do not have a chromeos checkout there.

This CL causes setup_dev_autotest to override [CROS]/source_tree in the
shadow_config that it creates, pointing it to AUTOTEST_DIR/../../../..
which is the standard location where most developers will have their
checkout. This may not be a rock solid assumption, but it is at least
better than /usr/local/google/chromeos, and at least as solid as a lot
of the other assumptions in the setup_dev_autotest script.

BUG=None
TEST=After ./setup_dev_autotest, can use tko/site_parse.py without
seeing ImportError related to generate_test_report. Also, tested new
AUTOTEST_DIR sanity check in script, by entering a non-existant
directory and seeing script abort.

Change-Id: I8f51e58f286e9c5c68bbafd3058e088beb5483f5
Reviewed-on: https://gerrit.chromium.org/gerrit/56612
Reviewed-by: Aviv Keshet <akeshet@chromium.org>
Tested-by: Aviv Keshet <akeshet@chromium.org>
Commit-Queue: Aviv Keshet <akeshet@chromium.org>
/external/autotest/site_utils/setup_dev_autotest.sh
a5745e9e7d05af07c82161a8f93cfb39accf4a31 09-May-2013 Scott Zawalski <scottz@google.com> Remove mod-python in favor of mod-wsgi.

mod-python has been deprecated for a while and our current distro of
Django doesn't support it anymore. Moving us to use wsgi completely.

Pull in bits from:
https://github.com/autotest/autotest/commit/ee3cced1afb6bc45216c7038472827ad4033c3f5

Pull in change to db/backends/afe/base.py to fixes readonly db
connection issues.

TEST=setup_dev_autotest.sh and moved our development server to
modpython.
BUG=chromium:217194

Change-Id: Ic3306700e07c7000b2451a576554810d8a6bf7f2
Reviewed-on: https://gerrit.chromium.org/gerrit/50656
Tested-by: Scott Zawalski <scottz@chromium.org>
Reviewed-by: Simran Basi <sbasi@chromium.org>
Commit-Queue: Scott Zawalski <scottz@chromium.org>
Reviewed-by: Scott Zawalski <scottz@chromium.org>
/external/autotest/site_utils/setup_dev_autotest.sh
18c70b3d929b759ea9ba4e876517c6b8fd4d6921 15-Feb-2013 Chris Sosa <sosa@chromium.org> Some small fixes found while doing an e2e test with devserver changes.

1) Alex's change to not exit 0 totally now clobbers you shadow config
even if you say no.
2) Release config should be updated for R27.
3) Site RPC interface -- better logging.
4) Site_Suite didn't actually allow an int override -- kept on casting it
to a string.

BUG=None
TEST=Ran through devserver test using cli/atest suite create and setup
autotest with shadow config.

Change-Id: Ie7f61fe95c3a642455de33416367085e159c3947
Reviewed-on: https://gerrit.chromium.org/gerrit/43429
Commit-Queue: Chris Sosa <sosa@chromium.org>
Reviewed-by: Chris Sosa <sosa@chromium.org>
Tested-by: Chris Sosa <sosa@chromium.org>
/external/autotest/site_utils/setup_dev_autotest.sh
5e7b2541e057dffd4eb3c058789ff96034b25d83 13-Feb-2013 Alex Miller <milleral@chromium.org> [autotest] Allow spaces in directory names.

`find | xargs` would choke on directories whose names contained spaces.
`find -print0 | xargx --null` is the way to fix this.

BUG=None
TEST=Ran it

Change-Id: Ib2d04a22196277e9da92ebe1a6d9c1ae2516f894
Reviewed-on: https://gerrit.chromium.org/gerrit/43216
Tested-by: Alex Miller <milleral@chromium.org>
Reviewed-by: Simran Basi <sbasi@chromium.org>
Commit-Queue: Alex Miller <milleral@chromium.org>
/external/autotest/site_utils/setup_dev_autotest.sh
3b52031a32a218c41446c75e0feada1f2a77d457 13-Feb-2013 Alex Miller <milleral@chromium.org> [autotest] Continue running if shadow_config is not clobbered.

I don't understand why we stop here. I generally want to be able to wipe
out my db and not clobber my config?

BUG=None
TEST=Ran it

Change-Id: I133aca22a654c3146825522735e7ff7dcf34d9b2
Reviewed-on: https://gerrit.chromium.org/gerrit/43214
Tested-by: Alex Miller <milleral@chromium.org>
Reviewed-by: Simran Basi <sbasi@chromium.org>
Commit-Queue: Alex Miller <milleral@chromium.org>
/external/autotest/site_utils/setup_dev_autotest.sh
79b1a7b40344cc8554cc7215e24ecaed6ba30fec 13-Feb-2013 Simran Basi <sbasi@chromium.org> Autotest: setup_dev_autotest should start mysql.

setup_dev_autotest errors out when if the mysql service was stopped
before running. In order to fix this, simply turn mysql on as part
of the script.

BUG=chromium-os:37605
TEST=ensured the script works with mysql started and stopped.

Change-Id: I6ad2a47000d1e3e529c1574692ac8b4eb3b0beb6
Reviewed-on: https://gerrit.chromium.org/gerrit/43187
Reviewed-by: Scott Zawalski <scottz@chromium.org>
Commit-Queue: Simran Basi <sbasi@chromium.org>
Reviewed-by: Simran Basi <sbasi@chromium.org>
Tested-by: Simran Basi <sbasi@chromium.org>
/external/autotest/site_utils/setup_dev_autotest.sh
e1b236d81babee197dd3368f858803789e2711bd 11-Jan-2013 beeps <beeps@chromium.org> Load mod-python in the setup_dev_autotest script.

Calling a2enmod python twice won't disrupt anything but
not calling it at all will not load mod_python, which is
needed to start apache.

TEST=Manually made the call and got it working.
BUG=None

Change-Id: I7caa5d85ffbb598d943612e6b69dfe60f410a55c
Reviewed-on: https://gerrit.chromium.org/gerrit/41147
Reviewed-by: Scott Zawalski <scottz@chromium.org>
Commit-Queue: Prashanth Balasubramanian <beeps@chromium.org>
Tested-by: Prashanth Balasubramanian <beeps@chromium.org>
/external/autotest/site_utils/setup_dev_autotest.sh
23ef442380af8f11836332fb6994a47ec1d5011b 02-Nov-2012 Richard Barnette <jrbarnette@chromium.org> Fix usage of -z tests in site_utils/setup_dev_autotest.sh.

Expressions like [ -z $VAR ] will do the wrong thing if "$VAR" has
spaces in it, and the expression isn't a terribly brilliant idea
when "$VAR" is empty, either. Ditto for tests with '=' and '!='.
For sanity, fixed the script to quote all test expressions that
might be a problem.

BUG=None
TEST=Run the script, provide a password with a space in it

Change-Id: I6200cbe05e3f1223182f79a52f72856c15c155f5
Reviewed-on: https://gerrit.chromium.org/gerrit/37280
Tested-by: Richard Barnette <jrbarnette@chromium.org>
Reviewed-by: Chris Sosa <sosa@chromium.org>
Reviewed-by: Alex Miller <milleral@chromium.org>
Commit-Ready: Richard Barnette <jrbarnette@chromium.org>
/external/autotest/site_utils/setup_dev_autotest.sh
e4181243c184f349be0120252000044fe874690e 11-Sep-2012 Chris Sosa <sosa@chromium.org> Fix local dev setup script to use only localhost as a drone.

This bug fixes a regression introduced in
https://gerrit.chromium.org/gerrit/27057. That change added atlantis2
as a drone in global_config.ini. A dev setting up autotest locally would
not be able to connect to atlantis2 causing their scheduler to terminate.

BUG=None
TEST=Ran the scheduler locally

Change-Id: Ifd620e249fce6c34949f29513c8efe810ed334e2
Reviewed-on: https://gerrit.chromium.org/gerrit/32845
Tested-by: Chris Sosa <sosa@chromium.org>
Reviewed-by: Simran Basi <sbasi@chromium.org>
Commit-Ready: Chris Sosa <sosa@chromium.org>
/external/autotest/site_utils/setup_dev_autotest.sh
3d18208314ffd83b24d58d6358a284d16a0ce465 07-Sep-2012 Simran Basi <sbasi@chromium.org> [AUTOTEST] Update setup_dev_autotest.sh for Z620's

setup_dev_autotest.sh failed on my machine when it tried to build
external packages, namely numpy and scipy. Therefore I added them
to the apt-get package list.

Also the grant command no longer worked for chromesqa-admin. I
changed the host name from % to localhost for these privileges.

After these sets of changes the script works.

BUG=chromium-os:34235
TEST=Script now properly sets up dev autotest server on my machine.

Change-Id: I0a8146f1cffa8c00055fa889e4b439ee53576d45
Reviewed-on: https://gerrit.chromium.org/gerrit/32557
Reviewed-by: Alex Miller <milleral@chromium.org>
Reviewed-by: Simran Basi <sbasi@google.com>
Tested-by: Simran Basi <sbasi@google.com>
Commit-Ready: Simran Basi <sbasi@google.com>
/external/autotest/site_utils/setup_dev_autotest.sh
da3ecf43a262250caf3f75d5fbc32e57e06051c3 25-Jul-2012 Alex Miller <milleral@chromium.org> [autotest] Optionally clobber database when running setup.

This fixes setup_dev_autotest.sh not being re-entrant, and adds an
option to either drop the database or skip re-creating the database.

BUG=chromium-os:32854
TEST=run twice

Change-Id: I2d0cebce6a84682f75bd5fa44ec16b73d34c67a7
Reviewed-on: https://gerrit.chromium.org/gerrit/28981
Tested-by: Alex Miller <milleral@chromium.org>
Reviewed-by: Chris Masone <cmasone@chromium.org>
Commit-Ready: Alex Miller <milleral@chromium.org>
/external/autotest/site_utils/setup_dev_autotest.sh
e61dd81426d6a83f975ae8ef4c5af6e12c8508e3 11-Jan-2012 Chris Masone <cmasone@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>
/external/autotest/site_utils/setup_dev_autotest.sh
2aa5533429dbecd3215de46ce4a07d6b390a3c5f 30-Dec-2011 Chris Masone <cmasone@chromium.org> [autotest] Add script for setting up local autotest server

Create script for setting up a local autotest instance that can be used
for test infrastructure development. If you're just working on new tests,
you will not need to run this.

BUG=chromium-os:24654
TEST=Run it, then hit http://localhost in your browser
STATUS=Verified

Change-Id: I7238dfcacca056e9ed4c108138a5ed20ecd82cba
Reviewed-on: https://gerrit.chromium.org/gerrit/13561
Tested-by: Chris Masone <cmasone@chromium.org>
Reviewed-by: Scott Zawalski <scottz@chromium.org>
Commit-Ready: Chris Masone <cmasone@chromium.org>
/external/autotest/site_utils/setup_dev_autotest.sh