Cross Reference: /external/autotest/site_utils/test

History log of /external/autotest/site_utils/test_that.py
Revision	Date	Author	Comments (<<< Hide modified files) (Show modified files >>>)
42a0bffec26736bbdb95edf0cd6470f1a62808fe	19-Dec-2017	Prathmesh Prabhu <pprabhu@chromium.org>	Support running test_that via a symlink BUG=b:70390932 TEST=Manually patch test_that.py in lab-tools checkout; test_that works. Change-Id: I5eceebae232d8e791ddd6380c4a419bae1ed94cb /external/autotest/site_utils/test_that.py
f0dda1b3ab3941adeaf7c4e5b567227d4f970bd9	31-Oct-2017	C Shapiro <shapiroc@chromium.org>	test_that support for model parameter Add pass through support for model going to the test_suite BUG=b:65673486 TEST=test_that -b coral -i coral-release/R63-10000.0.0 :lab: dummy_Pass & test_that -b coral -m robo360 -i coral-release/R63-10000.0.0 :lab: dummy_Pass Change-Id: I00721d8d300a3647ec590d80f132d51695dfe55d Reviewed-on: https://chromium-review.googlesource.com/747622 Commit-Ready: C Shapiro <shapiroc@google.com> Tested-by: C Shapiro <shapiroc@google.com> Reviewed-by: Prathmesh Prabhu <pprabhu@chromium.org> /external/autotest/site_utils/test_that.py
02b46c55690dcbccaf2687ce3f0a6f6440b959db	11-Sep-2017	Allen Li <ayatane@chromium.org>	[autotest] Add old RPC support to test_that BUG=chromium:763207 TEST=trybot TEST=test_that :lab: -b reks -i reks-release/R63-9927.0.0 -p suites dummy_Pass -w cautotest TEST=Run test_that against old moblab (verify bug fix) Change-Id: I18ee13e8b561b0595358aba4f5cb3e8cb148c140 Reviewed-on: https://chromium-review.googlesource.com/661218 Commit-Ready: Allen Li <ayatane@chromium.org> Tested-by: Allen Li <ayatane@chromium.org> Reviewed-by: Prathmesh Prabhu <pprabhu@chromium.org> Reviewed-by: Laurence Goodby <lgoodby@chromium.org> /external/autotest/site_utils/test_that.py
3c0d6cba982b138e228c8f912028cbbc2db7b20e	22-Aug-2017	Allen Li <ayatane@chromium.org>	[autotest] Clean up new suite_args API This is a scrub of the repo, making sure the API is correct at all interfaces and backward compatibility is maintained at the control file interface. In detail, the changes are: AFE create_suite_job RPC made less defensive. An invalid argument will cause the RPC call to error instead of replacing suite_args with an empty dict, which probably would not have produced the desired behavior anyway, so erroring out is better. Inject suite_args into the control file. This allows new Autotest to run old tests. Make the relevant new tests support being run by old Autotest. The referenced bug contains a diagram listing all of the interface points between the new and old API and the compatibility between them. BUG=chromium:758427 TEST=site_utils/test_that.py -b reks -i reks-release/R60-9592.71.0 -w localhost :lab: dummy_Pass TEST=site_utils/run_suite.py -b reks -i reks-release/R60-9592.71.0 -p suites -s dummy Change-Id: I352491b4ad72818ce288144a0380e441a3f65b40 Reviewed-on: https://chromium-review.googlesource.com/631236 Commit-Ready: Allen Li <ayatane@chromium.org> Tested-by: Allen Li <ayatane@chromium.org> Reviewed-by: Allen Li <ayatane@chromium.org> /external/autotest/site_utils/test_that.py
429fd801a01a1f0b9fc8be09cf293b95d314088b	08-Aug-2017	Allen Li <ayatane@chromium.org>	[autotest] Make test_that pass suite_args as a dict BUG=chromium:753072 TEST=Trybot TEST=Run test_that Change-Id: I296a20bd7bc56567254fae7663ddc74178f5caf9 Reviewed-on: https://chromium-review.googlesource.com/604737 Commit-Ready: Allen Li <ayatane@chromium.org> Tested-by: Allen Li <ayatane@chromium.org> Reviewed-by: Prathmesh Prabhu <pprabhu@chromium.org> /external/autotest/site_utils/test_that.py
68ee1c54e49751ba4d8278586e121ceee97ef134	05-Jul-2017	Prathmesh Prabhu <pprabhu@chromium.org>	test_that: Fix argument validation. A test_droid CL broke argument validation so that test_that started accepting :lab: runs without a --build argument. This would lead to cryptic error later from the run_suite RPC. FixIt, and add unittests to protect this argument validation. BUG=None TEST=(new) unittest fails before the change, pass afterwards. Change-Id: Iffcd8005c62665ea9c0a2f1c45d43b8564c67abf Reviewed-on: https://chromium-review.googlesource.com/559950 Commit-Ready: Prathmesh Prabhu <pprabhu@chromium.org> Tested-by: Prathmesh Prabhu <pprabhu@chromium.org> Reviewed-by: Xixuan Wu <xixuan@chromium.org> /external/autotest/site_utils/test_that.py
910c6042cd2c93e7cfa8e253f96092792600b5be	25-Oct-2016	Allen Li <ayatane@chromium.org>	[autotest] Fix argparse handling of arguments starting with dashes BUG=chromium:658013 TEST=Run test_that against lab Change-Id: I98c8682ac6d46e7a3bc0c2aa85e5024915989aef Reviewed-on: https://chromium-review.googlesource.com/402710 Commit-Ready: Allen Li <ayatane@chromium.org> Tested-by: Allen Li <ayatane@chromium.org> Reviewed-by: Richard Barnette <jrbarnette@google.com> /external/autotest/site_utils/test_that.py
47b68eeb258a34a9c3f7138dfe4f737f81431b1d	06-Jun-2016	Kevin Cheng <kevcheng@chromium.org>	[autotest] test_that error message correction. Error message pointed out typo in flag to use: '--autotest-dir' instead of '--autoest_dir' BUG=None TEST=Check that it prints correct message now Change-Id: I55915c5075654ff4514a29e6c2304c7c2caab6ed Reviewed-on: https://chromium-review.googlesource.com/350030 Commit-Ready: Kevin Cheng <kevcheng@chromium.org> Tested-by: Kevin Cheng <kevcheng@chromium.org> Reviewed-by: Dan Shi <dshi@google.com> /external/autotest/site_utils/test_that.py
57740ca3b8ceb4bf4ff682e7fe8f208d4f7357d9	19-Feb-2016	Simran Basi <sbasi@google.com>	[autotest] fix test_{droid,that} --pretend. BUG=b:27043786,chromium:586833 TEST=test_that and test_droid runs. Change-Id: I0de93498e3d05db8bd30753d166bf7b7e7e3f486 Reviewed-on: https://chromium-review.googlesource.com/328713 Commit-Ready: Simran Basi <sbasi@chromium.org> Tested-by: Simran Basi <sbasi@chromium.org> Reviewed-by: Dan Shi <dshi@chromium.org> Reviewed-by: Kevin Cheng <kevcheng@chromium.org> /external/autotest/site_utils/test_that.py
60dfcefd5a8d726118d95297d1250909e834435b	13-Feb-2016	Laurence Goodby <lgoodby@google.com>	[autotest] add max_runtime_mins option to test_that. BUG=b:27174274 TEST=ran tests in Talyn lab. Change-Id: I8eef3e53f339f1346e249f104933fb63740caa32 Reviewed-on: https://chromium-review.googlesource.com/326928 Commit-Ready: Laurence Goodby <lgoodby@chromium.org> Tested-by: Laurence Goodby <lgoodby@chromium.org> Reviewed-by: Simran Basi <sbasi@chromium.org> /external/autotest/site_utils/test_that.py
f067d9c7e8dc08426a16edc89d2d33f17646a50f	22-Dec-2015	Simran Basi <sbasi@google.com>	test_droid: Basic remote support. Allows test_droid to run tests against Android devices connected to a remote host. This is useful if the test station is in the lab and unaccesible. BUG=b:26186193 TEST=test_droid.py ZX1G22JHXN android_DummyTest --debug \ --remote android1758-wifi-test-station-2.cros Change-Id: I7f98440540fcf2e81e8715b81591c1d64ac60f7a Reviewed-on: https://chromium-review.googlesource.com/319811 Commit-Ready: Simran Basi <sbasi@chromium.org> Tested-by: Simran Basi <sbasi@chromium.org> Reviewed-by: Dan Shi <dshi@chromium.org> /external/autotest/site_utils/test_that.py
14622bb8249c2200e5258ea6d40b3362229e90a7	25-Nov-2015	Simran Basi <sbasi@google.com>	[autotest] test_droid V1. This CL introduces test_droid, a script to launch autotest tests against local Android DUTs connected to the host computer via USB. Much of the logic is similar to test_that, so this has all been pulled into a new script test_utils.py Pending work: * Moving of generate_test_report to somewhere it is accesible outside of the chroot. * Add in support for remote adb hosts (i.e. the DUT is connected to a remote computer). * Sequences support. BUG=b:25748759 TEST=./test_droid.py 7d52318 brillo_WhitelistedGtests CQ-DEPEND=CL:315230 Change-Id: Idab3805f7921173fbc706354b322f37244240fa2 Reviewed-on: https://chromium-review.googlesource.com/314870 Commit-Ready: Simran Basi <sbasi@chromium.org> Tested-by: Simran Basi <sbasi@chromium.org> Reviewed-by: Aviv Keshet <akeshet@chromium.org> /external/autotest/site_utils/test_that.py
54ec4f3c0ae231c6177174603b448919dd1fa420	10-Dec-2015	Fang Deng <fdeng@chromium.org>	[autotest] test_that checks autoserv return code. If autoserv dies for unexpected reasons, test_that will exit with code 1. TEST=test_that dummy_Pass HOST_IP test_that dummy_Fail HOST_IP force abstract_ssh to raise an exception so that autoserv will fail at crashinfo collection step. Check exit code is 1. BUG=chromium:555073 Change-Id: I85eae412cb07d13f2f1eda49460faacf11bf393f Reviewed-on: https://chromium-review.googlesource.com/317593 Commit-Ready: Fang Deng <fdeng@chromium.org> Tested-by: Fang Deng <fdeng@chromium.org> Reviewed-by: Fang Deng <fdeng@chromium.org> /external/autotest/site_utils/test_that.py
7c55662fad7b6fa0d837e2a5dfff115af8b232be	07-Dec-2015	J. Richard Barnette <jrbarnette@chromium.org>	[autotest] Validate --board and --build with test_that :lab:. A board and build are both required with `test_that :lab:`. This adds a check to enforce that with a useful error message. BUG=chromium:418379 TEST=run test_that using all combinations of --board and --build Change-Id: I9f39fd751482db836c186d5a2024521d73c8e9a7 Reviewed-on: https://chromium-review.googlesource.com/316513 Commit-Ready: Richard Barnette <jrbarnette@chromium.org> Tested-by: Richard Barnette <jrbarnette@chromium.org> Reviewed-by: Fang Deng <fdeng@chromium.org> Reviewed-by: Aviv Keshet <akeshet@chromium.org> /external/autotest/site_utils/test_that.py
61078ebc0efc39d5ff57dd1513460ea0947f21b8	18-Nov-2015	Aviv Keshet <akeshet@chromium.org>	test_that: remove obsolete help text There is no :vm: mode to test that (and I believe there never was implemented). Runs against a local vm are just specified by using the local host and port for REMOTE. BUG=None TEST=None Change-Id: Ibf0e2f5c102deb76d22f6b8dbf8e434199d32aea Reviewed-on: https://chromium-review.googlesource.com/312988 Commit-Ready: Aviv Keshet <akeshet@chromium.org> Tested-by: Aviv Keshet <akeshet@chromium.org> Reviewed-by: Dan Shi <dshi@chromium.org> /external/autotest/site_utils/test_that.py
cbb5ba051619fc10b0607abc369c11592202a0a9	11-Aug-2015	Laurence Goodby <lgoodby@google.com>	Fix for test_that_wrapper call to test_that.parse_arguments. test_that_wrapper expects one return argument from parse_arguments. BUG=chromium:446321 TEST=Ran unittest, tested with moblab. Change-Id: I82bde8832e3f7213405b3f98efd703be0d153587 Reviewed-on: https://chromium-review.googlesource.com/292810 Reviewed-by: Simran Basi <sbasi@chromium.org> Tested-by: Laurence Goodby <lgoodby@chromium.org> Commit-Queue: Laurence Goodby <lgoodby@chromium.org> /external/autotest/site_utils/test_that.py
079312e32942bdf5d72721d0bcfd81bb87f927b0	05-Aug-2015	Laurence Goodby <lgoodby@google.com>	test_that: adds a --web option. Similar to run_suite's --web option, this option is used for remote :lab: runs to direct the test to a specific server (for example, a moblab). The --web option is not passed to remote test_that invocations. BUG=chromium:446321 TEST='--web' is used for run_suite but is not passed to remote test_that. Change-Id: I80081d751709b2f3d82fa8248139b43778962342 Reviewed-on: https://chromium-review.googlesource.com/290811 Trybot-Ready: Laurence Goodby <lgoodby@chromium.org> Reviewed-by: Simran Basi <sbasi@chromium.org> Commit-Queue: Laurence Goodby <lgoodby@chromium.org> Tested-by: Laurence Goodby <lgoodby@chromium.org> /external/autotest/site_utils/test_that.py
48e51174a21255fef9904d642f5c01d1457a9b0d	24-Jun-2015	Daniel Wang <wonderfly@google.com>	Take private key from a cmdline flag BUG=brillo:1200 TEST=unit tests Change-Id: Ic0f153c1905bacaac199d5ba6bfbd9c04a8cce6e Reviewed-on: https://chromium-review.googlesource.com/286914 Commit-Queue: Daniel Wang <wonderfly@google.com> Trybot-Ready: Daniel Wang <wonderfly@google.com> Tested-by: Daniel Wang <wonderfly@google.com> Reviewed-by: Prathmesh Prabhu <pprabhu@chromium.org> /external/autotest/site_utils/test_that.py
36cfd831af781eed114337efa5b90c103a49b502	10-Oct-2014	Dan Shi <dshi@chromium.org>	[autotest] Support updating both firmware and CrOS from run_suite Add firmware_build option for run_suite to pass in firmware build. Save the build containing server-side test to job_keyvals. Design doc: https://docs.google.com/a/google.com/document/d/115aAHyZaatFDzuKWm61Sj2fImH4NDWikXqifvWKbbW0/edit# BUG=chromium:270258 TEST=local run_suite: make sure it works with older build: ./run_suite.py -b veyron_jerry -i trybot-veyron_jerry-paladin/R45-7086.0.0-b8 -p suites -s dummy_server Call failed as --firmware_ro_build not supported yet. ./run_suite.py -b veyron_jerry -i trybot-veyron_jerry-paladin/R45-7122.0.0-b11 --firmware_build veyron_jerry-firmware/R41-6588.9.0 --test_source_build trybot-veyron_jerry-paladin/R45-7122.0.0-b11 --firmware_ro_build veyron_jerry-firmware/R41-6588.9.0 -p suites -s dummy_server Call failed as the firmware build does not have test_suites package built: ./run_suite.py -b veyron_jerry -i trybot-veyron_jerry-paladin/R45-7122.0.0-b11 --firmware_build veyron_jerry-firmware/R41-6588.9.0 --test_source_build veyron_jerry-firmware/R41-6588.9.0 -p suites -s dummy_server make sure it works with new build: ./run_suite.py -b veyron_jerry -i trybot-veyron_jerry-paladin/R45-7122.0.0-b11 --firmware_build veyron_jerry-firmware/R41-6588.9.0 --test_source_build trybot-veyron_jerry-paladin/R45-7122.0.0-b11 -p suites -s dummy_server DEPLOY=apache,scheduler Change-Id: I50d23a7e81e4d6224b3483111110f910eb407074 Reviewed-on: https://chromium-review.googlesource.com/272793 Reviewed-by: Dan Shi <dshi@chromium.org> Commit-Queue: Dan Shi <dshi@chromium.org> Trybot-Ready: Dan Shi <dshi@chromium.org> Tested-by: Dan Shi <dshi@chromium.org> /external/autotest/site_utils/test_that.py
a6b2ce9a320ac947873805c413a757e2d377e46f	28-May-2015	Dan Shi <dshi@chromium.org>	[autotest] Fix provision job in test_that --provision arg in autoserv was changed, which breaks test_that's run_provisioning_job. This CL updates the method with correct autoserv command line args: ['--provision', '--job-labels', build] BUG=chromium:492817 TEST=test_that --build veyron_jerry-release/R44-7058.0.0 172.27.215.232 dummy_Pass Change-Id: I6f67a854e897234396d2087a2b6417fbd6cbcbed Reviewed-on: https://chromium-review.googlesource.com/273863 Tested-by: Dan Shi <dshi@chromium.org> Reviewed-by: Aviv Keshet <akeshet@chromium.org> Commit-Queue: Dan Shi <dshi@chromium.org> /external/autotest/site_utils/test_that.py
8bd6d482f849d9e015f0a74c588e5135e3119dcb	22-Apr-2015	Simran Basi <sbasi@google.com>	[test_that] Remove --force arg when calling autotest_quickmerge autotest_quickmerge's --force arg will soon be deleted so remove the call from test_that. BUG=brillo:908 TEST=test_that still works. CQ-DEPEND=CL:266755 Change-Id: I7851dcbc14b3a6e1b1b9bfd766b7efdb02bf3851 Reviewed-on: https://chromium-review.googlesource.com/266763 Reviewed-by: Dan Shi <dshi@chromium.org> Tested-by: Simran Basi <sbasi@chromium.org> Commit-Queue: Simran Basi <sbasi@chromium.org> /external/autotest/site_utils/test_that.py
2252db34500a41ecbc8db0972ad91adce3030ab6	08-Apr-2015	Aviv Keshet <akeshet@chromium.org>	[autotest] remove unneeded legacy support from test_that This CL removes code that allows test_that to work with builds that pre-date the relocation of the build-time autotest tree in the sysroot. Given that that change is over a year old, it's unlikely that anyone still needs this support. BUG=chromium:256906 TEST=Unit tests Change-Id: I6f4854c3dc4bff7a242a0b34bfc661376e209023 Reviewed-on: https://chromium-review.googlesource.com/264750 Tested-by: Aviv Keshet <akeshet@chromium.org> Reviewed-by: Simran Basi <sbasi@chromium.org> Commit-Queue: Aviv Keshet <akeshet@chromium.org> /external/autotest/site_utils/test_that.py
1767613dbf75dc28299b9420cbffe0b2589a7783	08-Apr-2015	Mussa <mussa@chromium.org>	Always perform quickmerge step when running test_that. This scenario has come up multiple times. You are modifying your test on your local machine but when you run test_that the code you added isn't getting run. Test_that is running some other previous version of your code. You could chase down packages on the DUT or on your local box and look for sentinel files or checksum files and delete them to trick test_that to pickup your changes. Or, you can use a flag (--force) that autotest_quickmerge.py' already supports. Pass --force flag to autotest_quickmerge.py by default. BUG=None. TEST=I ran a local test. Will run test_that unit tests when I find out how to. Change-Id: I0f8f6f3c6763defe45cb31ef64e815fbd75bc0ae Reviewed-on: https://chromium-review.googlesource.com/264497 Tested-by: Mussa Kiroga <mussa@chromium.org> Reviewed-by: Katherine Threlkeld <kathrelkeld@chromium.org> Commit-Queue: Mussa Kiroga <mussa@chromium.org> /external/autotest/site_utils/test_that.py
b669cbdea7f4bfc9cbfcea48d9cf9ce62f0deff5	13-Sep-2013	Dan Shi <dshi@chromium.org>	[autotest] Disable install autotest from job_repo_url for test_that use_packing option for autotest._install method is True by default. When using test_that to run test, DUT will try to install autotest package from job_repo_url with server configured in global_config (cautotest). For DUT not located in lab, there is no job_repo_url existed for such DUT in cautotest, and therefore autotest will try to copy over the local files. However, when a user try to use a DUT in the lab to run test_that, autotest package is downloaded and installed from job_repo_url. That leads to a problem that developers can't use test_that to verify autotest code. The fix is to add a new option no_use_packaging to autoserv, and thread the option to autotest._install. The option is set to False by default, and set to True in test_that. Also, when this argument is set to True, any package installation will use AutoservFetcher. BUG=chromium:265673 TEST=run following command and confirm local autotest code is copied over to the DUT: test_that -b lumpy 172.22.75.225 dummy_Pass Change-Id: I365f5f7dc79c8e65cddaa0af77f1f1a1e4b0012a Reviewed-on: https://chromium-review.googlesource.com/169343 Reviewed-by: Mungyung Ryu <mkryu@google.com> Commit-Queue: Mungyung Ryu <mkryu@google.com> Tested-by: Mungyung Ryu <mkryu@google.com> /external/autotest/site_utils/test_that.py
789f87c87dcacee0584033b21cbf920210b8d336	24-Mar-2015	J. Richard Barnette <jrbarnette@chromium.org>	Remove references to the try-bot and pfq pools. The try-bot pool is poorly loved, and generally a nuisance. Remove references to the pool. Shift test_that to use the suites pool by default. This also deletes a stray, dead reference to the pfq pool, as that pool has been unused for some time. BUG=chromium:469926 TEST=None Change-Id: Iaa449c5d5efab5ee98c63e44d38f1a51dfed5d9a Reviewed-on: https://chromium-review.googlesource.com/262061 Tested-by: Richard Barnette <jrbarnette@chromium.org> Reviewed-by: Aviv Keshet <akeshet@chromium.org> Commit-Queue: Richard Barnette <jrbarnette@chromium.org> /external/autotest/site_utils/test_that.py
b723b1b17967f7f12f782b1d2d1b48854194d218	04-Feb-2015	Simran Basi <sbasi@google.com>	test_that: Be able to specify pool. BUG=chromium:446321 TEST='--pool' is passed to test_that_wrapper Change-Id: I591ca76419aa6cf796dfa986816f542ba5000963 Reviewed-on: https://chromium-review.googlesource.com/246185 Reviewed-by: Aviv Keshet <akeshet@chromium.org> Tested-by: Simran Basi <sbasi@chromium.org> Commit-Queue: Simran Basi <sbasi@chromium.org> /external/autotest/site_utils/test_that.py
f5f2ba2abff1d5831ac8ead266a7a99c69681984	03-Feb-2015	Christopher Wiley <wiley@chromium.org>	test_that: Enhance help text Make it clear that you don't get local changes when you run in the lab. BUG=None TEST=None Change-Id: Ic4aa0660fc5d913d668985307b6b8e7e058f09cc Reviewed-on: https://chromium-review.googlesource.com/245590 Tested-by: Christopher Wiley <wiley@chromium.org> Reviewed-by: Aviv Keshet <akeshet@chromium.org> Commit-Queue: Christopher Wiley <wiley@chromium.org> /external/autotest/site_utils/test_that.py
5783f8a94ce208df0cf46547e8b50b7f74a9638e	22-Dec-2014	Dan Shi <dshi@chromium.org>	[autotest] Provide suggestions when test_that failed to locate any test. Make it easier for user to locate the exact test to run. When test_that failed to locate any test matching the test argument, provide a list of suggestions. For example: test_that -b peppy --fast 172.27.213.193 e:dummy_Pass_123 leads to following exception message: ValueError: Found no tests. Check your suite name, test name, or test matching wildcard. Did you mean any of following tests? dummy_Pass dummy_PassServer dummy_Pass.wifichaos dummy_Pass.actionable dummy_Pass.experimental dummy_Fail dummy_Pass.bluetooth dummy_RepeatArgs dummy_FailServer dummy_FailServer_Flaky BUG=chromium:441455 TEST=local test runs with test_that: test_that -b peppy --fast 172.27.213.193 e:dummy_Pass_123 test_that -b peppy --fast 172.27.213.193 f:dummy test_that -b peppy --fast 172.27.213.193 suite:bvt_123 Change-Id: I22a8b566580e492c68b8729afc22d6950a2166a3 Reviewed-on: https://chromium-review.googlesource.com/237300 Trybot-Ready: Dan Shi <dshi@chromium.org> Tested-by: Dan Shi <dshi@chromium.org> Reviewed-by: Fang Deng <fdeng@chromium.org> Commit-Queue: Dan Shi <dshi@chromium.org> /external/autotest/site_utils/test_that.py
8a89e9b22f6edcd987020a9aefa74eb21571606f	08-Oct-2014	Fang Deng <fdeng@chromium.org>	[autotest] Use realpath for sysroot in test_that Use realpath for sysroot when checking whether it is already inside sysroot. TEST=run test_tat BUG=chromium:416905 Change-Id: Id08ab0cba78ee1493e1b79e1433974327e2b7a0b Reviewed-on: https://chromium-review.googlesource.com/222102 Tested-by: Fang Deng <fdeng@chromium.org> Reviewed-by: Dan Shi <dshi@chromium.org> Commit-Queue: Fang Deng <fdeng@chromium.org> /external/autotest/site_utils/test_that.py
f6e4024f58da69d578dede9b1d3f4456fc2a28df	03-Oct-2014	Aviv Keshet <akeshet@chromium.org>	autotest: improve test_that.py error message when no tests found BUG=chromium:419931 TEST=None Change-Id: Ic3b71c7a23183fc89436a757064dfb7852a9c34f Reviewed-on: https://chromium-review.googlesource.com/221315 Tested-by: Aviv Keshet <akeshet@chromium.org> Reviewed-by: Fang Deng <fdeng@chromium.org> Reviewed-by: Olof Johansson <olofj@chromium.org> Commit-Queue: Aviv Keshet <akeshet@chromium.org> /external/autotest/site_utils/test_that.py
8e555337e8ee40ac235f4d860f69497a9967e0e5	27-Jun-2014	Josh Triplett <josh@joshtriplett.org>	test_that: Point to latest results directory When done, print the path to the "latest" symlink, not just to the directory itself. Move the message to after the creation of that symlink. BUG=None TEST=test_that $machine dummy_Pass Change-Id: I086641962ea7e91aedea93f1dbe31753bdc2991f Reviewed-on: https://chromium-review.googlesource.com/205964 Tested-by: Josh Triplett <josh@joshtriplett.org> Reviewed-by: Ilja Friedel <ihf@chromium.org> Reviewed-by: Aviv Keshet <akeshet@chromium.org> Commit-Queue: Josh Triplett <josh@joshtriplett.org> /external/autotest/site_utils/test_that.py
6303341b1b7c1447344712903be1f3f2517ceb82	27-Jun-2014	Josh Triplett <josh@joshtriplett.org>	test_that: Use a relative symlink for test_that_latest for chroot-friendliness Linking to the absolute path of the latest test results only works from within the chroot; making the symlink relative makes it easy to access from outside the chroot as chroot/tmp/test_that_latest/ . BUG=None TEST=test_that $machine dummy_Pass Change-Id: I26c4c276028d5b7424126d3f4aa800e071fe0f35 Reviewed-on: https://chromium-review.googlesource.com/205963 Tested-by: Josh Triplett <josh@joshtriplett.org> Reviewed-by: Ilja Friedel <ihf@chromium.org> Reviewed-by: Aviv Keshet <akeshet@chromium.org> Commit-Queue: Josh Triplett <josh@joshtriplett.org> /external/autotest/site_utils/test_that.py
89dc43dd18fe29c73c901f670dc8eeceda144a69	29-May-2014	Jorge Lucangeli Obes <jorgelo@chromium.org>	Fix typo in 'test_that' error message. BUG=None TEST=None Change-Id: I3b40e2a5b7382d6ec503d0fb3ad8a57ef1fb01ec Reviewed-on: https://chromium-review.googlesource.com/202160 Commit-Queue: Jorge Lucangeli Obes <jorgelo@chromium.org> Tested-by: Jorge Lucangeli Obes <jorgelo@chromium.org> Reviewed-by: Aviv Keshet <akeshet@chromium.org> /external/autotest/site_utils/test_that.py
04be2bd5e4666a5c253e9c30ab20555e04286032	08-May-2014	Ilja H. Friedel <ihf@chromium.org>	Autotest: Change logging.warn() to logging.warning(). logging.warn() is deprecated. See http://bugs.python.org/issue13235 Substitution was performed via ~/cros/src/third_party/autotest/files$ find ./ -type f \| xargs sed -i 's/logging.warn(/logging.warning(/' BUG=None. TEST=There should be one-- and preferably only one --obvious way to do it. Change-Id: Ie5665743121a49f7fbd5d1f47896a7c65e87e489 Reviewed-on: https://chromium-review.googlesource.com/198793 Commit-Queue: Ilja Friedel <ihf@chromium.org> Tested-by: Ilja Friedel <ihf@chromium.org> Reviewed-by: Alex Miller <milleral@chromium.org> /external/autotest/site_utils/test_that.py
f81917c3692293e7b72a4fa467813cd1a43f3126	18-Apr-2014	Jorge Lucangeli Obes <jorgelo@chromium.org>	test_that: fix typo in usage string. BUG=None TEST=test_that --help shows no typo. Change-Id: I78c1b3619095842c38a4abeb39c4acb95850dbed Reviewed-on: https://chromium-review.googlesource.com/195500 Commit-Queue: Jorge Lucangeli Obes <jorgelo@chromium.org> Tested-by: Jorge Lucangeli Obes <jorgelo@chromium.org> Reviewed-by: Aviv Keshet <akeshet@chromium.org> /external/autotest/site_utils/test_that.py
20b20c73d91bf3411da5b5fa69b8cee592e8088f	02-Apr-2014	Aviv Keshet <akeshet@chromium.org>	[autotest] make test_that reuse a created suite when scheduling iterations This CL pulls turns test_that's schedule_local_suite into fetch_local_suite and moves the scheduling call into perform_local_run. When scheduling multiple iterations of a test or suite, this allows the created suite object to be re-used, which saves a lot of duplicate searches through all the control files in the tree when scheduling duplicate iterations. NOTE: This does not really fix the linked-to bug (test_that fails when more than 999 tests are schedule). However, it does make it less painful, and I don't feel like filing a new bug, so I'm linking to that one. TEST=Unit tests pass `git grep schedule_local_suite` -> no results `test_that --board=lumpy --iterations=1000 localhost dummy_Pass` -> 1000 jobs are scheduled in under a minute, rather than the snails pace before. BUG=chromium:356879 Change-Id: I50e3c70a95c829a2d97333bee4472f25c298da66 Reviewed-on: https://chromium-review.googlesource.com/193095 Tested-by: Aviv Keshet <akeshet@chromium.org> Reviewed-by: Fang Deng <fdeng@chromium.org> Reviewed-by: Christopher Wiley <wiley@chromium.org> Commit-Queue: Aviv Keshet <akeshet@chromium.org> /external/autotest/site_utils/test_that.py
5c50833d70f220440303fc1c1eea36fb7798dfc6	19-Mar-2014	Fang Deng <fdeng@chromium.org>	[autotest] dynamic suite emits sub-job's dir as subdir to status.log It is enforced by client/common_lib/base_job.py that, within a single job, mutiple tests with the same name can not run in the same sub-directory. That is to say, (test_name, subdir) should be unique within the scope of a job. Tko parser hold this assumption and it get confused if this is not the case. This cl makes dynamic suite emit a subdir to status.log for each test status. The subdir is composed of job_tag and subdir retrieved from tko_test_view_2. This makes sure of two things: a) if a job has been retried, we will not end up with having two statuses that look exactly the same. For example, in the case a retry has been run, without changes in this cl the status log looks like START ---- dummy_Fail.Fail timestamp=.. ... START ---- dummy_Fail.Fail timestamp=.. ... With changes in this cl, it will look like START 116-fdeng/172.2.3.4/dummy_Fail.Fail dummy_Fail.Fail timestamp=.. ... START 117-fdeng/172.5.6.7/dummy_Fail.Fail dummy_Fail.Fail timestamp=.. ... b) This also makes sure that if someone runs a test twice with different subdir_tag, (test_name, subdir) is still unique within the scope of the suite job. For example, one could do in control file job.run_test('dummy_Fail', tag='Fail', subdir_tag='subdir_1') job.run_test('dummy_Fail', tag='Fail', subdir_tag='subdir_2') With changes in this cl, the status log looks like START 116-fdeng/172.2.3.4/dummy_Fail.Fail.subdir_1 dummy_Fail.Fail timestamp=.. ... START 116-fdeng/172.2.3.4/dummy_Fail.Fail.subdir_2 dummy_Fail.Fail timestamp=.. ... TEST=unittest; dummy suite runs ok with both run_suite and test_that; Works fine with test retry changes: - Cherry-pick test retry changes crosreview.com/188365 and crosreview.com/190585. - Added JOB_RETRIES = 2 to dummy_Fail/control. Created a trybot image. - Ran dummy suite and observed that dummy_Fail was retried twice without errors. BUG=chromium:354654 DEPLOY=apache Change-Id: Ib939a8d95b3a4db06d408257b1be8608cce5fed2 Reviewed-on: https://chromium-review.googlesource.com/191002 Reviewed-by: Fang Deng <fdeng@chromium.org> Tested-by: Fang Deng <fdeng@chromium.org> Commit-Queue: Fang Deng <fdeng@chromium.org> /external/autotest/site_utils/test_that.py
2ce92d5a16b7842d2312258289747ebb3f7937ac	14-Mar-2014	Christopher Wiley <wiley@chromium.org>	Add a --iterations flag to test_that This is useful when we want to run a test N times to gauge how flaky a test is. TEST=Run test_that with --iterations=2. BUG=chromium:352719 Change-Id: Id787d9599f5ef222bafbea0ff6945ea9d0cef8f9 Reviewed-on: https://chromium-review.googlesource.com/190062 Reviewed-by: Christopher Wiley <wiley@chromium.org> Commit-Queue: Christopher Wiley <wiley@chromium.org> Tested-by: Christopher Wiley <wiley@chromium.org> /external/autotest/site_utils/test_that.py
ad7309b61b322548ed3a5edd18fec8e42f47ff5b	12-Feb-2014	Jorge Lucangeli Obes <jorgelo@chromium.org>	test_that: fix spacing in help message. BUG=None TEST=test_that -h Change-Id: Iaa629765ccf5ca66b8dbc1b0363b6018d4f3eea8 Reviewed-on: https://chromium-review.googlesource.com/186112 Commit-Queue: Jorge Lucangeli Obes <jorgelo@chromium.org> Tested-by: Jorge Lucangeli Obes <jorgelo@chromium.org> Reviewed-by: Aviv Keshet <akeshet@chromium.org> /external/autotest/site_utils/test_that.py
f860bd1617b5c200a0378cc379d83585c5ecff63	24-Jan-2014	beeps <beeps@chromium.org>	[Autotest] Download sonic extension in the server test. Though the canonical way to handle extensions is to install them as a dep, our builders seem to have trouble contacting the omaha server to get the extension. Since our drones don't have the same problem, download the extension in the server test instead. TEST=Ran the test. BUG=chromium:321179, chromium:321177: Change-Id: I4bcea636eb3a469e415af28630005a86196b7800 Reviewed-on: https://chromium-review.googlesource.com/183743 Tested-by: Prashanth B <beeps@chromium.org> Reviewed-by: Dan Shi <dshi@chromium.org> Commit-Queue: Prashanth B <beeps@chromium.org> /external/autotest/site_utils/test_that.py