| 02b6fee0016c10331831a1a7d0463d0c2c07f8b6 |
|
02-Feb-2017 |
xixuan <xixuan@chromium.org> |
autotest: add logging in testing control files.
This CL adds more loggings for running tests by control files.
BUG=chromium:674598
TEST=Run autoupdate_End_to_End test in local AFE and verify loggings.
Change-Id: I7c6696d2d46c8e2eff9dc744f9be53fa6045f5f1
Reviewed-on: https://chromium-review.googlesource.com/435964
Commit-Ready: Xixuan Wu <xixuan@chromium.org>
Tested-by: Xixuan Wu <xixuan@chromium.org>
Reviewed-by: Luigi Semenzato <semenzato@chromium.org>
/external/autotest/server/test.py
|
| d7f1242be09c5f889641af4783f26e3a470bae1d |
|
04-Jan-2016 |
Dan Shi <dshi@google.com> |
[autotest] Add a dummy test for testbed.
This change also updates the special task control segments to support testbed.
BUG=chromium:574173
TEST=local run the dummy test.
Change-Id: I233511fa340050b74df3fdbcc76c4a408ded5fcf
Reviewed-on: https://chromium-review.googlesource.com/320204
Commit-Ready: Dan Shi <dshi@chromium.org>
Tested-by: Dan Shi <dshi@google.com>
Reviewed-by: Simran Basi <sbasi@chromium.org>
/external/autotest/server/test.py
|
| 1bf60eb788365f083d0ee8045a6556f906149dec |
|
02-Dec-2015 |
Simran Basi <sbasi@google.com> |
[autotest] autoserv add --lab & --host_attributes arguments
Added two new flags to autoserv.
--lab indicates that autoserv is running in the lab and has
the full Autotest infrastructure at its disposal.
--host_attributes allows host attribute information that is
usually in the database to be retrievable from the command
line arguments.
If --lab is pulled in, autoserv will request the host attributes
from the database at test runtime.
From here this change, then updates the concept of the "machines"
list that test control files receive to now be a list of dicts
that contain the machine hostname and host attributes. This will
enable identifing information the hosts library needs to create
host objects to be available whether or not there is a database
present.
BUG=chromium:564343
TEST=local autoserv runs. Also verified scheduler changes work
via MobLab. waiting on trybot results.
DEPLOY=scheduler
Change-Id: I6021de11317e29e2e6c084d863405910c7d1a71d
Reviewed-on: https://chromium-review.googlesource.com/315230
Commit-Ready: Simran Basi <sbasi@chromium.org>
Tested-by: Simran Basi <sbasi@chromium.org>
Reviewed-by: Simran Basi <sbasi@chromium.org>
/external/autotest/server/test.py
|
| 1c3b853b2d9b80c9efcc1a27112731b96d765e6e |
|
19-Nov-2015 |
J. Richard Barnette <jrbarnette@chromium.org> |
[autotest] Remove dead code/features from hosts factory.
The code for create_host() in server/hosts/factory.py had a large
amount of unused legacy code left behind. This change removes all
of that unused legacy.
BUG=None
TEST=run all unit tests
Change-Id: I727521aa27e82c86e04ab3d6b62cbd9e4158f00b
Reviewed-on: https://chromium-review.googlesource.com/313192
Commit-Ready: Richard Barnette <jrbarnette@chromium.org>
Tested-by: Richard Barnette <jrbarnette@chromium.org>
Reviewed-by: Simran Basi <sbasi@chromium.org>
/external/autotest/server/test.py
|
| 7093669cc7037b0d7c03c5097065bd86a02e721e |
|
13-Oct-2015 |
Kevin Cheng <kevcheng@chromium.org> |
[autotest] Add in check for server test to skip sysinfo hooks.
For ADBHost, host client install is not supported and will pollute the
logs with exceptions of the install failing. This will allow ADBHost to
skip the client install steps for the time being until it is supported,
then another cl should rip out the changes from this cl.
BUG=chromium:542808
TEST=Ran dummy pass server and checked debug logs for lack of stack
trace. https://paste.googleplex.com/5661392518512640
CQ-DEPEND=CL:305569
Change-Id: Ie2dd4ad4373b61c98ca7985971bd9af8ef4131b0
Reviewed-on: https://chromium-review.googlesource.com/305368
Commit-Ready: Kevin Cheng <kevcheng@chromium.org>
Tested-by: Kevin Cheng <kevcheng@chromium.org>
Reviewed-by: Simran Basi <sbasi@chromium.org>
/external/autotest/server/test.py
|
| c2282213e0c17496c395d0c7f6ac45732dcd0935 |
|
26-Jan-2015 |
Fang Deng <fdeng@chromium.org> |
[autotest] Disable post-test and iteration sysinfo in provisioning
Sysinfo is taking 2 mins in provisioning. Post-provisioning
sysinfo is not that interesting. And in case a provisioning job
fails, the following repair will still collect logs.
Also disable per-iteration sysinfo which doesn't make sense
for provisioning since it only run once.
BUG=chromium:426141
TEST=Run a provisioning job and observe only pre-test sysinfo
is collected.
Change-Id: I57c95abb410a3be31b34e093f6a67e668ea4249c
Reviewed-on: https://chromium-review.googlesource.com/243361
Reviewed-by: Fang Deng <fdeng@chromium.org>
Tested-by: Fang Deng <fdeng@chromium.org>
Commit-Queue: Fang Deng <fdeng@chromium.org>
/external/autotest/server/test.py
|
| 4eba9f0d9fdac5dc3a57663a42ffadd559da4655 |
|
18-Jun-2014 |
Dan Shi <dshi@chromium.org> |
[autotest] Enable log_diff for server side test.
The bug was introduced when we try to force to collect all logs if a test
failed, refer to CL:
https://chromium-review.googlesource.com/#/c/174058
For server side test, the success flag does not pass to the code to run
log_after_each_test, thus all logs are collected by default.
The fix is to add a line of code in _sysinfo_after_test_script to pass the
flag mytest.success to the script to run on the dut.
Also update dummy_FailServer to be consistent on naming.
BUG=chromium:386242
TEST=test_that 172.22.30.146 dummy_PassServer
confirm only the log diff is collected:
/tmp/test_that_results_8Xj6Qj/results-1-dummy_PassServer/dummy_PassServer/sysinfo/var/log_diff/
test_that 172.22.30.146 dummy_FailServer
confirm the full log is collected:
/tmp/test_that_results_iAOAfZ/results-1-dummy_FailServer/dummy_FailServer/sysinfo/var/log/
Change-Id: Icec189c1c0d05ece11d41c68517b6671193a9cd9
Reviewed-on: https://chromium-review.googlesource.com/204488
Reviewed-by: Dan Shi <dshi@chromium.org>
Commit-Queue: Dan Shi <dshi@chromium.org>
Tested-by: Dan Shi <dshi@chromium.org>
/external/autotest/server/test.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/server/test.py
|
| 9285ddf562c698fda569390be6763170215663d7 |
|
05-Jan-2011 |
Dale Curtis <dalecurtis@chromium.org> |
Rollback ignore_aborts change.
We're no longer seeing any unexpected aborts and have not for a couple months. In order to track better with upstream, this change rolls back the work arounds we introduced for the issue.
Change-Id: I078385946a0c44d9bf90b0a7cf46c30dc765f144
BUG=chromium-os:7931
TEST=
Review URL: http://codereview.chromium.org/6020015
/external/autotest/server/test.py
|
| 0b6843a4482ed69c8fa965612c097711a00eca4a |
|
16-Nov-2010 |
Dale Curtis <dalecurtis@chromium.org> |
Fix server side autotests installing to the wrong directory.
I've added two new constants to global_config.ini: chromeos_client_autodir (default: /mnt/stateful_partition/autotest) and chromeos_client_mount (default: /home/autotest_mount). Autotest will now always create these directories and then mount chromeos_client_autodir at chromeos_client_mount as executable.
A previous change did this for all client tests, but server side tests were over looked. Original CL is at http://codereview.chromium.org/3763007/show . I've merely relocated the code into autotest.py and updated unit tests and surrounding code.
Since the original variable for client installation, client_autodir_paths, has no meaning for us in Chrome OS. I've removed it and ensured there are no dependencies.
Some tests will need modification to work properly as they improperly hard coded the path to the autotest directory instead of querying the autodir variable.
Change-Id: Ic8f9171d14a754d86f38ec882006a4217eab8ec3
BUG=8336
TEST=Ran unit tests. Tested in production; ran bvt, works fine.
Review URL: http://codereview.chromium.org/4176007
/external/autotest/server/test.py
|
| f9d7d8d00c06566ff75b513061be2dcb15b2257a |
|
20-Oct-2010 |
Dale Curtis <dalecurtis@chromium.org> |
We're encountering a significant number of unexpected aborts in the pre/post-test and pre/post-iteration sysinfo collection. After a week of debugging I'm no closer to determining the underlying cause.
In the mean time, I've prepared this CL to prevent Autotest from recording a job as aborted if the abort happens in the pre/post-test or pre/post-iteration sysinfo collection phase.
Change-Id: I2082415ce85e73b469934f7ac39035ed490e98d7
BUG=7931
TEST=Running in production. Observe bug does not trigger abort.
Review URL: http://codereview.chromium.org/3919001
/external/autotest/server/test.py
|
| 44dedf97dac839bbdcbd5c4626215e9aa8aa8d57 |
|
15-Oct-2010 |
Dale Curtis <dalecurtis@chromium.org> |
Since Chrome OS is running tmpfs, we shouldn't be running Autotest client from /tmp. Further, with fes's upcoming changes to make all user directories as noexec we need to be elsewhere anyways.
With this change, the new Autotest client directory is at /mnt/stateful_partition/autotest. We then mount --bind this to /home/autotest_mount and remount that bind as executable.
Change-Id: I94797159279854077e302565cd69ec0371f2af3d
BUG=
TEST=Remounted /tmp as noexec, ran a few stand alone test cases plus a full BVT. All tests completed as expected.
Review URL: http://codereview.chromium.org/3763007
/external/autotest/server/test.py
|
| 12b45582c04b2417036a6f11afc843ac5fddea50 |
|
11-Jan-2010 |
lmr <lmr@592f7852-d20e-0410-864c-8624ca9c26a4> |
Massive permission fix
Fix permissions for all the development tree
Signed-off-by: Lucas Meneghel Rodrigues <lmr@redhat.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@4094 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/server/test.py
|
| f780bbfa740b0706cec4e7bf42747cda5d457da9 |
|
03-Sep-2009 |
mbligh <mbligh@592f7852-d20e-0410-864c-8624ca9c26a4> |
Fix up the sysinfo install procedure to be more transactional. If
the autotest installation fails we want the logger object to remain
uninstalled, with no Host and Autotest objects associated with it.
Whatever caused the install to fail will still fail the sysinfo
collection, but this should at least expose the root cause of the
failure.
Also drops the sysinfo keyval collection from the post-iteration
hook. The post-iteration code doesn't ever generate such a keyval
so this will always fail. It doesn't cause any problems, but it's
pointless noise.
Risk: Low
Visibility: Eliminate an area where the sysinfo collection can
fail with an error that masks the real cause of the failure.
Signed-off-by: John Admanski <jadmanski@google.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@3650 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/server/test.py
|
| 43dd549ce3ec132c24d2cbeb1c233cd887f5d1e8 |
|
03-Sep-2009 |
mbligh <mbligh@592f7852-d20e-0410-864c-8624ca9c26a4> |
Add a mechanism for server-side tests to declare which of their
parameters is the Host object they run on. Also adds code to the
server test execution to automatically call Host.log_kernel before
each of those tests, so that we can ensure that the kernel a
single-machine server test is running on is always captured.
Risk: Low
Visibility: Adds semi-automatic kernel logging for server tests
Signed-off-by: John Admanski <jadmanski@google.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@3640 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/server/test.py
|
| 27b529165c63274395ff1d207e346201cea4cb25 |
|
14-Aug-2009 |
jadmanski <jadmanski@592f7852-d20e-0410-864c-8624ca9c26a4> |
Get rid of the "lightweight" autotest install option, in favour of
just always doing a thin install whenever possible; now that the
packaging-via-autoserv is supported, this should almost always be the
case.
Risk: Low
Visibility: Get rid of explicit lightweight installs, in favour of
automatic ones whenever possible.
Signed-off-by: John Admanski <jadmanski@google.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@3544 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/server/test.py
|
| 089f1e3c2cd3acba1a703b5460a52ef6181fd717 |
|
22-Jun-2009 |
mbligh <mbligh@592f7852-d20e-0410-864c-8624ca9c26a4> |
Changed server sysinfo support code to reinstall the sysinfo Autotest
object and recreate the temporary output dir if it notices they are
missing (say if the test code removes them, they are allowed to do
that). Also changed it to uninstall the sysinfo Autotest client and
remove the contents of the outputdir after each sysinfo step if the test
has set to True a flag attribute named 'disable_sysinfo_install_cache'.
Signed-off-by: Mihai Rusu <dizzy@google.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@3311 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/server/test.py
|
| 3524589241ead1fcbc3b9e7f31648850463d01ad |
|
08-Jun-2009 |
mbligh <mbligh@592f7852-d20e-0410-864c-8624ca9c26a4> |
Changed server side sysinfo support code to remember the host/autotest
and temporary work dir values and reuse them across the various sysinfo
steps. Still supports only a single host per sysinfo object instance
(which means it works with multiple machines if one uses
job.parallel_simple and such to run their server side test, it does not
work with server side tests that don't do that and work directly with
all the machines in their test class code).
Signed-off-by: Mihai Rusu <dizzy@google.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@3207 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/server/test.py
|
| 11fbbcef33f34d06e3c86b47682a4bdb8ff80af9 |
|
28-Apr-2009 |
jadmanski <jadmanski@592f7852-d20e-0410-864c-8624ca9c26a4> |
Because we all love another layer of try-finally indentation...make
sure the server-side sysinfo collection cleans up the Host objects
it use. It can be expensive to leave these objects lying around,
waiting for the end-of-job cleanup to finalize them. We know they're
not needed anymore after these lines, so why not clean them up?
Risk: Low
Visibility: Cleans up remote temp directories more eagerly, and
avoids profiler proliferation.
Signed-off-by: John Admanski <jadmanski@google.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@3043 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/server/test.py
|
| 046599115eb5f685e2a8248017b2cdebfb709175 |
|
01-Apr-2009 |
jadmanski <jadmanski@592f7852-d20e-0410-864c-8624ca9c26a4> |
Fix up the sysinfo install-and-run decorator try-finally structure to
work reliably in the case that the installation or temp dir
creation fails; it should only try to clean up objects that were
allocated, or else it'll run into UnboundLocalError messages.
Risk: Low
Visibility: Fixes up some finally blocks that didn't work in the
case of failure.
Signed-off-by: John Admanski <jadmanski@google.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@2948 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/server/test.py
|
| 7c7aff3a2ed5787d502642a3f5eaa0107aad1661 |
|
25-Mar-2009 |
jadmanski <jadmanski@592f7852-d20e-0410-864c-8624ca9c26a4> |
Fix up the server-side sysinfo collection (again) to make sure all
temp directories and installs on the host machine are removed. Since
the install->run collection->remove pattern seems to be pretty common,
I extracted it out into a dectorator.
Risk: Low
Visibility: Should eliminate more sysinfo collection junk eagerly.
Signed-off-by: John Admanski <jadmanski@google.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@2938 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/server/test.py
|
| ea45566e16b5021dea5f74af54e7e635af79fb5e |
|
25-Mar-2009 |
jadmanski <jadmanski@592f7852-d20e-0410-864c-8624ca9c26a4> |
Add support for explicitly removing tempdirs created on a host,
and modify the server-side sysinfo to use this to clean up the
sysinfo directory immediately.
Risk: Low
Visibility: We should leave less trash lying around during tests.
Signed-off-by: John Admanski <jadmanski@google.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@2936 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/server/test.py
|
| 4395bbd96ed53aec5fad87d6c169a47dfdb8c9dd |
|
25-Mar-2009 |
mbligh <mbligh@592f7852-d20e-0410-864c-8624ca9c26a4> |
Added sysinfo support to log pre and post iteration (currently it logs
the contents of /proc/schedstat). Added client.common_lib.test hooks to
call pre and post iteration. Used the hooks in client.bin.test.runtest()
for client tests. Refactored server.test and added wrappers for the
pre/post iteration logging and used them on the new pre/post iteration
hooks.
For each iteration there will be a
resultsdir/sysinfo/iteration.N/schedstat.after and schedstat.before.
If there are tests that override execute() and implement their own
iteration logic they need to be changed over to override run_once()
instead and take advantage of the default execute() that supports the
pre/post iteration hooks and other things.
Signed-off-by: Mihai Rusu <dizzy@google.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@2929 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/server/test.py
|
| e7693bae7cbaf18d5dd693620db4618f25f5d633 |
|
30-Jan-2009 |
mbligh <mbligh@592f7852-d20e-0410-864c-8624ca9c26a4> |
Cleanup.
Remove site-specific containers 'initialize' arg from host.create_host().
Remove site-specific containers code from client/bin/autotest_client.
Signed-off-by: Duane Sand <duanes@google.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@2712 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/server/test.py
|
| 9f7dd11823a7bfd1854e72f3ba2134a18f7eb6e6 |
|
17-Nov-2008 |
jadmanski <jadmanski@592f7852-d20e-0410-864c-8624ca9c26a4> |
Move the temporary sysinfo files from /tmp to /tmp/sysinfo. This makes the actual location more configurable (e.g. you can add a symlink to redirect it).
Risk: Medium
Visibility: server-side sysinfo collection happens in /tmp/sysinfo
Signed-off-by: John Admanski <jadmanski@google.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@2428 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/server/test.py
|
| 79a2ee19751173af33227bd4438e0bc7d2ced6e7 |
|
05-Nov-2008 |
mbligh <mbligh@592f7852-d20e-0410-864c-8624ca9c26a4> |
Create a verify test so that its possible to see the results of verify in TKO.
Signed-off-by: Jeremy Orlow <jorlow@google.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@2379 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/server/test.py
|
| c75e0acf5fa50407e9adfefd7300731abf08dbd0 |
|
29-Oct-2008 |
mbligh <mbligh@592f7852-d20e-0410-864c-8624ca9c26a4> |
The serverside sysinfo code should specify initialize=False since, 3 lines down, we explicitly do a lightweight install.
Signed-off-by: Jeremy Orlow <jorlow@google.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@2355 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/server/test.py
|
| 54f90af69daac8a781678f0ccd42d6728d5d81d1 |
|
10-Oct-2008 |
jadmanski <jadmanski@592f7852-d20e-0410-864c-8624ca9c26a4> |
Add server-side sysinfo collection code (for server tests). This
is implemented by doing a temporary lightweight (no tests or
deps) autotest install on the remote machine and then running a
small script to generate the sysinfo.
The code is somewhat ugly because of the nature of what it has
to do on the remote machine (it needs to run before the test,
save some state, and then run afterwards with the saved state).
I accomplish this by pickling off of the sysinfo object after
the pre-test run, and reloading it during the post-test run.
However, I don't see a cleaner solution; we can't depend on
anything we leave behind on the remote machine while the test
is running not getting smashed.
This only applies to single-machine jobs (or multi-machine jobs
that break down into single-machine jobs via job.parallel_simple).
For multi-machine jobs we'd need to come up with a new,
multi-machine way to log sysinfo; in my mind it's a completely
separate problem.
Risk: Medium
Visibility: Adds sysinfo collection to server-side tests.
Signed-off-by: John Admanski <jadmanski@google.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@2270 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/server/test.py
|
| c5ddfd1f71caef9ec0c84c53ef7db42fcdc33e1c |
|
04-Aug-2008 |
mbligh <mbligh@592f7852-d20e-0410-864c-8624ca9c26a4> |
I have attached the patch for the packaging system.
The documentation is available at : http://test.kernel.org/autotest/PackagingSystem
Signed-off-by: Ashwin Ganti <aganti@google.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@1953 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/server/test.py
|
| 0afbb6369aa5aa9a75ea67dd9e95ec4b21c0c181 |
|
06-Jun-2008 |
jadmanski <jadmanski@592f7852-d20e-0410-864c-8624ca9c26a4> |
Convert all python code to use four-space indents instead of eight-space tabs.
Signed-off-by: John Admanski <jadmanski@google.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@1658 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/server/test.py
|
| 313f12ceca6185ea4890fec8e66baf06fd5d6f40 |
|
16-May-2008 |
mbligh <mbligh@592f7852-d20e-0410-864c-8624ca9c26a4> |
Did some cleanup work on imports in order to remove any of the remaining "from blah import *" imports.
From: Travis Miller
git-svn-id: http://test.kernel.org/svn/autotest/trunk@1522 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/server/test.py
|
| ccb9e18237137e547fc0f815506710a8b1d94453 |
|
17-Apr-2008 |
mbligh <mbligh@592f7852-d20e-0410-864c-8624ca9c26a4> |
Convert all imports on the server to use absolute imports.
Signed-off-by: John Admanski <jadmanski@google.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@1452 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/server/test.py
|
| 4e61c4e6479dccb3f34dcd4922f1647a81b06c08 |
|
07-Apr-2008 |
mbligh <mbligh@592f7852-d20e-0410-864c-8624ca9c26a4> |
1. Modified the runtest() function in test.py to not fork off a separate client process for the test but instead call it directly. This was needed to catch the exceptions that were thrown in the tests (as it wasn't possible to do that if the tests are separate forked client processes)
2. Modified the run_test() in server_job.py to log the exception detail too when a test fails.
Testing : I tested the change by modifying sleeptest.py to simply raise a TestError and trigger a failure purposefully and see how the failure reason was logged into status.log
From: Ashwin Ganti <aganti@google.com>
Signed-off-by: John Admanski <jadmanski@google.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@1406 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/server/test.py
|
| 6e2ffec8a247d84271dc86a1551c3ad543475d0f |
|
05-Mar-2008 |
mbligh <mbligh@592f7852-d20e-0410-864c-8624ca9c26a4> |
Enhance the error message displayed when a server-side test fails.
The existing message just indicates that a runtest function failed, and
gives you the exit code. We can at least display the name of the
failed test in the error message.
Signed-off-by: John Admanski <jadmanski@google.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@1301 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/server/test.py
|
| ea397bbc85f1a3eda39c9f2ef4fc209b4ff336f4 |
|
02-Feb-2008 |
mbligh <mbligh@592f7852-d20e-0410-864c-8624ca9c26a4> |
Refactor the server and client side test classes into a the common lib
Big change here. Pull all of the common code in the server and client
versions of test into the common lib. This also requires pulling
chunks of the client and server utility functions into the common lib
as well.
Signed-off-by: John Admanski <jadmanski@google.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@1215 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/server/test.py
|
| dccabe3e918737bdb907b8d1fa60c2786ddda862 |
|
01-Feb-2008 |
mbligh <mbligh@592f7852-d20e-0410-864c-8624ca9c26a4> |
Add an assert_ method to the server-side version of test, like the one already
added to the client-side version.
Signed-off-by: John Admanski <jadmanski@google.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@1211 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/server/test.py
|
| ecf55f408768b6c55957c916f066d227eb727eff |
|
14-Jan-2008 |
mbligh <mbligh@592f7852-d20e-0410-864c-8624ca9c26a4> |
Pre-emptively check if a test has already been run with the same tag
and raise a more informative failure message, instead of just failing
with a "file already exists" error during a mkdir call.
Signed-off-by: John Admanski <jadmanski@google.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@1159 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/server/test.py
|
| f31b0c0060dd688c80be3bb97ffdfa193e3d924b |
|
29-Nov-2007 |
mbligh <mbligh@592f7852-d20e-0410-864c-8624ca9c26a4> |
Move error.py'>error.py'>error.py out of the client and server and into common_lib.
Signed-off-by: John Admanski <jadmanski@google.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@1003 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/server/test.py
|
| 29d65039cac088a8da67739070e988bbae416dce |
|
25-Oct-2007 |
mbligh <mbligh@592f7852-d20e-0410-864c-8624ca9c26a4> |
Added a cleanup method to the test class that is called in a finally
block after the execute method.
From: John Admanski <jadmanski@google.com>
Signed-off-by: Martin J. Bligh <mbligh@google.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@846 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/server/test.py
|
| 05269369a9bbfee9481ce8b03b88f7abce4bad7b |
|
16-Oct-2007 |
mbligh <mbligh@592f7852-d20e-0410-864c-8624ca9c26a4> |
Add support for tests on the server side
Signed-off-by: Martin J. Bligh <mbligh@google.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@807 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/server/test.py
|