The cros_workon tool has been replaced with a simpler flatcar_workon
tool based around git-r3.
Signed-off-by: James Le Cuirot <jlecuirot@microsoft.com>
TEST=Tested within chroot and using "repo start ooga b<tab>"
Change-Id: I372d13458fb89571db4cdd7561e91c68e1563941
Review URL: http://codereview.chromium.org/3191012
Takes effect when you sync/re-enter chroot.
Also, minor non-exhaustive style cleanup of existing code.
BUG=5623
TEST=tried tab completion with ./cros_workon and various options
Change-Id: I46d2eb29205a3a4ce350b82e7eced7f2069095ca
Review URL: http://codereview.chromium.org/3185003
A new command line script was introduced in this CL named autotest, which is intend to replace both build_autotest.sh and run_remote_tests.sh in the future.
This change list should be reviewed with
http://codereview.chromium.org/1513006http://codereview.chromium.org/1595001
all together.
autotest --board x86-generic --build=all will build all client tests.
autotest --board x86-generic --build=unioxbench,ltp will build enlisted client tests.
autotest --board x86-generic -c client/tests/sleeptest/control -m 12.34.56.78 ...
will invoke autoserv inside emerge-x86-generic cross-compiling env, and do a prebuild of the client test before it got pushed onto client host.
you could also:
1. bash complete the directory/file name from autotest directory after -c or -s args.
2. supply any autoserv commandline args transparently.
Note: replace build_autotest.sh/run_remotes_test.sh is only a future plan. When all the three CLs got pushed, no existing use cases should be broken.
I need to change:
1. build_packages script from third_party/chromiumos-overlay/chromeos/scripts/build_packages.
2. add "enable_server_precompile: False " to third_party/autotest/files/global_config.ini
to activate it.
Review URL: http://codereview.chromium.org/1595001
For example, ./build_packages --<tab> will try to complete all supported
./build_packages flags (or print them if completion is non-unique).
This completion could be used outside chroot.
Review URL: http://codereview.chromium.org/661096
If you source this script inside chroot, you would get <tab> completion for the --board= argument for some build scripts.
For example,
. bash_completion
./build_image --board=x<tab>
may complete to
./build_image --board=x86-generic
if x86-generic is the only available board starting with "x". If not, it will list available boards with the given prefix.
We could extend this to work with setup_board and other scripts. Also, it may be nice to extend it to work outside chroot.
Does it make sense to make this part of the regular dev chroot by default? If so, not sure what the best way to do that. Maybe install this as a hard-host-depends and source it from the chroot user .bashrc?
Review URL: http://codereview.chromium.org/652129
