| 9aec6930955ea7d3d345cf2d214f9e6982f84cb8 |
|
03-Jun-2016 |
Richard Barnette <jrbarnette@chromium.org> |
[autotest] Remove the last of the support for kernel selection.
This removes all the vestiges related to support selecting a kernel
for test from client side code. This completes removal of all such
code from the Chrome OS fork of Autotest.
N.B. It's possible that there are still design concepts within the
code that exist primarily for the benefit of kernel selection.
Finding and simplifying those design concepts are left for the
next intrepid developer.
BUG=chromium:266704
TEST=Run push_to_prod suite in a local instance.
Change-Id: I7a8bbee0f58c14c4826689d5d04999b3708ad5f6
Reviewed-on: https://chromium-review.googlesource.com/349710
Commit-Ready: Richard Barnette <jrbarnette@chromium.org>
Tested-by: Richard Barnette <jrbarnette@chromium.org>
Reviewed-by: Aviv Keshet <akeshet@chromium.org>
/external/autotest/client/bin/setup_job_unittest.py
|
| 67ad67d564fd605dc0ac3671b1620a601cfc6c90 |
|
29-Jun-2016 |
Justin Giorgi <jgiorgi@google.com> |
[autotest] Removed copy of unittest library.
All tests still pass with the standard unittest library.
BUG=None
TEST=Executed utils/unittest_suite.py locally
Change-Id: I86f7e2884282bca0fcb240fe2f70c4adb71f8ddf
Reviewed-on: https://chromium-review.googlesource.com/357330
Commit-Ready: Justin Giorgi <jgiorgi@google.com>
Tested-by: Justin Giorgi <jgiorgi@google.com>
Reviewed-by: Richard Barnette <jrbarnette@google.com>
Reviewed-by: Simran Basi <sbasi@chromium.org>
/external/autotest/client/bin/setup_job_unittest.py
|
| eeb1cad28c83faacb7bc51a4630154e9ca122088 |
|
13-Feb-2013 |
Aviv Keshet <akeshet@chromium.org> |
[autotest] Fix unittest -- client/bin/setup_job
Unit test for setup_job was broken back in a previous merge of upstream
autotest, commit 8adf78936c915df6fd1edb6c592f40a7ed8350a5 . This commit
fixes the broken tests by adding the new required argument to
job.__init__ calls.
BUG=chromium-os:37989
TEST=Unit tests for this module now pass
Change-Id: I7e9011a71b578dd1108ac80c29b25c3482f0bb43
Reviewed-on: https://gerrit.chromium.org/gerrit/43208
Commit-Queue: Aviv Keshet <akeshet@chromium.org>
Reviewed-by: Aviv Keshet <akeshet@chromium.org>
Tested-by: Aviv Keshet <akeshet@chromium.org>
/external/autotest/client/bin/setup_job_unittest.py
|
| 861b2d54aec24228cdb3895dbc40062cb40cb2ad |
|
04-Feb-2011 |
Eric Li <ericli@chromium.org> |
Merge remote branch 'cros/upstream' into master
Merged to upstream autotest @4749~@5215.
The entire change list description is too big to enlist here. Please refer to upstream (http://autotest.kernel.org/browser) for more details.
BUG=
TEST=emerged both x86 and arm build.
Tested emerged x86 build bvt against a chromeos device.
Review URL: http://codereview.chromium.org/6246035
Change-Id: I8455f2135c87c321c6efc232e2869dc8f675395e
/external/autotest/client/bin/setup_job_unittest.py
|
| be583c18a66815a3d93fae411c5fd58788aff4c0 |
|
23-Jul-2010 |
lmr <lmr@592f7852-d20e-0410-864c-8624ca9c26a4> |
Crash handler: Make sure autotest cleans up leftover debugdir files
Sometimes, autotest might abort (autotest bug, job error) and
there will be some /tmp/autotest_results_dir.XXX files lying
around. If there are such files lying around, if a program
segfaults, the crash handler will re-create some of the old
debugdirs, that might clash with the debugdirs of the tests
being executed on the new job. Make sure we clean up all old
files prior to autotest execution. Updated the unittests
job_unittest and setup_job_unittest accordingly. The unittests
are passing.
Also, fixed up some indentation prolems found on setup_job.py,
and made setup_job_unittest.py executable
Signed-off-by: Lucas Meneghel Rodrigues <lmr@redhat.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@4731 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/client/bin/setup_job_unittest.py
|
| 0e02d3cb4d1bf7c92baa8d181293cc832b14a065 |
|
15-Apr-2010 |
jadmanski <jadmanski@592f7852-d20e-0410-864c-8624ca9c26a4> |
Patch up a broken unit test.
Signed-off-by: John Admanski <jadmanski@google.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@4416 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/client/bin/setup_job_unittest.py
|
| e3a22513ce0a52739f89589c43af9e221e1ada61 |
|
12-Feb-2010 |
mbligh <mbligh@592f7852-d20e-0410-864c-8624ca9c26a4> |
The new flag will prebuild all autotest client tests/site_tests on the server side, when the dev tool chain is not available on the client, by directly invoke the setup method() on the test.
If this flag is not provided on the command line (default behavior), there should be no regression changes to existing usages.
If provided:
--setup=all will prebuild all client tests/site_tests.
--setup=A,B,C,.. will only build the comma separated list of tests supplied.
This new flag does not work with any control file, instead, it works on test classes.
from:ericli@google.com
git-svn-id: http://test.kernel.org/svn/autotest/trunk@4243 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/client/bin/setup_job_unittest.py
|