e4c08273f039d97349999818e25fedbb13cdcb4b |
|
02-Feb-2017 |
Allen Li <ayatane@chromium.org> |
[autotest] Remove synch_id concept BUG=chromium:687781 TEST=None Change-Id: Ibbef8f7b58d7bb26dcbbe85df308b9e0c4b86bd9 Reviewed-on: https://chromium-review.googlesource.com/435711 Commit-Ready: Allen Li <ayatane@chromium.org> Tested-by: Allen Li <ayatane@chromium.org> Reviewed-by: Allen Li <ayatane@chromium.org>
/external/autotest/cli/job_unittest.py
|
b774aa277a9e351708d9a8396ecee846dd0a8e91 |
|
02-Feb-2017 |
Allen Li <ayatane@chromium.org> |
[autotest] Remove site specific stuff from cli BUG=chromium:672727 TEST=Run unittests Change-Id: Ib3b420d95f59f8afd0e90eb598f2988703ebfa14 Reviewed-on: https://chromium-review.googlesource.com/435473 Commit-Ready: Allen Li <ayatane@chromium.org> Tested-by: Allen Li <ayatane@chromium.org> Reviewed-by: Allen Li <ayatane@chromium.org>
/external/autotest/cli/job_unittest.py
|
335f2162d379440c49d9d4a834532c4551f49442 |
|
01-Feb-2017 |
Allen Li <ayatane@chromium.org> |
[autotest] [atomic] Remove atomic groups from cli BUG=chromium:681906 TEST=Run unittest suite Change-Id: I2f9edaa074e4ce7f7d658f79d1256413c34a7a1c Reviewed-on: https://chromium-review.googlesource.com/434108 Commit-Ready: Allen Li <ayatane@chromium.org> Tested-by: Allen Li <ayatane@chromium.org> Reviewed-by: Richard Barnette <jrbarnette@google.com>
/external/autotest/cli/job_unittest.py
|
352b86a33c78c0ad35f55c14ffba11896d27556c |
|
14-Dec-2016 |
Allen Li <ayatane@chromium.org> |
[autotest] Remove old priority hack This is from 2013, Im assuming the priorities have all been migrated over. The reason for doing this is that the sole purpose of this function is to remove invalid keywords from passing locals() to create_job_common, so this is a step toward removing locals() and this function. BUG=None TEST=CQ Change-Id: Ia5b527b509863bbe12ff047628c23a988dbc32c9 Reviewed-on: https://chromium-review.googlesource.com/420178 Commit-Ready: Allen Li <ayatane@chromium.org> Tested-by: Allen Li <ayatane@chromium.org> Reviewed-by: Prathmesh Prabhu <pprabhu@chromium.org>
/external/autotest/cli/job_unittest.py
|
41e617b8ad86c84e19fc74dd47b44d93c57cb8cd |
|
20-May-2016 |
Richard Barnette <jrbarnette@chromium.org> |
[autotest] Remove atest cli support for specifying a test kernel. The `atest job create` command provided a -k option for specifying a kernel to be tested. The option was a non-functional legacy not applicable to Chrome OS. This deletes the legacy atest CLI code. The underlying RPC calls and features made obsolete by this change will be removed in subsequent CLs. BUG=None TEST=run `atest job create` in a local Autotest instance, plus unit tests Change-Id: I882f96bf940f9de8af1ffd502e7b3f59e6fdddb5 Reviewed-on: https://chromium-review.googlesource.com/346058 Commit-Ready: Richard Barnette <jrbarnette@chromium.org> Tested-by: Richard Barnette <jrbarnette@chromium.org> Reviewed-by: Dan Shi <dshi@google.com>
/external/autotest/cli/job_unittest.py
|
ec1d47d85cc83f30631518d8fbb6406036a3ac39 |
|
13-Feb-2015 |
Dan Shi <dshi@chromium.org> |
[autotest] Add support for scheduler to honor require_ssp attribute in control file This CL adds changes to pipe require_ssp attribute in control file to autoserv command. Following are the work flow: 1. The control file parser stores require_ssp attribute value in afe_jobs table. 2. QueueTask compiles command line list, --require-ssp option will be added to the command line list if following conditions are met: a. AUTOSERV/enable_ssp_container in global config is True b. The test is a server-side test c. require_ssp for the job entry is None or True. 3. When agent_task tries to call run method to run the command, it will check if there is any drone supporting server-side packaging first. If no drone is found, the agent task will will run the command in a drone without using server-side packaging. A warning will be posted in the autoserv log. 4. If a drone without SSP supported is assigned to a test requires SSP, the test will be run without ssp. BUG=chromium:453624 TEST=unittest, local test: set AUTOSERV/enable_ssp_container to True in shadow config; Create a job for dummy_PassServer in AFE, check require SSP, confirm the job succeeds but with a warning in the autoserv log. Create a job for dummy_PassServer_nossp in AFE, uncheck require SSP, confirm the job passes without warning in the autoserv log. set AUTOSERV/enable_ssp_container to False in shadow config, restart scheduler. Create a job for dummy_PassServer in AFE, check require SSP, confirm the job succeeds without warning in the autoserv log. also run test_that in local chroot to make sure test_that is not affected. DEPLOY=apache,scheduler, db migrate must be done before push this CL to prod. Change-Id: I02f3d137186676ae570e8380d975a1bcd9ffbb94 Reviewed-on: https://chromium-review.googlesource.com/249841 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/cli/job_unittest.py
|
7e60574f3baa0b3928623216a74a770f19d2c316 |
|
12-Nov-2013 |
Simran Basi <sbasi@chromium.org> |
Autotest: Update RPC, Scheduler and AFE to use timeout_mins. Now that timeout_mins is in the database, we need to update the infrastructure to display and utilize timeout_mins rather than timeout. The scheduler now aborts based off of timeout_mins. The afe displays/creates jobs using timeout_mins rather than timeout. The RPC's take in timeout and timeout_min depending on what is inputted to the system. Note the value supplied for timeout_mins takes precedence over timeout. BUG=chromium:221264 TEST=Created job through AFE, run_suite with smoke suite, job_unittest and rpc_unittests. DEPLOY=apache, afe, scheduler CQ-DEPEND=I09f8b6023a31dcef37e98c298dc0d63b37bc0a9e Change-Id: I838cd1ff85a2ce6bd49fe96bf18fd82be608c758 Reviewed-on: https://chromium-review.googlesource.com/176605 Reviewed-by: Simran Basi <sbasi@chromium.org> Commit-Queue: Simran Basi <sbasi@chromium.org> Tested-by: Simran Basi <sbasi@chromium.org>
/external/autotest/cli/job_unittest.py
|
3dd8beb386f7298ffe84d7410d00cce26973e170 |
|
14-May-2013 |
Aviv Keshet <akeshet@chromium.org> |
[autotest] make a consistent CONTROL_TYPE enum across the codebase Prior to this CL, there were a multitude of duplicate defitions of the two control files types (Client or Server), incluiding a difference between the afe Job model (1 = Server) and the afe Test model (1 = Client). This CL introduces enums CONTROL_TYPE and CONTROL_TYPE_NAMES to control_data, to act as the central and consistent defition across the codebase. In order to avoid needing to mangle the running Jobs table, we have adopted the existing Job model convention (1 = Server); the Test table will be re-written with the new consistent convention during test import. BUG=chromium:240643 TEST=All existing unit tests pass; In local autotest without this patch applied, started a suite. Halfway through suite, applied this patch, ran test importer, restarted apache, and restarted scheduler. Suite finished successfully. Verified manually that Client/Server type control files show up correctly in afe Create Job view. DEPLOY=scheduler DEPLOY=apache DEPLOY=test_importer Change-Id: Ia5b2573e1d08d96b3826f2837903ef407dcae303 Reviewed-on: https://gerrit.chromium.org/gerrit/51191 Commit-Queue: Aviv Keshet <akeshet@chromium.org> Reviewed-by: Aviv Keshet <akeshet@chromium.org> Tested-by: Aviv Keshet <akeshet@chromium.org>
/external/autotest/cli/job_unittest.py
|
34217022229b755bc1ee52f83665acba76bd5044 |
|
06-Nov-2012 |
Simran Basi <sbasi@chromium.org> |
Autotest: Increase run timeout granularity This CL modifies all references to max_runtime_hrs to instead be max_runtime_mins. This includes the django models, rpc interfaces, the cleanup timeout code, and the frontend java views. The frontend java code will need to be recompiled once this commits to prevent the frontend from breaking. The cleanup timeout pathway has been adjusted to find all timedout jobs by minute, and has been changed to run every 5 minutes vs every hour as before. BUG=chromium-os:36067 TEST=Ran on my local afe, ensure that jobs can still be created correctly, and jobs with short timeouts do indeed get aborted when expected. Change-Id: Idfdeb3f1d4947d6b2e6b48127a31db535704e972 Reviewed-on: https://gerrit.chromium.org/gerrit/37827 Tested-by: Simran Basi <sbasi@chromium.org> Reviewed-by: Scott Zawalski <scottz@chromium.org> Reviewed-by: Simran Basi <sbasi@chromium.org> Commit-Ready: Simran Basi <sbasi@chromium.org>
/external/autotest/cli/job_unittest.py
|
a8a0d75c2591ab872f695d7b8f22f2ca10493dab |
|
08-Nov-2012 |
Scott Zawalski <scottz@chromium.org> |
Revert "Autotest: Increase run timeout granularity" This causes autoupdate problems, see bug crosbug.com/36183 This reverts commit daffa57a6738c2a80caee1f311a527313ece1207 Change-Id: Iad65be9bf1b0ea329866bfdc764b0089c4f9b2a5 Reviewed-on: https://gerrit.chromium.org/gerrit/37657 Commit-Ready: Scott Zawalski <scottz@chromium.org> Reviewed-by: Scott Zawalski <scottz@chromium.org> Tested-by: Scott Zawalski <scottz@chromium.org>
/external/autotest/cli/job_unittest.py
|
daffa57a6738c2a80caee1f311a527313ece1207 |
|
06-Nov-2012 |
Simran Basi <sbasi@chromium.org> |
Autotest: Increase run timeout granularity This CL modifies all references to max_runtime_hrs to instead be max_runtime_mins. This includes the django models, rpc interfaces, the cleanup timeout code, and the frontend java views. The frontend java code will need to be recompiled once this commits to prevent the frontend from breaking. The cleanup timeout pathway has been adjusted to find all timedout jobs by minute, and has been changed to run every 5 minutes vs every hour as before. BUG=chromium-os:36067 TEST=Ran on my local afe, ensure that jobs can still be created correctly, and jobs with short timeouts do indeed get aborted when expected. Change-Id: Id7668bbd05a9b02c22e7c549fac232fae02fc728 Reviewed-on: https://gerrit.chromium.org/gerrit/37479 Reviewed-by: Scott Zawalski <scottz@chromium.org> Commit-Ready: Simran Basi <sbasi@chromium.org> Tested-by: Simran Basi <sbasi@chromium.org>
/external/autotest/cli/job_unittest.py
|
74a314b490ff542c4dd2ae4aa0d11c6394d92960 |
|
23-Jun-2011 |
Dale Curtis <dalecurtis@chromium.org> |
Upstream Autotest merge. As titled, a merge up to 93fc426ca133e775eb495f34d138fc57d92fb55e. - Removes a bunch of deprecated code. - Moves several private utilities into the private repo. - Couple changes ported upstream and resynced. BUG=None TEST=In progress... will spin up new Autotest server and use run_remote_tests for bvt, regression, smoke. Change-Id: Id3e2ad529bb7b05f148e5d98aea46bb9ea828200 Reviewed-on: http://gerrit.chromium.org/gerrit/3350 Tested-by: Dale Curtis <dalecurtis@chromium.org> Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
/external/autotest/cli/job_unittest.py
|
8a12e800f05f6862fc39c6a45c9c57d9051b795e |
|
17-Feb-2011 |
Eric Li <ericli@chromium.org> |
Merge remote branch 'cros/upstream' into master. Merged to upstream autotest @5216~@5235. Most of the stuff are from Olof's arm cross compiling and some misc changes from Dale Curtis. As usual,the entire change list description is too big to enlist here. Please refer to upstream (http://autotest.kernel.org/browser) for more details. BUG=none TEST=1. emerge-arm-generic autotest autotest-deps autotest-tests 2. emerge-x86-generic autotest autotest-deps autotest-tests 3. run bvt from both src/third_party and inside emerged chroot/..usr/local/autotest. Seems fine. No regression found. Review URL: http://codereview.chromium.org/6539001 Change-Id: I613929ec9c29849db5110ae8234bc68a80f4d2d5
/external/autotest/cli/job_unittest.py
|
c2863163f0305e441e3178b88ab5a80656ca777b |
|
12-Jul-2010 |
jamesren <jamesren@592f7852-d20e-0410-864c-8624ca9c26a4> |
(Submitting for dalecurtis. For some reason, Patchwork doesn't want to pick up his patches...) All, First off, sorry for the spam, hopefully this will be last message and Patchwork will finally pick up the patch. Reposted with modifications from prior discussion per James Ren. Credit for suggestion to split on commas goes to Jongki Suwandi. The "host list", "host create", and "job create" command line options for the atest CLI module do not support labels with commas. In our deployment we have several labels which contain commas, leading to some bad parsing when trying to use the CLI tools. I've added escaped comma support to the topic_common.item_parse_info.get_values.__get_items(...) function to fix this. For example, atest host list --label "label0,comma\,label" will now parse the labels as 'label0' and 'comma,label'. Any option using topic_common.item_parse_info gets this behavior for free. Specifically for our needs, I've changed the "atest host list" and "atest job create" methods from using <string>.split(',') to topic_common.item_parse_info for labels. Implementation wise, I modified the topic_common.item_parse_info.get_values.__get_items(...) regex so that it would only split commas not preceded by slashes. In order to handle labels that may end in slashes, I replace double slashes with a null character before splitting and then put a single slash back afterwards. The new regex is r'(?<!\),|\s' if space splitting is enabled and r'(?<!\),' otherwise. Testing was done through 11 new unit tests, exercising escaped commas with and without preceding escaped slashes. As well as manual testing on our own deployment. All unit tests pass and existing deployments should not be affected. A minor quibble is consistency from a user point of view. I've only added support for escaped commas to the topic_common.item_parse_info class, but there are a couple other areas which are still using <string>.split(',') to parse their options. Specifically status names, host names, test names, and dependencies in the host.py and job.py files. I've left these alone for now, but if anyone objects I can roll them in. I've attached the patch file for the changes, but if you prefer a more GUI driven experience, you can see the change list here: http://codereview.chromium.org/2740001/show Risk: Low-Medium (CLI infrastructure and tests modified) Visibility: CLI users Signed-off-by: Dale Curtis Regards, Dale Curtis Software Engineer in Test @ Google git-svn-id: http://test.kernel.org/svn/autotest/trunk@4718 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/cli/job_unittest.py
|
ad57516bcd19d61b5356ea6330fd1dd1f0c7f3f4 |
|
24-Mar-2010 |
mbligh <mbligh@592f7852-d20e-0410-864c-8624ca9c26a4> |
Fixing the unittest that had wrong lists and only worked because we zipped the lists to compare them Signed-off-by: Jean-Marc Eurin <jmeurin@google.com> git-svn-id: http://test.kernel.org/svn/autotest/trunk@4334 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/cli/job_unittest.py
|
f4a6899c2460fecc0cc0b72727afc9c51cb05da7 |
|
03-Feb-2010 |
showard <showard@592f7852-d20e-0410-864c-8624ca9c26a4> |
Remove /noauth/ usage in CLI. Extracted the bit of the CLI that generates authorization headers into a function with a site override. If you have site-specific authorization in place on your Autotest web service, you'll need to write a site-specific function to generate authorization info to continue using the CLI. I'll send a patch in a week or so to remove the /noauth/ endpoint entirely. Let me know if you have any questions or feedback, I'm happy to help. Signed-off-by: Steve Howard <showard@google.com> git-svn-id: http://test.kernel.org/svn/autotest/trunk@4199 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/cli/job_unittest.py
|
fca5ed16315cef727b62664815848b773fb6de64 |
|
06-Nov-2009 |
mbligh <mbligh@592f7852-d20e-0410-864c-8624ca9c26a4> |
* Add ability to CLI job_stat to display only a list of hosts for a given job with --list-hosts. Also adds --list-hosts-status which takes a list of statuses as an argument and displays hosts in each status. * Remove the check that prevents running a server side job with both the --control-file and --kernel options. This works now. Risk(Low): New functionality could possibly break job_stat Visibility(Low): Useful for grabbing machine lists from Autotest jobs Signed-off-by: Ryan Kubiak <rkubiak@google.com> git-svn-id: http://test.kernel.org/svn/autotest/trunk@3901 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/cli/job_unittest.py
|
c613317ba061b85a38ba51edfca9172f228a83c0 |
|
18-Sep-2009 |
mbligh <mbligh@592f7852-d20e-0410-864c-8624ca9c26a4> |
A few followup enhancements to the recent change made to the cli to enclose the topic names in single quotes. Signed-off-by: Ashwin Ganti <aganti@google.com> git-svn-id: http://test.kernel.org/svn/autotest/trunk@3747 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/cli/job_unittest.py
|
5dc6276b560798fded59e9334a824c839fa7a371 |
|
03-Sep-2009 |
mbligh <mbligh@592f7852-d20e-0410-864c-8624ca9c26a4> |
Add single quotes to the topic value in the output message . Signed-off-by: Ashwin Ganti <aganti@google.com> git-svn-id: http://test.kernel.org/svn/autotest/trunk@3641 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/cli/job_unittest.py
|
a3c58d20be69a292bdfafbea735c7503f4995b4c |
|
25-Aug-2009 |
mbligh <mbligh@592f7852-d20e-0410-864c-8624ca9c26a4> |
Added support to specify cmdline for the booted kernels for both the CLI and the frontend. For the CLI there is a new "--kernel-cmdline" option that will be used for all the kernels configured to be booted with the "-k" parameter. For the frontend there's a new textbox under the kernel version one where cmdline can be provided. Signed-off-by: Mihai Rusu <dizzy@google.com> git-svn-id: http://test.kernel.org/svn/autotest/trunk@3599 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/cli/job_unittest.py
|
56f1f4a9bc430f6bc41cbdc6b1cc88ffebe518aa |
|
03-Aug-2009 |
mbligh <mbligh@592f7852-d20e-0410-864c-8624ca9c26a4> |
Allow to specify hosts when cloning a job. Signed-off-by: Jean-Marc Eurin <jmeurin@google.com> git-svn-id: http://test.kernel.org/svn/autotest/trunk@3481 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/cli/job_unittest.py
|
5a496088c7daa10aad13580615bfd157c4cd8180 |
|
03-Aug-2009 |
mbligh <mbligh@592f7852-d20e-0410-864c-8624ca9c26a4> |
Make 'job clone --id' an action instead of 'job create --clone'. Add the backward compatibility method and call. This is a first step in allowing to specify different hosts when cloning, but it's just a code restructuring, it doesn't fix anything (and hopefully doesnt' break new things either). Signed-off-by: Jean-Marc Eurin <jmeurin@google.com> git-svn-id: http://test.kernel.org/svn/autotest/trunk@3480 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/cli/job_unittest.py
|
4151539ad9880e0329c788b0d25e9998ae1a8f73 |
|
11-Jul-2009 |
mbligh <mbligh@592f7852-d20e-0410-864c-8624ca9c26a4> |
Update CLI to use autotemp for tempfiles Signed-off-by: Scott Zawalski <scottz@google.com> git-svn-id: http://test.kernel.org/svn/autotest/trunk@3396 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/cli/job_unittest.py
|
12f3e3212795a539d95973f893ac570e669e3a22 |
|
13-May-2009 |
showard <showard@592f7852-d20e-0410-864c-8624ca9c26a4> |
Add job maximum runtime, a new per-job timeout that counts time since the job actually started. * added started_on field to host_queue_entries, so that we could actually compute this timeout * added max_runtime_hrs to jobs, with default in global config, and added option to create_job() RPC * added the usual controls to AFE and the CLI for the new job option * added new max runtime timeout method to * added migration to add new fields and set a safe default max runtime for existing jobs Signed-off-by: Steve Howard <showard@google.com> git-svn-id: http://test.kernel.org/svn/autotest/trunk@3132 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/cli/job_unittest.py
|
53cb10c8775e733151297d870ccd401afe90d2d4 |
|
01-May-2009 |
showard <showard@592f7852-d20e-0410-864c-8624ca9c26a4> |
Fix CLI unittests to call check_playback in all cases, not just when run_cmd is used. Signed-off-by: Gregory Smith <gps@google.com> git-svn-id: http://test.kernel.org/svn/autotest/trunk@3075 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/cli/job_unittest.py
|
648a35c560f78874c05582349e1c09632ce210d6 |
|
01-May-2009 |
showard <showard@592f7852-d20e-0410-864c-8624ca9c26a4> |
Add support for submitting a job into an atomic group to the CLI. Signed-off-by: Gregory Smith <gps@google.com> git-svn-id: http://test.kernel.org/svn/autotest/trunk@3071 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/cli/job_unittest.py
|
b27f4adf598062aa35323595c5724111ffbac202 |
|
01-May-2009 |
showard <showard@592f7852-d20e-0410-864c-8624ca9c26a4> |
Update CLI to allow scheduling jobs against labels Signed-off-by: Ryan Kubiak <rkubiak@google.com> git-svn-id: http://test.kernel.org/svn/autotest/trunk@3070 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/cli/job_unittest.py
|
ce34864d7aa45fc0f2927840af734c6ad2f0325d |
|
12-Feb-2009 |
mbligh <mbligh@592f7852-d20e-0410-864c-8624ca9c26a4> |
Adding support for one time hosts. Signed-off-by: Jean-Marc Eurin <jmeurin@google.com> git-svn-id: http://test.kernel.org/svn/autotest/trunk@2784 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/cli/job_unittest.py
|
a212d716ac00059fd7839c14a72c0bdf2475cd09 |
|
11-Feb-2009 |
mbligh <mbligh@592f7852-d20e-0410-864c-8624ca9c26a4> |
Cleanup the container code from the CLI. Signed-off-by: Jean-Marc Eurin <jmeurin@google.com> git-svn-id: http://test.kernel.org/svn/autotest/trunk@2772 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/cli/job_unittest.py
|
0887d402476b4a873f0664ddb88d3e43005f6113 |
|
30-Jan-2009 |
mbligh <mbligh@592f7852-d20e-0410-864c-8624ca9c26a4> |
Fix atest label list --all. A FE change from 0/1 to False/True had broken it. Signed-off-by: Jean-Marc Eurin <jmeurin@google.com> git-svn-id: http://test.kernel.org/svn/autotest/trunk@2713 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/cli/job_unittest.py
|
120351e0c9a9b3e7c7a4aa51477a5ae2366214c4 |
|
24-Jan-2009 |
mbligh <mbligh@592f7852-d20e-0410-864c-8624ca9c26a4> |
Allow control file body text to be supplied as an alternative to a list of test names for the generate_control_file AFE rpc. This allows the command line client to let people specify a kernel along with their own client-side control file. It adds the kernel installation steps to the supplied control file before scheduling it (using the same code as the GUI when a kernel is specified there). Signed-off-by: Gregory Smith <gps@google.com> git-svn-id: http://test.kernel.org/svn/autotest/trunk@2684 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/cli/job_unittest.py
|
5d0b4b3d9bd4a9f73e4d26d98e5f29fb3ef29563 |
|
22-Dec-2008 |
mbligh <mbligh@592f7852-d20e-0410-864c-8624ca9c26a4> |
* Add option to disable verify for created jobs * Add option to specify a job timeout for created jobs Visibility(Medium): New job create options Risk(Low): Adding new options, default beahavior remains Signed-off-by: Ryan Kubiak <rkubiak@google.com> git-svn-id: http://test.kernel.org/svn/autotest/trunk@2578 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/cli/job_unittest.py
|
7bce1021117066ae6d7cf9f03a61c22e107457ef |
|
14-Nov-2008 |
showard <showard@592f7852-d20e-0410-864c-8624ca9c26a4> |
Make job create CLI parse synch_count as an int instead of a string. git-svn-id: http://test.kernel.org/svn/autotest/trunk@2422 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/cli/job_unittest.py
|
206d50a5f82c213caac4d115164bb5996386ac26 |
|
13-Nov-2008 |
mbligh <mbligh@592f7852-d20e-0410-864c-8624ca9c26a4> |
Fix the CLI job abort to use new RPC. Worth noting that the new RPC does not return an error if job IDs do not exist so the unittest for aborting an unknown job was removed. Abort could be changed to check to see if the jobs exist first, but last time I did that the general consensus was it was unnecessary. Risk(Low): Abort is already broken Visibility(Medium): CLI job abort now works again Signed-off-by: Ryan Kubiak <rkubiak@google.com> git-svn-id: http://test.kernel.org/svn/autotest/trunk@2409 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/cli/job_unittest.py
|
fb8f0ab0c168fb477b5eb756d041d06e3491bbde |
|
13-Nov-2008 |
mbligh <mbligh@592f7852-d20e-0410-864c-8624ca9c26a4> |
* Add job cloning functionality to the CLI * Move parse_hosts from job_create to action_common Risk(Low): Implements a new feature Visibility(Medium): Users can now clone jobs through the CLI Signed-off-by: Ryan Kubiak <rkubiak@google.com> git-svn-id: http://test.kernel.org/svn/autotest/trunk@2408 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/cli/job_unittest.py
|
2bab8f45adedeacbf2d62d37b90255581adc3c7d |
|
12-Nov-2008 |
showard <showard@592f7852-d20e-0410-864c-8624ca9c26a4> |
Implement sync_count. The primary change here is replacing the job.synch_type field with a synch_count field. There is no longer just a distinction between synchronous and asynchronous jobs. Instead, every job as a synch_count, with synch_count = 1 corresponding to the old concept of synchronous jobs. This required: -changes to the job creation RPC and corresponding client code in AFE and the CLI -massive changes to the scheduler to schedule all jobs in groups based on synch_count (this unified the old synch and async code paths) -changed results directory structure to accomodate synchronous groups, as documented at http://autotest.kernel.org/wiki/SchedulerSpecification, including widespread changes to monitor_db and a change in AFE -changes to AFE abort code to handle synchronous groups instead of just synchronous jobs -also got rid of the "synchronizing" field in the jobs table, since I was changing the table anyway and it seems very likely now that that field will never be used other changes included: -add some logging to afe/models.py to match what the scheduler code does, since the scheduler is starting to use the models more -added checks for aborts of synchronous groups to abort_host_queue_entries RPC git-svn-id: http://test.kernel.org/svn/autotest/trunk@2402 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/cli/job_unittest.py
|
b9a8b166937bf37213649b4fd3b17e48423d1dc7 |
|
29-Oct-2008 |
mbligh <mbligh@592f7852-d20e-0410-864c-8624ca9c26a4> |
Change --dependencies flag to --labels flag to be more consistent. Also let people add their own dependencies even if they specified a test via --test. Risk: Low Visibility: High Signed-off-by: Jeremy Orlow <jorlow@google.com> git-svn-id: http://test.kernel.org/svn/autotest/trunk@2356 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/cli/job_unittest.py
|
0a6691339e16267ca93f891cdbfc503ae093761b |
|
10-Oct-2008 |
mbligh <mbligh@592f7852-d20e-0410-864c-8624ca9c26a4> |
Add some unittests for my new CLI features. Risk: Low Visibility: Low Signed-off-by: Jeremy Orlow <jorlow@google.com> git-svn-id: http://test.kernel.org/svn/autotest/trunk@2272 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/cli/job_unittest.py
|
6fee7fd5493d49fecc3aaa71e71f11c593699f93 |
|
10-Oct-2008 |
mbligh <mbligh@592f7852-d20e-0410-864c-8624ca9c26a4> |
Add the option to specify an email address to be notified on job completion. Risk: Low Visibility: High Signed-off-by: Jeremy Orlow <jorlow@google.com> git-svn-id: http://test.kernel.org/svn/autotest/trunk@2268 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/cli/job_unittest.py
|
989f25dcbb6361218f0f84d1c8404761b4c39d96 |
|
01-Oct-2008 |
showard <showard@592f7852-d20e-0410-864c-8624ca9c26a4> |
two new major features: (1) added test and job dependencies -added M2M relationship between tests and labels and between jobs and labels, for tracking the labels on which a test/job depends -modified test_importer to read the DEPENDENCIES field and create the right M2M relationships -modified generate_control_file() RPC to compute and return the union of test dependencies. since generate_control_file now returns four pieces of information, i converted its return type from tuple to dict, and changed clients accordingly. -modified job creation clients (GWT and CLI) to pass this dependency list to the create_job() RPC -modified the create_job() RPC to check that hosts satisfy job dependencies, and to create M2M relationships -modified the scheduler to check dependencies when scheduling jobs -modified JobDetailView to show a job's dependencies (2) added "only_if_needed" bit to labels; if true, a machine with this label can only be used if the label is requested (either by job dependencies or by the metahost label) -added boolean field to Labels -modified CLI label creation/viewing to support this new field -made create_job() RPC and scheduler check for hosts with such a label that was not requested, and reject such hosts also did some slight refactoring of other code in create_job() to simplify it while I was changing things there. a couple notes: -an only_if_needed label can be used if either the job depends on the label or it's a metahost for that label. we assume that if the user specifically requests the label in a metahost, then it's OK, even if the job doesn't depend on that label. -one-time-hosts are assumed to satisfy job dependencies. Signed-off-by: Steve Howard <showard@google.com> git-svn-id: http://test.kernel.org/svn/autotest/trunk@2215 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/cli/job_unittest.py
|
8d631c9d894ee1f438733530fb8b966f7af07df1 |
|
18-Aug-2008 |
jadmanski <jadmanski@592f7852-d20e-0410-864c-8624ca9c26a4> |
Convert all our uses of directoy SSHHost construction over to use hosts.create_host instead. Also, fix up a bunch of test references that use SSHHost when they really just need to run against the abstract RemoteHost class, and fix some tests using the MockSSHHost class to just use the mock framework instead. Risk: Low Visibility: Gets rid of almost all direct references to SSHHost. Signed-off-by: John Admanski <jadmanski@google.com> git-svn-id: http://test.kernel.org/svn/autotest/trunk@2010 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/cli/job_unittest.py
|
be630eb07ddb84310fcc580acffcaa362a2dc606 |
|
01-Aug-2008 |
mbligh <mbligh@592f7852-d20e-0410-864c-8624ca9c26a4> |
Attached is the CLI code tarball. It is documented at http://test.kernel.org/autotest/CLIHowTo From: jmeurin@google.com git-svn-id: http://test.kernel.org/svn/autotest/trunk@1950 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/cli/job_unittest.py
|