5cca8180477b25ab2b83861cbaaeb1fb35fd931d |
|
20-Nov-2017 |
Allen Li <ayatane@chromium.org> |
[autotest] Use JobHandoff for job_aborter tracking This handles all cases of job_reporter failure after spawning. The main loophole in the previous model is if job_reporter crashes before making the lease file, as job_aborter relied on expired leases to determine if cleanup is necessary. We now rely on JobHandoff to track ongoing jobs. The lease file is still kept to determine if a job still has an active job_reporter owning it. Previously we cared only about expired lease files, now we care only about active lease files combined with JobHandoff. BUG=chromium:748234 TEST=bin/test_lucifer TEST=bin/job_aborter without crashing Change-Id: I97e8b53f2fbd33d41a2b567e2797de8811a36e88 Reviewed-on: https://chromium-review.googlesource.com/780768 Commit-Ready: Allen Li <ayatane@chromium.org> Tested-by: Allen Li <ayatane@chromium.org> Reviewed-by: Allen Li <ayatane@chromium.org>
/external/autotest/tko/site_parse_unittest.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/tko/site_parse_unittest.py
|
934f0dca520ebf8eeebaa7befa484408281e0f91 |
|
15-Oct-2014 |
Jakob Juelich <jakobjuelich@chromium.org> |
[autotest] Move database configuration to separate file. As we're about to add more databases the logic for parsing the database configurations gets more complicated. This centralizes the configuration parsing in one dedicated file. BUG=chromium:419435 DEPLOY=apache,scheduler,host_scheduler,shard_client TEST=Ran suites, tried syncdb and apache restart Change-Id: I486b72f30ccd0f1e44316927b4fe3d5c93eacbe2 Reviewed-on: https://chromium-review.googlesource.com/223377 Reviewed-by: Dan Shi <dshi@chromium.org> Commit-Queue: Jakob Jülich <jakobjuelich@chromium.org> Tested-by: Jakob Jülich <jakobjuelich@chromium.org>
/external/autotest/tko/site_parse_unittest.py
|
3270e189d5da845d034231a6eb75c5bd4e37ac97 |
|
13-Oct-2014 |
Jakob Juelich <jakobjuelich@chromium.org> |
Revert "[autotest] Always use tko tables on master from shards." This reverts commit e2bf396b7d3870f7565b2b10018087ab7fa6256e. BUG=422637 CQ-DEPEND=CL:223065 Change-Id: I0513889a3acfc3a189843e79030da9bbd551999d Reviewed-on: https://chromium-review.googlesource.com/223072 Reviewed-by: Fang Deng <fdeng@chromium.org> Commit-Queue: Jakob Jülich <jakobjuelich@chromium.org> Tested-by: Jakob Jülich <jakobjuelich@chromium.org>
/external/autotest/tko/site_parse_unittest.py
|
a204088d40d4fd1ecfd8f219f723b72d8ebe391c |
|
13-Oct-2014 |
Jakob Juelich <jakobjuelich@chromium.org> |
Revert "[autotest] Always use tko tables on master from shards." This reverts commit 8aff81d0334c05c5e7b8d6c3f1dcdc2b1ef21c29. BUG=422637 CQ-DEPEND=CL:223072 Change-Id: I897828cd665b265c2518c08cbe4c55ea6edb64b6 Reviewed-on: https://chromium-review.googlesource.com/223065 Reviewed-by: Fang Deng <fdeng@chromium.org> Commit-Queue: Jakob Jülich <jakobjuelich@chromium.org> Tested-by: Jakob Jülich <jakobjuelich@chromium.org>
/external/autotest/tko/site_parse_unittest.py
|
8aff81d0334c05c5e7b8d6c3f1dcdc2b1ef21c29 |
|
02-Oct-2014 |
Jakob Juelich <jakobjuelich@chromium.org> |
[autotest] Always use tko tables on master from shards. tko/db.py was changed to always use settings for the global database. This added configuration overhead for non-shard machines. This adds the normal, old settings as a failover. Also, 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. This is a re-submit of CL:221018 and contains a fix for the import error on the builders. BUG=chromium:419435 TEST=Ran suites and manually tried rpcs. DEPLOY=apache Change-Id: Id470ae189231384eda8aa3e78aa97f8dde2548e1 Reviewed-on: https://chromium-review.googlesource.com/222286 Reviewed-by: Prashanth B <beeps@chromium.org> Reviewed-by: Fang Deng <fdeng@chromium.org> Commit-Queue: Jakob Jülich <jakobjuelich@chromium.org> Tested-by: Jakob Jülich <jakobjuelich@chromium.org> Reviewed-by: Dan Shi <dshi@chromium.org>
/external/autotest/tko/site_parse_unittest.py
|
e2bf396b7d3870f7565b2b10018087ab7fa6256e |
|
02-Oct-2014 |
Jakob Juelich <jakobjuelich@chromium.org> |
[autotest] Always use tko tables on master from shards. tko/db.py was changed to always use settings for the global database. This added configuration overhead for non-shard machines. This adds the normal, old settings as a failover. Also, 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:419435 TEST=Ran suites and manually tried rpcs. DEPLOY=apache,tko Change-Id: I675b064ffdcb0440cd33835b9a83e3858f826ca7 Reviewed-on: https://chromium-review.googlesource.com/221018 Tested-by: Jakob Jülich <jakobjuelich@chromium.org> Reviewed-by: Fang Deng <fdeng@chromium.org> Commit-Queue: Jakob Jülich <jakobjuelich@chromium.org>
/external/autotest/tko/site_parse_unittest.py
|
9ec668053c3cc508d3966e319e5b2bc644b272d6 |
|
28-Apr-2014 |
Fang Deng <fdeng@chromium.org> |
Revert "Revert "[autotest] TKO parser mark original tests as invalid"" This reverts commit dbd9037df0cbe1232fcb016a2c261f5994ae03a2. Commit this cl again. Once this cl lands, deploy the db changes together with https://chrome-internal-review.googlesource.com/#/c/161494/ https://chrome-internal-review.googlesource.com/#/c/161426/ DEPLOY=apache, migrate, wmatrix db changes should be pushed together (see commit messeage) Change-Id: I47916708e7b49bbc2064370262e3f9e231f08efe Reviewed-on: https://chromium-review.googlesource.com/197306 Reviewed-by: Dan Shi <dshi@chromium.org> Tested-by: Fang Deng <fdeng@chromium.org> Commit-Queue: Fang Deng <fdeng@chromium.org>
/external/autotest/tko/site_parse_unittest.py
|
dbd9037df0cbe1232fcb016a2c261f5994ae03a2 |
|
28-Apr-2014 |
Prashanth B <beeps@chromium.org> |
Revert "[autotest] TKO parser mark original tests as invalid" This reverts commit 5ca36681271b3feab50dfabc67eb43b6669032c6. Change-Id: I7e597d0f341f9046078e2f9319c30d1d2cb8f599 Reviewed-on: https://chromium-review.googlesource.com/197230 Reviewed-by: Prashanth B <beeps@chromium.org> Commit-Queue: Prashanth B <beeps@chromium.org> Tested-by: Prashanth B <beeps@chromium.org>
/external/autotest/tko/site_parse_unittest.py
|
5ca36681271b3feab50dfabc67eb43b6669032c6 |
|
28-Feb-2014 |
Fang Deng <fdeng@chromium.org> |
[autotest] TKO parser mark original tests as invalid This is part of the test retry imeplementation. When retry job finished, we mark the original tests as invalid so that run_suite/tko frontend could get the latest results by only retrieving "valid" tests. Also add a column 'invalidates_test_idx' in tko_tests. This field works as a pointer from retry to original tests. It will be used by wmatrix. Design doc: crbug.com/314759 CQ-DEPEND=CL:191002, CL:190585 TEST=1)Manually call create_job twice, drop a keyval "original_retry_job_id" for the first job. Let the scheduler pick up and run the two jobs. Observe that at the end, the rows for the first job in tko_tests are marked as invalid. And 'invalidates_test_idx' are updated correctly. 2) Integration test with crosreview.com/191002 and crosreview.com/190585. - Add "JOB_RETRIES=2" to dummy_Fail/control and dummy_Pass/control. Create a trybot image that has the change. - run_suite.py -b lumpy -s dummy -i trybot-lumpy-release/R35-5653.0.0-b1948 - Observe that dummy_Fail is retried twice, and 'invalid' and 'invalidates_job_id' are properly set in tko_tests. Observe that dummy_Pass is not retried. - Test the same flow but dependencies are not satisfied Observed no retry was scheduled - Test the same flow but abandon dummy_Fail before it started Observed no retry was scheduled 3) dummy suite runs ok with run_suite and test_that 4) Run database/migrate.py sync 86 (85) Observed database sync'd properly. BUG=chromium:347687 DEPLOY=migrate, apache Change-Id: Ieed64a724c7330c50e8c022bd659b9d1ec781061 Reviewed-on: https://chromium-review.googlesource.com/188365 Reviewed-by: Fang Deng <fdeng@chromium.org> Commit-Queue: Fang Deng <fdeng@chromium.org> Tested-by: Fang Deng <fdeng@chromium.org>
/external/autotest/tko/site_parse_unittest.py
|
7768f7d8fad5370f50c556a2eaee5feb2a41a48b |
|
21-Jun-2013 |
Aviv Keshet <akeshet@chromium.org> |
[autotest] remove "unit"test which just checks for a directory to exist This test doesn't make sense as a unit test, and is breaking when run inside the chroot. BUG=chromium:221254 TEST=Test passes inside chroot CQ-DEPEND=CL:I4b2123ae691bd371f983026ef991bebf60fd5e7b Change-Id: Ic5535de6c834eb6c8cb6730490c4bfb1ac37cb11 Reviewed-on: https://gerrit.chromium.org/gerrit/59603 Reviewed-by: Aviv Keshet <akeshet@chromium.org> Tested-by: Aviv Keshet <akeshet@chromium.org> Commit-Queue: Aviv Keshet <akeshet@chromium.org>
/external/autotest/tko/site_parse_unittest.py
|
4111f86ce678209f35d52ef42417ad072fc7b918 |
|
13-Feb-2013 |
Aviv Keshet <akeshet@chromium.org> |
[autotest] Fix unittest -- remove site_parse tests of removed funcs A number of functions were eliminated from site_parse.py in commit facf51195e190c9786862940f0924f2074dbfbf1 , but were still being referenced in site_parse_unittest.py. Removed all the tests that referenced these removed functions. BUG=chromium-os:37989 TEST=Unit tests for this module now pass Change-Id: Ibb2dc8c2abcb7e7cb4c1e0e89332254f49430c98 Reviewed-on: https://gerrit.chromium.org/gerrit/43207 Commit-Queue: Aviv Keshet <akeshet@chromium.org> Reviewed-by: Aviv Keshet <akeshet@chromium.org> Tested-by: Aviv Keshet <akeshet@chromium.org>
/external/autotest/tko/site_parse_unittest.py
|
4a431e6cf2fc2419829612c99e3594455f6d4285 |
|
12-Oct-2011 |
Dale Curtis <dalecurtis@chromium.org> |
Automatically generate stack traces for crashes. Adds support for automatically generating stack traces for crashes. Uses the post job parser to check for crashes, retrieve debug symbols, and call cros_generate_stacks_bvt inside the chroot. Upon completion, each core dump in the results folder has an associated .dmp.txt stack trace. Uses gsutil to retrieve the debug symbols as well as a local cache to ensure symbols for the same build aren't downloaded repeatedly. The cache self cleans to contain only the last 24 hours worth of symbols. The debug symbol URLs are read from the dashboard configuration files which are added to autotest/utils/dashboard/. Fixes an issue with os_dep where it didn't expand usernames or variables in the path. Will upstream. Introduces 12 new unit tests to verify this functionality. BUG=chromium-os:19565 TEST=Ran locally + Unit tests. Change-Id: Ib46841f62188a3f18be9c2c05c0a2c244cbae605 Reviewed-on: http://gerrit.chromium.org/gerrit/10060 Reviewed-by: Thieu Le <thieule@chromium.org> Tested-by: Dale Curtis <dalecurtis@chromium.org>
/external/autotest/tko/site_parse_unittest.py
|