| 767dced065c8918b5ff74c1347371a0f0f8d9c69 |
|
01-Feb-2015 |
Dan Shi <dshi@chromium.org> |
[autotest] Add a utility module to interact with LXC binaries.
Add a module (lxc.py) to interact with LXC binaries.
lxc_functional_test.py is a test script to test the module. It will
1. Set up base container in a tmp directory.
2. Create a test container from the base container.
3. Test site-packages and results directory can be mounted and shared between
host and test container.
4. Run autoserv in test mode.
Also add a utility function in client/common_lib/site_utils.py to get the value
of the given argument for the function. It's used in decorator to check function
parameters.
BUG=chromium:453621
CQ-DEPEND=CL:251140
TEST=unittest,
sudo python site_utils/lxc_functional_test.py
sudo python site_utils/lxc.py -s -p /tmp/container_123
sudo python site_utils/lxc.py -s -p /tmp/container_123 -f
sudo python site_utils/lxc.py -p /tmp/container_123 -f
Change-Id: Id7b259c4bc03977974af44d6d88420b220706589
Reviewed-on: https://chromium-review.googlesource.com/247271
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/utils/unittest_suite.py
|
| 8e9f9f10233ad3bdbfeffab7f7776af5b94d6c9b |
|
17-Feb-2015 |
Dan Shi <dshi@chromium.org> |
[autotest] Check the running env for unittest suite to skip tests require chroot
BUG=chromium:458615
TEST=run until/unittest_suite inside and out side chroot, make sure both pass.
Change-Id: Iee965a6cb8018d9c38abaed4da41090d40020a82
Reviewed-on: https://chromium-review.googlesource.com/250441
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/utils/unittest_suite.py
|
| 8f0c4a8011777ea7b815fea0b062ec22c03dd1a2 |
|
27-Dec-2014 |
Chris Masone <cmasone@chromium.org> |
Remove unused auth_server.py
I wrote this long ago to mock out Gaia on test images.
We now do this in a totally different way, and nothing uses it.
BUG=None
TEST=None
Change-Id: I8d7434f3e10b34aba4e677e1aa2436a5e2773bd7
Reviewed-on: https://chromium-review.googlesource.com/237740
Trybot-Ready: Chris Masone <cmasone@chromium.org>
Tested-by: Chris Masone <cmasone@chromium.org>
Reviewed-by: Aviv Keshet <akeshet@chromium.org>
Commit-Queue: Chris Masone <cmasone@chromium.org>
/external/autotest/utils/unittest_suite.py
|
| 784df0c730f522dc4de83fa81c0f6fe211247673 |
|
26-Nov-2014 |
Dan Shi <dshi@chromium.org> |
[autotest] Add atest command to interact with server database
This CL add following actions to atest command to make chances to server
database.
atest server list [--summary] [--role role_name] [--status status]
Show servers with optinal role and status.
atest server create hostname --role role_name
Create a server with given role, with status backup.
atest server delete hostname
Delete a server from the database.
atest server modify hostname --role role_name --status status --note note \
--delete --attribute attr_name --value value
Modify a server's role, status, note, or attribute:
1. Add role to a server. If the server is in primary status, proper actions
like service restart will be executed to enable the role (in a later CL).
2. Delete a role from a server. If the server is in primary status, proper
actions like service restart will be executed to disable the role (in a
later CL).
3. Change status of a server. If the server is changed from or to primary
status, proper actions like service restart will be executed to enable
or disable each role of the server (in a lter CL).
4. Change note of a server. Note is a field you can add description about
the server.
5. Change/delete attribute of a server. Attribute can be used to store
information about a server. For example, the max_processes count for a
drone.
BUG=chromium:424778
CQ-DEPEND=CL:231671
TEST=unittest and atest commands in local setup:
atest server create hostname --role drone
atest server delete hostname
atest server modify hostname --role drone
atest server modify hostname --status primary
atest server modify hostname --role devserver
atest server modify hostname --role drone --delete
atest server modify hostname --attribute max_processes --value 200
atest server modify hostname --attribute max_processes --delete
Change-Id: Ie8f7f651b3e5be53bf078b963d50f37dd067503f
Reviewed-on: https://chromium-review.googlesource.com/232003
Reviewed-by: Dan Shi <dshi@chromium.org>
Commit-Queue: Dan Shi <dshi@chromium.org>
Tested-by: Dan Shi <dshi@chromium.org>
/external/autotest/utils/unittest_suite.py
|
| 22dd226625255110c079e979113dcda1f4fa5ea8 |
|
29-Nov-2014 |
Prashanth Balasubramanian <beeps@google.com> |
[autotest] Shard client resyncs conflicting jobs.
There is currently a race in the shard_client, described thus:
* scheduler marks job 1 complete
* shard heartbeat doesn't include job 1 in packet
* scheduler marks job 1 with shard_id = NULL (for upload)
* master replies with 'Hey job 1 is Queued but you say it
isn't running'
* shard serializes the fks of job1 sent by master, over
writing the NULL shard_id
=> Job1 is never synced back to the master
This cl fixes this race by:
1. The shard client continues to declare a job as incomplete till
the scheduler has update the shard_id to NULL. In the above
example, the second step won't happen.
2. If the shard_client notices any disagreement between the complete
bits of jobs in the local db and the 'new' jobs sent from the
master, it re-marks the job for upload by setting shard_id=NULL.
In the above example this would happen after the last step,
forcing the next heartbeat to pick up the job.
The cl also adds some important stats and logging to help debug
issues in production.
TEST=Ran suites via puppylab, unittests.
BUG=chromium:423225,chromium:425347
DEPLOY=scheduler
Change-Id: Ib35b193681b187e3745a4678778dbeba77fe83e5
Reviewed-on: https://chromium-review.googlesource.com/232193
Tested-by: Prashanth B <beeps@chromium.org>
Reviewed-by: Fang Deng <fdeng@chromium.org>
Commit-Queue: Prashanth B <beeps@chromium.org>
/external/autotest/utils/unittest_suite.py
|
| 8a764d1fb6cd99d08cda6400bd35162fa3ac5fe0 |
|
15-Oct-2014 |
Jakob Juelich <jakobjuelich@chromium.org> |
[autotest] Use global database for tko models in django v3.
This adds the global database to django.
A django database router is added to determine to which database
should be used for which models. All tko models are always taken or
written from or into the global database while all other objects
remain unchanged.
BUG=chromium:422637
TEST=Ran suites, syncdb, restart apache, ran a suite.
Confirm global database connection is closed after each attempt to get
test view: https://x20web.corp.google.com/~beeps/log/db_routers.html
Change-Id: Idf6933d1d112bbc5a2896fa61afd03f6604dafb5
Reviewed-on: https://chromium-review.googlesource.com/223501
Tested-by: Dan Shi <dshi@chromium.org>
Reviewed-by: Prashanth B <beeps@chromium.org>
Commit-Queue: Dan Shi <dshi@chromium.org>
/external/autotest/utils/unittest_suite.py
|
| d456bf0c5823b0f6832dc2e3e0e13ea7acf1b2ad |
|
15-Nov-2014 |
Prathmesh Prabhu <pprabhu@chromium.org> |
unittest_suite: Add exception for mbim_compliance modules.
There are two modules in client/cros/cellular/mbim_compliance that are named
'*_test.py' but aren't really tests. These modules are in the process of going
away. Add temporary exception to not treat them as tests to ease the process of
their removal.
BUG=chromium:432621
TEST=`./utils/unittest_suite.py -r client/cros/cellular/mbim_compliance` passes.
Change-Id: Ib25758a32a64f5845d253a677d32706f5f3424bd
Reviewed-on: https://chromium-review.googlesource.com/229960
Reviewed-by: Simran Basi <sbasi@chromium.org>
Reviewed-by: Prathmesh Prabhu <pprabhu@chromium.org>
Commit-Queue: Prathmesh Prabhu <pprabhu@chromium.org>
Tested-by: Prathmesh Prabhu <pprabhu@chromium.org>
/external/autotest/utils/unittest_suite.py
|
| ab583045d1e3e21da15eeb5152c2f808f4aea8ff |
|
11-Aug-2014 |
Nathan Stoddard <nstoddard@chromium.org> |
Add basic Chrome Web Store tests.
These tests include: a basic sanity test, 5 tests that verify that free
items can be installed, and 3 tests that verify that free trial items
can be installed.
BUG=chromium:403498
TEST=These tests pass
Change-Id: Id7aa76b4e23e5059652dbdb84f5976dcd2b0a3f5
Reviewed-on: https://chromium-review.googlesource.com/211835
Reviewed-by: Dan Shi <dshi@chromium.org>
Tested-by: Nathan Stoddard <nstoddard@chromium.org>
Commit-Queue: Dan Shi <dshi@chromium.org>
/external/autotest/utils/unittest_suite.py
|
| 36accc6a2a572e9d502407b34701f535a169f524 |
|
23-Jul-2014 |
Jakob Jülich <jakobjuelich@google.com> |
[autotest] Fixing and re-enabling monitor_db_functional_test.
The test was disabled and outdated. Database access and mocking of the drone
manager changed. This fixes these issues, updates the unit tests to the
current status and reanables them.
BUG=chromium:395756
DEPLOY=scheduler
TEST=ran ./utils/unittest_suite.py
Change-Id: I6a3eda5ddfaf07f06d6b403692b004b22939ffb6
Reviewed-on: https://chromium-review.googlesource.com/209567
Reviewed-by: Alex Miller <milleral@chromium.org>
Tested-by: Jakob Jülich <jakobjuelich@google.com>
Commit-Queue: Jakob Jülich <jakobjuelich@google.com>
/external/autotest/utils/unittest_suite.py
|
| 27054ab75824a1a3c085f1d6b428b523497e95e6 |
|
10-Jul-2014 |
Prathmesh Prabhu <pprabhu@chromium.org> |
Revert "mbim_compliance: Temporarily add unittest exception."
The pyusb dependency was added to chromeos-base/autotest-tests-cellular by CL:203677.
Additionally, this test no longer depends on 'extra' fields that did not exist in upstream pyusb.
This reverts commit 008f1336f9b59055071da03da8a4cb4551188a12.
BUG=chromium:384345
TEST=uniitest_suite.py passes locally.
Change-Id: Icd7ae4b32838301b1ffdf30cd4a954c6b6f599d9
Reviewed-on: https://chromium-review.googlesource.com/207353
Reviewed-by: Dan Shi <dshi@chromium.org>
Commit-Queue: Prathmesh Prabhu <pprabhu@chromium.org>
Tested-by: Prathmesh Prabhu <pprabhu@chromium.org>
/external/autotest/utils/unittest_suite.py
|
| 008f1336f9b59055071da03da8a4cb4551188a12 |
|
13-Jun-2014 |
Prathmesh Prabhu <pprabhu@chromium.org> |
mbim_compliance: Temporarily add unittest exception.
uniitest_suite picks up the tests under test/ as unittest.
This CL temporarily blacklists them because there is a broken dependency in
these files that is hard to fix, and is going away in the next couple days.
BUG=chromium:384345
TEST=utils/unittest_suite.py
Change-Id: I1aaf6fd8f9ac309771db426b5416744c1e9dd516
Reviewed-on: https://chromium-review.googlesource.com/203713
Tested-by: Prathmesh Prabhu <pprabhu@chromium.org>
Reviewed-by: Dan Shi <dshi@chromium.org>
Commit-Queue: Prathmesh Prabhu <pprabhu@chromium.org>
/external/autotest/utils/unittest_suite.py
|
| 4ec9867f46deb969c154bebf2e64729d56c3a1d3 |
|
15-May-2014 |
Prashanth B <beeps@google.com> |
[autotest] Split host acquisition and job scheduling II.
This cl creates a stand-alone service capable of acquiring hosts for
new jobs. The host scheduler will be responsible for assigning a host to
a job and scheduling its first special tasks (to reset and provision the host).
There on after, the special tasks will either change the state of a host or
schedule more tasks against it (eg: repair), till the host is ready to
run the job associated with the Host Queue Entry to which it was
assigned. The job scheduler (monitor_db) will only run jobs, including the
special tasks created by the host scheduler.
Note that the host scheduler won't go live till we flip the
inline_host_acquisition flag in the shadow config, and restart both
services. The host scheduler is dead, long live the host scheduler.
TEST=Ran the schedulers, created suites. Unittests.
BUG=chromium:344613, chromium:366141, chromium:343945, chromium:343937
CQ-DEPEND=CL:199383
DEPLOY=scheduler, host-scheduler
Change-Id: I59a1e0f0d59f369e00750abec627b772e0419e06
Reviewed-on: https://chromium-review.googlesource.com/200029
Reviewed-by: Prashanth B <beeps@chromium.org>
Tested-by: Prashanth B <beeps@chromium.org>
Commit-Queue: Prashanth B <beeps@chromium.org>
/external/autotest/utils/unittest_suite.py
|
| f66d51b5caa96995b91e7c155ff4378cdef4baaf |
|
06-May-2014 |
Prashanth B <beeps@google.com> |
[autotest] Split host acquisition and job scheduling.
This is phase one of two in the plan to split host acquisition out of the
scheduler's tick. The idea is to have the host scheduler use a job query
manager to query the database for new jobs without hosts and assign
hosts to them, while the main scheduler uses the same query managers to
look for hostless jobs.
Currently the main scheduler uses the class to acquire hosts inline,
like it always has, and will continue to do so till the
inline_host_acquisition feature flag is turned on via the shadow_config.
TEST=Ran the scheduler, suites, unittets.
BUG=chromium:344613
DEPLOY=Scheduler
Change-Id: I542e4d1e509c16cac7354810416ee18ac940a7cf
Reviewed-on: https://chromium-review.googlesource.com/199383
Reviewed-by: Prashanth B <beeps@chromium.org>
Commit-Queue: Prashanth B <beeps@chromium.org>
Tested-by: Prashanth B <beeps@chromium.org>
/external/autotest/utils/unittest_suite.py
|
| 0e960285b022fad77f0b087a2007867363bf6ab9 |
|
14-May-2014 |
Prashanth B <beeps@google.com> |
[autotest] Consolidate methods required to setup a scheduler.
Move methods/classes that will be helpful in setting up another scheduler
process into scheduler_lib:
1. Make a connection manager capable of managing connections.
Create, access, close the database connection through this manager.
2. Cleanup setup_logging so it's usable by multiple schedulers if they
just change the name of the logfile.
TEST=Ran suites, unittests.
BUG=chromium:344613
DEPLOY=Scheduler
Change-Id: Id0031df96948d386416ce7cfc754f80456930b95
Reviewed-on: https://chromium-review.googlesource.com/199957
Reviewed-by: Prashanth B <beeps@chromium.org>
Tested-by: Prashanth B <beeps@chromium.org>
Commit-Queue: Prashanth B <beeps@chromium.org>
/external/autotest/utils/unittest_suite.py
|
| 86934c86a72509c6aede78591817edcedbddc268 |
|
09-May-2014 |
Prashanth B <beeps@google.com> |
[autotest] Calculate database cache staleness.
TEST=Unittests, calculated staleness.
BUG=None
DEPLOY=Scheduler
Change-Id: I82084c1d412a0a9bbda911159a156c5436e5e6c6
Reviewed-on: https://chromium-review.googlesource.com/199114
Commit-Queue: Prashanth B <beeps@chromium.org>
Tested-by: Prashanth B <beeps@chromium.org>
Reviewed-by: Dan Shi <dshi@chromium.org>
/external/autotest/utils/unittest_suite.py
|
| b474fdfd353cdb0888191f4b80e47e6b5343d891 |
|
04-Apr-2014 |
Prashanth B <beeps@google.com> |
[autotest] Lease hosts according to frontend job priorities.
This cl modifies the way we lease hosts by teaching the
RDBServerHostWrapper to handle host leasing. Though this involves
a seperate query for each host it leads to a design we can later
build atomicity into, because we can check the leased bit on a single
host before setting it. This model of leasing also has the following benefits:
1. It doesn't abuse the response map.
2. It gives us more clarity into which reqeusts are acquiring
hosts by setting the leased bit in step with host validation.
3. It is more tolerant to db errors because exceptions raised while
leasing one host will not fail the entire batched request.
This cl also adds an rdb_unittest module.
TEST=Unittests, ran suites.
BUG=chromium:353183
DEPLOY=scheduler
Change-Id: I35c04bcb37eee0191a211c133a35824cc78b5d71
Reviewed-on: https://chromium-review.googlesource.com/193182
Reviewed-by: Prashanth B <beeps@chromium.org>
Commit-Queue: Prashanth B <beeps@chromium.org>
Tested-by: Prashanth B <beeps@chromium.org>
/external/autotest/utils/unittest_suite.py
|
| 489b91d72cd225e902081dbd3f9e47448fe867f6 |
|
15-Mar-2014 |
Prashanth B <beeps@google.com> |
[autotest] Establish a common interface for host representation.
This cl has the work needed to ensure that schema changes made on
the server trickled down into the client. If the same changes don't
reflect on the client, creating or saving a client host wrapper for
a given host will fail deterministically on the client side until
modules using the rdb_host are modified to reflect the changes.
1. rdb_hosts: A module containing the host heirarchy needed to
establish a dependence between the creation of the RDBServerHostWrapper
(which is serialized and returned to the client, which converts it
into an RDBClientHostWrapper) and the saving of the RDBClientHostWrapper
through and rdb update request.
2. rdb_requests: Contains the requests/request managers that were in
rdb_utils, because I plan to expand them in subsequent cls.
3. rdb_model_extensions: Contains model classes common
to both server and client that help in establishing
the common host model interface.
4. rdb integration tests.
TEST=Ran suites, unittests
BUG=chromium: 348176
DEPLOY=scheduler
Change-Id: I0bbab1dd184e505b1130ee73714e45ceb7bf4189
Reviewed-on: https://chromium-review.googlesource.com/191357
Commit-Queue: Prashanth B <beeps@chromium.org>
Tested-by: Prashanth B <beeps@chromium.org>
Reviewed-by: Dan Shi <dshi@chromium.org>
/external/autotest/utils/unittest_suite.py
|
| 7d8273bad1318c13698a162a6e5910bea060d167 |
|
06-Nov-2013 |
beeps <beeps@chromium.org> |
[autotest] RDB refactor I
Initial refactor for the rdb, implementes 1 in this schematic:
https://x20web.corp.google.com/~beeps/rdb_v1_midway.jpg
Also achieves the following:
- Don't process an hqe more than once, after having assigned a host to it.
- Don't assign a host to a queued, aborted hqe.
- Drop the metahost concept.
- Stop using labelmetahostscheduler to find hosts for non-metahost jobs.
- Include a database migration script for jobs that were still queued during
the scheduler restart, since they will now need a meta_host dependency.
This cl also doesn't support the schedulers ability to:
- Schedule an atomic group
* Consequently, also the ability to block a host even when the hqe using it is
no longer active.
- Schedule a metahost differently from a non-metahost
* Both metahosts and non-metahosts are just labels now
* Jobs which are already assigned hosts are still give precedence, though
- Schedule based on only_if_needed.
And fixes the unittests appropriately.
TEST=Ran suites, unittests. Restarted scheduler after applying these changes
and tested migration. Ran suite scheduler.
BUG=chromium:314082,chromium:314219,chromium:313680,chromium:315824,chromium:312333
DEPLOY=scheduler, migrate
Change-Id: I70c3c3c740e51581db88fe3ce5879c53d6e6511e
Reviewed-on: https://chromium-review.googlesource.com/175957
Reviewed-by: Alex Miller <milleral@chromium.org>
Commit-Queue: Prashanth B <beeps@chromium.org>
Tested-by: Prashanth B <beeps@chromium.org>
/external/autotest/utils/unittest_suite.py
|
| 0ddb541793e93c46f597c47b18a80f517ea1982d |
|
19-Nov-2013 |
Prathmesh Prabhu <pprabhu@chromium.org> |
Revert "Temporarily turn-off unittests in wardmodem till all CLs are in."
This reverts commit 97e5d26e7853d78d45b7bea77f2262ba70a8c834.
BUG=chromium:302840
TEST=Run unittest_suite.py, ensure wardmodem tests are run and pass.
Change-Id: Iac7b9edcc6fa0757cbd3eaaf77830295d1eeefc7
Reviewed-on: https://chromium-review.googlesource.com/177278
Tested-by: Prathmesh Prabhu <pprabhu@chromium.org>
Reviewed-by: Thieu Le <thieule@chromium.org>
Commit-Queue: Prathmesh Prabhu <pprabhu@chromium.org>
/external/autotest/utils/unittest_suite.py
|
| 97e5d26e7853d78d45b7bea77f2262ba70a8c834 |
|
02-Oct-2013 |
Prathmesh Prabhu <pprabhu@chromium.org> |
Temporarily turn-off unittests in wardmodem till all CLs are in.
There are a bunch of wardmodem CLs that are ready to be merged. Turning off the
unit-tests as they go in will simplify the process.
Wardmodem is not used by any tests right now.
This CL will be reverted once these CLs are in.
BUG=chromium:302840
TEST=Run unittest_suite.py, ensure new tests from wardmodem are not run.
Change-Id: Ib951428781880044f9fb0935764fcbf1b7b5f76f
Reviewed-on: https://chromium-review.googlesource.com/171500
Reviewed-by: Arman Uguray <armansito@chromium.org>
Reviewed-by: Aviv Keshet <akeshet@chromium.org>
Commit-Queue: Prathmesh Prabhu <pprabhu@chromium.org>
Tested-by: Prathmesh Prabhu <pprabhu@chromium.org>
/external/autotest/utils/unittest_suite.py
|
| 36f4c1edb43cb273e4327ad77ba69787179f20f2 |
|
12-Aug-2013 |
Keyar Hood <keyar@chromium.org> |
Autotest: Bug reporting unit tests now pass.
BUG=chromium:249377
TEST=Ran autotests.
Change-Id: I7020d1447d2ee19935f90a6b4418ff8971e45c79
Reviewed-on: https://gerrit.chromium.org/gerrit/65592
Reviewed-by: Prashanth Balasubramanian <beeps@chromium.org>
Commit-Queue: Keyar Hood <keyar@chromium.org>
Tested-by: Keyar Hood <keyar@chromium.org>
/external/autotest/utils/unittest_suite.py
|
| 6e161a728b733068efd7dab561ba92ebaf5e243a |
|
27-Jun-2013 |
Aviv Keshet <akeshet@chromium.org> |
[autotest] fix 2 remaining unit tests that fail on builder
1) common_util_test has a test that assumes the USER environment
variable is set. However, this envvar is in fact NOT set in the builder
environment. The test has been modified to catch the resulting KeyError
and skip the test.
2) full_release_test fails on the builder due to an exception in
importing the dev_server module. For now I'm adding this test to the
SKIP_TEST list, and filing a bug to get that import logic sorted out.
BUG=chromium:221254
TEST=ran a tryjob, tests passed on builder.
Change-Id: Id0d3369e6529479235388e5dde8f78af9ea9d545
Reviewed-on: https://gerrit.chromium.org/gerrit/60163
Tested-by: Aviv Keshet <akeshet@chromium.org>
Reviewed-by: Alex Miller <milleral@chromium.org>
Commit-Queue: Aviv Keshet <akeshet@chromium.org>
/external/autotest/utils/unittest_suite.py
|
| af04857a63c7d789713aca41d3bc467adbddf9f1 |
|
25-Jun-2013 |
Prathmesh Prabhu <pprabhu@chromium.org> |
Exclude wardmodem/task_loop_unittest.py from unittest_suite
These unittests currently take around 30s because they involve dispatching
events from an asynchronous event loop. Speeding up this particular unittest
module will likely not happen in the near future, so exclude them from scheduled
tests.
BUG=chromium:254030
TEST=From autotest/files/ run /utils/unittest_suite.py and verify that
wardmodem.task_loop_unittest.py is not run.
Change-Id: If314ed58dcc487b3ed52af6d37b1856771a32487
Reviewed-on: https://gerrit.chromium.org/gerrit/59948
Reviewed-by: Aviv Keshet <akeshet@chromium.org>
Commit-Queue: Prathmesh Prabhu <pprabhu@chromium.org>
Tested-by: Prathmesh Prabhu <pprabhu@chromium.org>
/external/autotest/utils/unittest_suite.py
|
| c0fdfc5ae1af77160bce948a49dacd58eff400c8 |
|
18-Jun-2013 |
Aviv Keshet <akeshet@chromium.org> |
[autotest] blacklist dev_server_test
BUG=chromium:251395
TEST=Run utils/unittest_suite.py inside chroot. Does not hang on a
dev_server_test unittest waiting for a password. (A bunch of tests fail
inside of the chroot still, but that is a separate issue).
Change-Id: Id4a908d13d6f6549afce401bbb27bcda29793888
Reviewed-on: https://gerrit.chromium.org/gerrit/59097
Commit-Queue: Aviv Keshet <akeshet@chromium.org>
Reviewed-by: Aviv Keshet <akeshet@chromium.org>
Tested-by: Aviv Keshet <akeshet@chromium.org>
/external/autotest/utils/unittest_suite.py
|
| cc8956fe15712581bffe0b883f619e8f0ff82207 |
|
18-Jun-2013 |
Tan Gao <tgao@chromium.org> |
Update Selenium dependency for chaos_base_test_unittest.py
BUG=chromium:251297
TEST=Manual (run unit test and verified passing; also manually inspected
imports to verify no selenium is present in the chain)
Change-Id: Ib14e8d4854a3e7246a300c853d32c3ac8fecd10f
Reviewed-on: https://gerrit.chromium.org/gerrit/59078
Reviewed-by: Aviv Keshet <akeshet@chromium.org>
Commit-Queue: Tan Gao <tgao@chromium.org>
Tested-by: Tan Gao <tgao@chromium.org>
/external/autotest/utils/unittest_suite.py
|
| 78f446d878e81dd92af4b642f5c9d86b649e17c2 |
|
18-Jun-2013 |
Aviv Keshet <akeshet@chromium.org> |
Revert "Remove Selenium dependency from 3 unit tests."
This reverts commit 17d4efd68621bddee3c07e3b14e01275f940ed93
Change-Id: I9dbadf50c3098aec0e2964de849bc5ab104d7cbb
Reviewed-on: https://gerrit.chromium.org/gerrit/59074
Tested-by: Aviv Keshet <akeshet@chromium.org>
Reviewed-by: Alex Miller <milleral@chromium.org>
Commit-Queue: Aviv Keshet <akeshet@chromium.org>
/external/autotest/utils/unittest_suite.py
|
| 17d4efd68621bddee3c07e3b14e01275f940ed93 |
|
17-Jun-2013 |
Tan Gao <tgao@chromium.org> |
Remove Selenium dependency from 3 unit tests.
- this CL reverts https://gerrit.chromium.org/gerrit/#/c/50888/3
[I've refactored the code to remove Selenium dependency]
BUG=chromium:239255
TEST=Manual (run all 3 unit tests and verified passing w/o selenium)
Change-Id: Iad001ab8f433ade66d0853df68a84d35d6d75900
Reviewed-on: https://gerrit.chromium.org/gerrit/58881
Tested-by: Tan Gao <tgao@chromium.org>
Reviewed-by: Aviv Keshet <akeshet@chromium.org>
Commit-Queue: Tan Gao <tgao@chromium.org>
/external/autotest/utils/unittest_suite.py
|
| d79585434f956f418629c939dfdd042b2a3beb42 |
|
13-Jun-2013 |
beeps <beeps@chromium.org> |
[autotest] Disable reporting_unittest.
Having moved over the new project hosting api we need to rewrite
the reporters unittests. To reduce code churn I'd rather we wait
till the first week before checking in a 'fixed' version, as I
expect most of the minor reporting module tweaks and changes to
happen by then.
BUG=chromium:249377
TEST=Ran the unittest_suite with and without reporting_unittest
black listed and made sure it didn't run in the former case.
Change-Id: I9aa669f0dbd06f7dbe5dfd8fe8582efd14088bbe
Reviewed-on: https://gerrit.chromium.org/gerrit/58549
Tested-by: Prashanth Balasubramanian <beeps@chromium.org>
Reviewed-by: Aviv Keshet <akeshet@chromium.org>
Commit-Queue: Prashanth Balasubramanian <beeps@chromium.org>
/external/autotest/utils/unittest_suite.py
|
| 1f23b6918dd601f469eea2975f3e8dbda6659b58 |
|
14-May-2013 |
Aviv Keshet <akeshet@chromium.org> |
[autotest] reenable django or simplejson requiring unit tests
For a refactor of control_type, a lot of the relevant unit test coverage
is currently blacklisted in utils/unittest_suite.py due to requiring
Django or simplejson.
This CL un-blacklists those tests. It also therefore
fixes a few tests which are failing or broken. In particular:
tko/rpc_interface_unittest was throwing
`DatabaseError: only a single result allowed for a SELECT that is
part of an expression` all over the place. I couldn't blacklist just
this test file, since it has the same filename as
afe/rpc_interface_unittest.py which we do not want to blacklist and with
the way blacklists work in utils/unittest_suite I couldn't blacklist
just one of them. Instead, I have renamed the broken test file to
rpc_interface_unittest_fixme.py. tko/resources_test imports this failing
module, so I had to rename that one too.
One test in resources_test was throwing the same excepiion as above, so
I commented it out. (test_keyval_filtering)
in monitor_db_unittest, the test
test_HostScheduler_get_host_atomic_group_id throws KeyErrors that seem
to be related to labels not being correctly set up or committed to the
test database in the test setup phase. After trying to blindly track
this down a bit, I realized I was in over my head and just commented out
this specific test).
monitor_db_functional_test was throwing
`DatabaseError: near "TRUNCATE": syntax error` all over the place, so I
blacklisted that test file in utils/unittest_suite.py
BUG=chromium:240643
TEST=utils/unittest_suite.py # All tests pass
Change-Id: I8fdbe048b04516548e96bd888ed74e9fc82a2d88
Reviewed-on: https://gerrit.chromium.org/gerrit/51190
Commit-Queue: Aviv Keshet <akeshet@chromium.org>
Reviewed-by: Aviv Keshet <akeshet@chromium.org>
Tested-by: Aviv Keshet <akeshet@chromium.org>
/external/autotest/utils/unittest_suite.py
|
| 3c5a1f880c5320ca688bee187efe50ce74475b08 |
|
10-May-2013 |
Aviv Keshet <akeshet@chromium.org> |
[autotest] blacklist 2 files from unittest_suite.py
CL adds 2 tests to utils/unittest_suite.py blacklist so that they are no
longer run as unit tests.
BUG=chromium:239255
TEST=Run utils/unittest_suite.py. chaos_base_test and chaos_interop_test
no longer show up as failing.
Change-Id: Ifef1b460dc48b6fb0094a37a4afb34a68619eeb6
Reviewed-on: https://gerrit.chromium.org/gerrit/50874
Commit-Queue: Aviv Keshet <akeshet@chromium.org>
Tested-by: Aviv Keshet <akeshet@chromium.org>
Reviewed-by: Tan Gao <tgao@chromium.org>
/external/autotest/utils/unittest_suite.py
|
| 2f6524a61cb60658c12bdb7f62961d018281ddee |
|
10-May-2013 |
Aviv Keshet <akeshet@chromium.org> |
[autotest] Blacklist unit tests that require selenium
CL adds a new class of skipped tests to utils/unittest_suite.py
BUG=chromium:239255
TEST=utils/unittest_suite.py no longer fails the following tests:
'ap_configurator_factory_unittest.py',
'chaos_base_test_unittest.py',
'ap_batch_locker_unittest.py'
Change-Id: I1a4810669caf436d4b820fd2a88ec5ca3db634e1
Reviewed-on: https://gerrit.chromium.org/gerrit/50888
Commit-Queue: Aviv Keshet <akeshet@chromium.org>
Tested-by: Aviv Keshet <akeshet@chromium.org>
Reviewed-by: Tan Gao <tgao@chromium.org>
/external/autotest/utils/unittest_suite.py
|
| 8af6fbe5ef7217011d06617eb4247b450a377d01 |
|
13-Feb-2013 |
Dan Shi <dshi@chromium.org> |
[autotest] support file path in blacklist in unittest_suite.py
Code is changed to check if a file is in the blacklist with both
file name and path. For example, 'mirror/trigger_unittest.py' in
REQUIRES_AUTH set will skip the unittest in mirror folder but not
the one in any other folder, while 'trigger_unittest.py' will skip
any test with that file name in any folder.
BUG=chromium-os:28739
TEST=run unittest_suite.py locally to verify files in blacklist
are skipped.
Change-Id: I3f5ab5fab83785f9d55241661d37919390753ed0
Reviewed-on: https://gerrit.chromium.org/gerrit/43218
Tested-by: Dan Shi <dshi@chromium.org>
Reviewed-by: Alex Miller <milleral@chromium.org>
Commit-Queue: Dan Shi <dshi@chromium.org>
/external/autotest/utils/unittest_suite.py
|
| 13b83c5453670727eac8853c0450838ebe74ef59 |
|
15-Feb-2013 |
Alex Miller <milleral@chromium.org> |
[autotest] Fix auth_server_unittest.py
It failed because it was trying to open a port <1024 as non-root.
Setting the HTTP port now makes it pass (but also spit out lots of error
messages?).
TEST=ran it
BUG=chromium-os:37989
Change-Id: Id13e5037868a013bc7a0878b9021d84b4225db42
Reviewed-on: https://gerrit.chromium.org/gerrit/43399
Commit-Queue: Alex Miller <milleral@chromium.org>
Reviewed-by: Alex Miller <milleral@chromium.org>
Tested-by: Alex Miller <milleral@chromium.org>
/external/autotest/utils/unittest_suite.py
|
| 78b0595e3841a41aae3c0ce20178629c42c1e3b3 |
|
13-Feb-2013 |
Aviv Keshet <akeshet@chromium.org> |
[autotest] Fix unittest -- blacklist ap_configurator_test.py
ap_configurator_test depends on having selenium installed, which would
mean requiring everyone who develops on autotest to have selenium
installed. This seems excessive. Blacklisting the test from running as
part of unittest_suite.py.
BUG=chromium-os:37989
TEST=Unit test no longer runs as part of utils/unittest_suite.py
Change-Id: I07a7029dbb3b9c65fb57d30113d0fbc6826545d4
Reviewed-on: https://gerrit.chromium.org/gerrit/43220
Reviewed-by: Dan Shi <dshi@chromium.org>
Reviewed-by: Kris Rambish <krisr@chromium.org>
Commit-Queue: Aviv Keshet <akeshet@chromium.org>
Reviewed-by: Aviv Keshet <akeshet@chromium.org>
Tested-by: Aviv Keshet <akeshet@chromium.org>
/external/autotest/utils/unittest_suite.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/utils/unittest_suite.py
|
| 34a0f3bea5490e2914536481f339794e8a3b0a88 |
|
08-Jun-2010 |
jamesren <jamesren@592f7852-d20e-0410-864c-8624ca9c26a4> |
Add job_serializer_unittest to long tests
Signed-off-by: James Ren <jamesren@google.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@4586 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/utils/unittest_suite.py
|
| 999fb13dcbf4de5e37ca2b3059ef1061b5faba43 |
|
23-Apr-2010 |
mbligh <mbligh@592f7852-d20e-0410-864c-8624ca9c26a4> |
barrier cleanups:
* renames barrier.py to base_barrier.py and adds a barrier.py
stub to import from base_barrier and override with site_barrier
if found. barrier_unittest.py is renamed to match.
* Move BarrierAbortError to the error module with everything else.
* Add a rendezvous_servers abort=True from the server test case.
* Moved get_sync_control_file() from common_lib.utils to
server.base_utils where it belongs to avoid a circular
import of utils importing barrier.
Signed-off-by: Gregory Smith <gps@google.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@4444 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/utils/unittest_suite.py
|
| cd7a81a58c7a1a16105dcd9dca5e9f1680eff65b |
|
21-Apr-2010 |
jamesren <jamesren@592f7852-d20e-0410-864c-8624ca9c26a4> |
Various changes to support further high-level automation efforts.
* added a RESTful interface for TKO. right now there's only a single, simple resource for accessing test attributes.
* extended the REST server library in a few ways, most notably to support
* querying on keyvals, with something like ?has_keyval=mykey=myvalue&...
* operators, delimited by a colon, like ?hostname:in=host1,host2,host3
* loading relationships over many items efficiently (see InstanceEntry.prepare_for_full_representation()). this is used to fill in keyvals when requesting a job listing, but it can (and should) be used in other places, such as listing labels for a host collection.
* loading a collection with inlined full representations, by passing full_representations=true
* added various features to the AFE RESTful interface as necessary.
* various fixes to the rest_client library, most notably
* changed HTTP client in rest_client.py to use DI rather than singleton, easing testability. the same should be done for _get_request_headers(), to be honest.
* better support for query params, including accepting a MultiValueDict and supporting URIs that already have query args
* basic support for redirects
* builtin support for requesting a full collection (get_full()), when clients explicitly expect the result not to be paged. i'm still considering alternative approaches to this -- it may make sense to have something like this be the default, and have clients set a default page size limit rather than passing it every time.
* minor change to mock.py to provide better debugging output.
Signed-off-by: Steve Howard <showard@google.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@4438 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/utils/unittest_suite.py
|
| 37dfa9dea1a38d42485ddcb00535444b9fc9fef9 |
|
12-Apr-2010 |
jamesren <jamesren@592f7852-d20e-0410-864c-8624ca9c26a4> |
Missed a comma in a tuple. Added category for REQUIRES_HTTPLIB2. Added
a test to REQUIRES_MYSQLDB.
Signed-off-by: James Ren <jamesren@google.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@4404 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/utils/unittest_suite.py
|
| 1468135de4b2e86844c360deeb7579328aa33331 |
|
09-Apr-2010 |
jamesren <jamesren@592f7852-d20e-0410-864c-8624ca9c26a4> |
Add site_rpc_utils_unittest and execution_engine_unittest to LONG_TESTS
Signed-off-by: James Ren <jamesren@google.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@4394 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/utils/unittest_suite.py
|
| 6461fff8f5edf5be1b5bb9bba07ef8b150d36e7d |
|
07-Apr-2010 |
jamesren <jamesren@592f7852-d20e-0410-864c-8624ca9c26a4> |
Create a new unittest set for REQUIRES_AUTH and move tests into LONG_TESTS that require auth.
Signed-off-by: Scott Zawalski <scottz@google.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@4375 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/utils/unittest_suite.py
|
| 12c9fddebefb25a11802a942eed6c071d7c8a205 |
|
02-Mar-2010 |
jamesren <jamesren@592f7852-d20e-0410-864c-8624ca9c26a4> |
Missed ".py" when flagging client_compilation_unittest.py as a long test
Signed-off-by: James Ren <jamesren@google.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@4277 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/utils/unittest_suite.py
|
| 92c185903cf2eb1fd2289f0206b291aded7b41f8 |
|
25-Feb-2010 |
jamesren <jamesren@592f7852-d20e-0410-864c-8624ca9c26a4> |
Split long unit tests into different sets by their dependencies.
Add database.db_utils_unittest to long tests; requires MySQLdb.
Add rpc_utils_unittest.py to long tests: requires Django.
Signed-off-by: James Ren <jamesren@google.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@4271 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/utils/unittest_suite.py
|
| 31ef6ff086037d74e6dc6ce29643e9d0f7281ee1 |
|
23-Feb-2010 |
jamesren <jamesren@592f7852-d20e-0410-864c-8624ca9c26a4> |
Marking metahost scheduler unittests as long tests since they require a
Django installation.
Signed-off-by: James Ren <jamesren@google.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@4262 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/utils/unittest_suite.py
|
| 74e77fcfe7828a387aff8427caf64f8fac728328 |
|
19-Feb-2010 |
jamesren <jamesren@592f7852-d20e-0410-864c-8624ca9c26a4> |
Add a --skip-tests option to the unittest_suite this can be used with --full to limit tests on a conditional basis (it is mostly used inside of other scripts).
Signed-off-by: Scott Zawalski <scottz@google.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@4259 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/utils/unittest_suite.py
|
| c44ae99354228290914326d42ef1e743b5b7e4b8 |
|
19-Feb-2010 |
jamesren <jamesren@592f7852-d20e-0410-864c-8624ca9c26a4> |
Refactor scheduler models into a separate module, scheduler_models. This module doesn't depend on monitor_db, only the other way around. The separation and isolation of dependencies should help us organize the scheduler code a bit better.
This was made possible largely by the many changes we made late last year to improve statelessness of the scheduler. It was motivated here by my work on pluggable metahost handlers, which will need to depend on scheduler models. Without this separation, we'd end up with circular dependencies.
Also includes some fixes for metahost schedulers.
Signed-off-by: Steve Howard <showard@google.com>
Property changes on: scheduler/scheduler_models.py
git-svn-id: http://test.kernel.org/svn/autotest/trunk@4252 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/utils/unittest_suite.py
|
| 656b3b8e1092a08bb60a059b09d1dbafadcbd037 |
|
28-Jan-2010 |
jadmanski <jadmanski@592f7852-d20e-0410-864c-8624ca9c26a4> |
Do simplejson imports in json_rpc lazily, so that the library is only needed
for actually making rpc calls, not just for importing the json_rpc module.
Also adjust the unittest suite runner to add the serviceHandler_unittest
to the long tests, since it requires a build externals run to actually work.
Signed-off-by: John Admanski <jadmanski@google.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@4174 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/utils/unittest_suite.py
|
| f828c77299496a78d8e7f5afe608f7e73851fbd0 |
|
25-Jan-2010 |
showard <showard@592f7852-d20e-0410-864c-8624ca9c26a4> |
First version of new RESTful AFE interface. Includes a substantial library (under frontend/shared) and a definition of the interface for AFE (frontend/afe/resources.py).
If you want to see what this interface looks like, I encourage you to check out
http://your-autotest-server/afe/server/resources/?alt=json-html
>From there you can explore the entire interface through your browser (this is one of its great strengths).
For an introduction to the idea behind RESTful services, try http://bitworking.org/news/How_to_create_a_REST_Protocol.
This is still very much under development and there are plenty of TODOs, but it's working so I wanted to get it out there so we can start seeing how useful it turns out to be.
Signed-off-by: Steve Howard <showard@google.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@4165 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/utils/unittest_suite.py
|
| 9afb2e9a16112651e9ef6f237eff8c14decd3ddf |
|
12-Jan-2010 |
showard <showard@592f7852-d20e-0410-864c-8624ca9c26a4> |
Exclude new monitor_db_cleanup_test from the "short" test suite.
Signed-off-by: Steve Howard <showard@google.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@4102 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/utils/unittest_suite.py
|
| 5f55484c193f51fe1f193a3bbff179f206a19d5b |
|
21-Dec-2009 |
mbligh <mbligh@592f7852-d20e-0410-864c-8624ca9c26a4> |
Because we have our own more-updated unittest.py in test_utils, any unit tests that
use it will not get executed by unittest_suite. As a quick fix, just extend the
unittest_suite.py script to load any unit test based on either the stdlib version or
our custom one.
Risk: Low
Visibility: Fixes up the unit test executor
Signed-off-by: John Admanski <jadmanski@google.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@4036 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/utils/unittest_suite.py
|
| 34ab09918228040aa244f7f258280e59c6baca3a |
|
06-Oct-2009 |
showard <showard@592f7852-d20e-0410-864c-8624ca9c26a4> |
beginnings of a new scheduler functional test. this aims to test the entire monitor_db.py file holistically, made possible by the fact that monitor_db.py is already isolated from all direct system access through drone_manager (this was a necessary separation for distributed scheduling). by mocking out the entire drone_manager, as well as other major dependencies (email manager, global config), and filling a test database, we can allow the dispatcher to execute normally and allow it to interact with all the other code in monitor_db. at the end, we can check the state of the database and the drone_manager, and (probably most importantly, given the usual failure mode of the scheduler) we can ensure no exceptions get raised from monitor_db.
right now, the test is very minimal. it's able to walk through the process of executing a normal, default job with nothing unusual arising. it checks very little, other than ensuring that the scheduler doesn't die from any exceptions. over time it can be extended to test many more cases and check many more things. this is just a start.
as a side note, i added a "django" backend to database_connection.py which just uses the Django connection wrapper. this is preferable because Django has lots of nice translations already in place. for example, SQLite returns datetime columns as strings, but Django's wrapper automatically translates them into real datetime objects. we could probably just use this in lots of places, such as the frontend and scheduler unit tests. but it was necessary here.
Signed-off-by: Steve Howard <showard@google.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@3801 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/utils/unittest_suite.py
|
| a64df1ab8e2ca7c6f2f1e5721b9c207f14d56c27 |
|
18-Sep-2009 |
mbligh <mbligh@592f7852-d20e-0410-864c-8624ca9c26a4> |
Let unittest_suite --full cleanup stray leftover .pyc files for us.
Signed-off-by: Gregory Smith <gps@google.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@3743 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/utils/unittest_suite.py
|
| ed2afea4ca6e23a82d20d1f2ee1067d0c25a8cc2 |
|
07-Jul-2009 |
showard <showard@592f7852-d20e-0410-864c-8624ca9c26a4> |
make SpecialTasks recoverable. this involves quite a few changes.
* run tasks in determined dirs instead of temp dirs. the dir paths look like hosts//-, for example, hosts/myhost/4-verify. the ID comes from the SpecialTask DB row. this allows us to find the pidfile when we go looking for it during recovery, and it makes it simple to find the logs for any given special task, much like for HostQueueEntries. added SpecialTask.execution_path() for this purpose, and added models_test to test it.
* added execution_path() to HostQueueEntry to match the interface of SpecialTask, allowing for more polymorphism, and changed most call sites to use it.
* since we're running in these dirs, copy the full results back in these dirs, instead of just copying a single log file.
* move process recovery code up into AgentTask, so that all AgentTasks can share the same generic process recovery code.
* change SpecialTask recovery code to do process recovery.
* change VerifyTask handling of multiple pending verify requests for a machine. instead of updating all the requests, just delete all other tasks. they're not specially tracked in any way so it's simplest to just delete them.
* made special tasks get marked is_active=False when they complete, to be consistent with HQEs
other changes:
* added null=True to SpecialTask.time_started definition
* made EmailManager.enqueue_notify_email always log the message, and removed explicit logging calls from call sites
* added feature to DroneManager.execute_command() to automatically substitute the working directory into the command. this avoids some duplicate information being passed around and simplifies the unit test.
Signed-off-by: Steve Howard <showard@google.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@3380 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/utils/unittest_suite.py
|
| 780fa7fd272267e955f361f1be1740424e4b5853 |
|
02-Jul-2009 |
mbligh <mbligh@592f7852-d20e-0410-864c-8624ca9c26a4> |
Clean up the test discovery a bit. Uses os.walk instead of the obsolete
os.path.walk. Now prunes subdirectories which are not python modules
from further searching. This will prevent any attempts to run tests
from non-repository random "data" files such as results directories, etc.
TESTED: I verified that exactly the same set of tests are found and
executed using this code as with the old code.
Signed-off-by: Gregory Smith <gps@google.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@3358 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/utils/unittest_suite.py
|
| ef1edafb2cee0a06805476cd3d78557ad5935310 |
|
02-Jul-2009 |
showard <showard@592f7852-d20e-0410-864c-8624ca9c26a4> |
Update the unittest finder to look for _test.py suffixes as well.
This way logging_manager_test.py is found and run.
Signed-off-by: Gregory Smith <gps@google.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@3351 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/utils/unittest_suite.py
|
| f8b19046c4496f570c776b65288382108a633ab4 |
|
12-May-2009 |
showard <showard@592f7852-d20e-0410-864c-8624ca9c26a4> |
Add the ability for users to add test attributes. Non-user-created attributes (added by the parser) are still immutable.
* add boolean column user_created to TestAttribute to keep track of which are user created, so we can preserve immutability
* add id primary key field to test attributes. Django requires this and we've been squeezing by without it, but we can't anymore.
* declare some PK fields AutoFields in TKO models, as they should be. this didn't matter before but does now that we have a TKO unit test, since these models determine how the test DB gets created.
* add set_test_attribute RPC to set/delete attributes
* modify get_detailed_test_views() to use the new populate_relationships() method to gather attributes and labels much more efficiently
* add rpc_interface_unittest, a unit test for the TKO rpc interface. TKO was previously completely untested, so this is the first unit test of any kind for it. since the doctests on AFE turned out to be quite unpopular, I'm using the unittest framework this time. this required some changes to AFE testing code.
* various fixes to model_logic to account for assumptions we were previously making that aren't true in TKO (mostly about PK fields being named "id").
Note that the migration may be slow, as it's adding two columns to test_attributes, a potentially large table.
Signed-off-by: Steve Howard <showard@google.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@3109 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/utils/unittest_suite.py
|
| 363cdb56d1b5326f020020365754be944c6d78a7 |
|
12-May-2009 |
showard <showard@592f7852-d20e-0410-864c-8624ca9c26a4> |
Remove csv_encoder_unittest from the default set that is run as it
required Django to be installed and most users and test developers will
never have that installed.
Signed-off-by: Gregory Smith <gps@google.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@3108 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/utils/unittest_suite.py
|
| 80718c7006e5fec46e543de381581bfa37d6054a |
|
26-Feb-2009 |
jadmanski <jadmanski@592f7852-d20e-0410-864c-8624ca9c26a4> |
Fix up the unit test suite to not try to run unit tests that it
won't be able to import.
Risk: Low
Visibility: Stops the suite from trying to run tests it can't possibly
run.
Signed-off-by: John Admanski <jadmanski@google.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@2824 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/utils/unittest_suite.py
|
| 4f2a2cbfa6b449173215172ff714ea7843507e58 |
|
07-Nov-2008 |
mbligh <mbligh@592f7852-d20e-0410-864c-8624ca9c26a4> |
make unittests executable in svn
git-svn-id: http://test.kernel.org/svn/autotest/trunk@2388 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/utils/unittest_suite.py
|
| 7f9dd3d1a6be0144c8c815570326926944205331 |
|
14-Oct-2008 |
showard <showard@592f7852-d20e-0410-864c-8624ca9c26a4> |
Get rid of dependencies between database-based unit tests in unittest_suite.py. There's no need anymore, now that they all use SQLite.
git-svn-id: http://test.kernel.org/svn/autotest/trunk@2281 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/utils/unittest_suite.py
|
| 442e71e957a8d16ba234193352f3ad1baffbd680 |
|
06-Oct-2008 |
showard <showard@592f7852-d20e-0410-864c-8624ca9c26a4> |
Move migration system into database/ directory.
git-svn-id: http://test.kernel.org/svn/autotest/trunk@2243 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/utils/unittest_suite.py
|
| 3de2a76fa5e272503f924b5cd9d100931bed1e7f |
|
12-Sep-2008 |
showard <showard@592f7852-d20e-0410-864c-8624ca9c26a4> |
Add a unit test to check that the GWT code compiles. I added it as a "long" test because it requires GWT to be set up (and it's kind of slow).
git-svn-id: http://test.kernel.org/svn/autotest/trunk@2138 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/utils/unittest_suite.py
|
| 43758dfde7745b5b12e8bcb2e91207ea7092d7f8 |
|
04-Sep-2008 |
mbligh <mbligh@592f7852-d20e-0410-864c-8624ca9c26a4> |
Change the debug variable in the unittest_suite to a debug flag.
Risk: Low
Visibility: Medium
Signed-off-by: Jeremy Orlow <jorlow@google.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@2107 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/utils/unittest_suite.py
|
| cc85e815b4f21265cd646d72f79955c771c7a5fb |
|
08-Aug-2008 |
showard <showard@592f7852-d20e-0410-864c-8624ca9c26a4> |
Fixing the unit test suite. Tests were failing because they were being
passed unexpected command line arguments. Also, some tests were failing
because they were creating and destroying test databases with the same
name.
Risk: low
Visibility: medium
Signed-off-by: James Ren <jamesren@google.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@1964 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/utils/unittest_suite.py
|
| 1ee9ad74c7505e90dda27b680058aaf93c93e903 |
|
01-Aug-2008 |
mbligh <mbligh@592f7852-d20e-0410-864c-8624ca9c26a4> |
Unbuffering the unittest output as it helps sometimes.
Signed-off-by: Jean-Marc Eurin <jmeurin@google.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@1947 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/utils/unittest_suite.py
|
| eeb13577724d31a4a6a2ed6b7956b37c729b7a2b |
|
30-Jul-2008 |
mbligh <mbligh@592f7852-d20e-0410-864c-8624ca9c26a4> |
makes unittest running parallel. The code which does the parallel processing understands the concept of dependencies and rate limiting. The former is a feature that's unused by this code, but I'll be sending something out soon that makes use of it
Signed-off-by: Jeremy Orlow <jorlow@google.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@1928 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/utils/unittest_suite.py
|
| bd1eb20db1d469a73ce169ecf4af5231b52bace6 |
|
30-Jul-2008 |
mbligh <mbligh@592f7852-d20e-0410-864c-8624ca9c26a4> |
To apply: svn move coverage_suite.py to utils/coverage_suite.py and unittest_suite.py to utils/unittest_suite.py and then apply this patch.
This patch moves the unittest tools into utils (where they should have been from the start) and makes unittest running parallel. The code which does the parallel processing understands the concept of dependencies and rate limiting. The former is a feature that's unused by this code, but I'll be sending something out soon that makes use of it.
Signed-off-by: Jeremy Orlow <jorlow@google.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@1924 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/utils/unittest_suite.py
|