| 7b271d0305b5f6ba1c746f3b6098695e9377f038 |
|
26-Apr-2016 |
Dan Shi <dshi@google.com> |
[autotest] Update control_file_preprocessor to support tests in other autotest dir.
BUG=b:28319891
TEST=local build dragonboard package
Change-Id: If3b1bde77acbcdccbff5774f104e0419b049ba36
Reviewed-on: https://chromium-review.googlesource.com/340760
Commit-Ready: Dan Shi <dshi@google.com>
Tested-by: Dan Shi <dshi@google.com>
Reviewed-by: Kevin Cheng <kevcheng@chromium.org>
/external/autotest/site_utils/suite_preprocessor.py
|
| 9a1987acc36506ceba0397ce64aeca1b39eb5b39 |
|
22-Aug-2013 |
Alex Miller <milleral@chromium.org> |
[autotest] Death to the tryjobs.
This removes reimager.py from dynamic suite, and follows through with
all the consequences of doing so:
* reimage_and_run has had the reimager completely dropped from it
* All reimaging-related parameters in SuiteSpec have been removed
* Any unittests for reimaging code were removed
* The suite scheduler sanity check for `num` was removed
* run_suite no longer reports on reimage times, as there are none
* skip_reimage has been removed, including in suite control files
* The dependencies_info file is no longer needed, so therefore:
* suite_preprocessor is being stripped down until it's removed in
the ebuilds
BUG=chromium:250586
TEST=unit, manual
Built trybot-lumpy-paladin/R31-4609.0.0-b1136 with this patch, and ran
various suites on it. Dummy ran as expected. Network3g_tmobile was all
TEST_NA as expected. BVT scheduled and ran tests. All seemed fine.
Also ran lumpy-release/R29-4319.78.0 to confirm backwards compatibility.
Change-Id: Ia75400f906eff5f3234a2a97ab82e1e014229e7c
Reviewed-on: https://chromium-review.googlesource.com/66607
Reviewed-by: Aviv Keshet <akeshet@chromium.org>
Tested-by: Alexander Miller <milleral@chromium.org>
Commit-Queue: Alexander Miller <milleral@chromium.org>
/external/autotest/site_utils/suite_preprocessor.py
|
| c594c1c3ed039635462371af90562475fcee575e |
|
10-Jul-2013 |
beeps <beeps@chromium.org> |
[autotest] Pipe suite_name through client devserver code.
To reduce the overhead involved with fetching control files
from the devserver we generate a mapping of suite->control
files at build time. This cl will ask the control file getter
to fetch the control files for a given suite instead of all
the control files associated with an image.
Also removing SUITE = None from some networking test control
files, and patched unittests.
BUG=chromium:252398
TEST=Ran a suite with many control files. Made sure the suite->
control file mapping falls back to the old code when a bad suite
name is specified. Compared the test objects created in the old
version vs those created with this change.
Ran unittests.
CQ-DEPEND=CL:I6b590c8c40a863e6744875a26ac228ffd4dd8794
Change-Id: I4274c78764ffaaabef1ed48cdb40f523e307938d
Reviewed-on: https://gerrit.chromium.org/gerrit/63182
Tested-by: Prashanth Balasubramanian <beeps@chromium.org>
Reviewed-by: Dan Shi <dshi@chromium.org>
Commit-Queue: Prashanth Balasubramanian <beeps@chromium.org>
/external/autotest/site_utils/suite_preprocessor.py
|
| 5cb8f91e6853de4ecc351a842eb8f1c1919094bb |
|
10-Jul-2013 |
beeps <beeps@chromium.org> |
[autotest] A tool that maps a suite to it's control files.
Currently, this mapping is achieved at runtime, by going
through all control files in search of a suite attribute
that matches the current suite's name. This is an expensive
process, and since the control files don't change after we
freeze them at build time, one that can be avoided with some
preprocessing. This tool will go through all control files
specified in the given root directory and build a suite
to control file map that dynamic_suite can consume at
run time.
BUG=chromium:252398
TEST=Ran the script both stand alone and through emerge
autotest-all, checked the suite map it generated.
Change-Id: I77df32189039fc9d0f1aa6768a35ae4b361e01ae
Reviewed-on: https://gerrit.chromium.org/gerrit/61393
Tested-by: Prashanth Balasubramanian <beeps@chromium.org>
Reviewed-by: Alex Miller <milleral@chromium.org>
Commit-Queue: Prashanth Balasubramanian <beeps@chromium.org>
/external/autotest/site_utils/suite_preprocessor.py
|
| 9979b5a5e449662ce2047151735b7ba7bb206ca5 |
|
02-Nov-2012 |
Alex Miller <milleral@chromium.org> |
[autotest] Add dependencies analysis to |suite_scheduler --sanity|
It's quite easy to accidentally make a suite suddenly unable to properly
run once tests start getting added that have DEPENDENCIES in them. Any
time that the number of different machine configurations exceeds the
number of machines allocated to the suite, some tests will never be able
to get run.
Thankfully, we can do roughly the same analysis statically over the
codebase that dynamic_suites does at runtime so that we can generate
instructions on what suites are currently crippled and provide
instructions on how to fix them.
BUG=chromium-os:35828
TEST=There already existed violating suites
$ ./site_utils/suite_scheduler/suite_scheduler.py --sanity
WARNING:root:Increase KernelDailyRegression to |num: 2|
WARNING:root:Increase NightlyRegression to |num: 2|
$ echo $?
1
Change-Id: I5dc7a4f7a12b0a5877b1d4437d2a7562de2d6dc5
Reviewed-on: https://gerrit.chromium.org/gerrit/40455
Reviewed-by: Scott Zawalski <scottz@chromium.org>
Commit-Queue: Alex Miller <milleral@chromium.org>
Tested-by: Alex Miller <milleral@chromium.org>
/external/autotest/site_utils/suite_preprocessor.py
|
| 44e4d6ce5a7c38451c25d35b307b35338606091f |
|
15-Aug-2012 |
Chris Masone <cmasone@chromium.org> |
[autotest] Continuing refactor of dynamic_suite code; splitting monster files!
Split the biiiiig dynamic_suite.py and dynamic_suite_unittest.py into separate
files for Reimager and Suite. Adjust imports to compensate.
BUG=chromium-os:30266
TEST=unit
TEST=successful run_suite.py run
TEST=suite_enumerator.py, suite_preprocessor.py,
Change-Id: I0457053a7ae1422970138619a64edbcfbbc338bc
Reviewed-on: https://gerrit.chromium.org/gerrit/30457
Tested-by: Chris Masone <cmasone@chromium.org>
Reviewed-by: Scott Zawalski <scottz@chromium.org>
Commit-Ready: Chris Masone <cmasone@chromium.org>
/external/autotest/site_utils/suite_preprocessor.py
|
| b493555db2d43e79d96e793cae9d1ffb822dd6c1 |
|
14-Aug-2012 |
Chris Masone <cmasone@chromium.org> |
[autotest] Move dynamic suite code into its own module
No big rewrite, just moving files around
BUG=chromium-os:30266
TEST=unit
TEST=successful run_suite.py run
TEST=suite_enumerator.py, suite_preprocessor.py, and suite_scheduler.py
Change-Id: I2fbcae0332104ce3adcb10a1e90ce94cb209aca8
Reviewed-on: https://gerrit.chromium.org/gerrit/30267
Reviewed-by: Scott Zawalski <scottz@chromium.org>
Commit-Ready: Chris Masone <cmasone@chromium.org>
Tested-by: Chris Masone <cmasone@chromium.org>
/external/autotest/site_utils/suite_preprocessor.py
|
| 4ac6c7349d8cdbd5203534fa87642186e7f9f83f |
|
05-Jun-2012 |
Chris Masone <cmasone@chromium.org> |
[autotest] Add data for tests that have no DEPENDENCIES in suite_preprocessor.py
When preprocessing tests to extract suite information, it's important
that we keep track of tests with no DEPENDENCIES, as well as those that do.
This enables us to make good decisions later wrt padding out pools of
machines for suite runs.
BUG=chromium-os:22060
TEST=run suite_preprocessor.py
Change-Id: Ibba973a6e73d92402d10ed857c4f3288a86adb2f
Reviewed-on: https://gerrit.chromium.org/gerrit/24430
Tested-by: Chris Masone <cmasone@chromium.org>
Reviewed-by: Chris Sosa <sosa@chromium.org>
Commit-Ready: Chris Masone <cmasone@chromium.org>
/external/autotest/site_utils/suite_preprocessor.py
|
| a3d98c8c9ffc6ffa52762696fbd835d89c310423 |
|
04-Jun-2012 |
Chris Masone <cmasone@chromium.org> |
[autotest] Update suite_preprocessor.py to use only literals
When saving dependencies information, forcing all data to literal types
means that the resulting file can be read in with ast.literal_eval, which
is much safer than using eval().
BUG=chromium-os:22060
TEST=run suite_preprocessor.py and check the output to ensure all data is in literals.
Change-Id: I23ad701b0b44e7c6bed931f96836a87c5f70c488
Reviewed-on: https://gerrit.chromium.org/gerrit/24399
Tested-by: Chris Masone <cmasone@chromium.org>
Reviewed-by: Chris Sosa <sosa@chromium.org>
Commit-Ready: Chris Masone <cmasone@chromium.org>
/external/autotest/site_utils/suite_preprocessor.py
|
| c80af5b919a1d97c3246279e55a1c75b9158e996 |
|
30-May-2012 |
Chris Masone <cmasone@chromium.org> |
[autotest] Tool to gather suite dependencies at build-time
In order to support DEPENDENCIES in dynamic suites, the infrastructure needs
to be able to determine the needs of a suite _before_ doing any reimaging work.
Naively, this would require looking at all controls files in a suite before
picking machines to reimage. Staging all control files on the dev server is
slow, and we currently do this in the background while reimaging devices.
To avoid forcing the infrastructure to stage the entire autotest tarball before
doing any work, we plan to pre-process control files at build time and use
this data to make decisions at run-time. This tool does the pre-processing
work.
BUG=chromium-os:22060
TEST=run this tool, view output.
Change-Id: Ifde836db1a60eff2e7fb5eb74ba4ae84bd505d5f
Reviewed-on: https://gerrit.chromium.org/gerrit/24217
Tested-by: Chris Masone <cmasone@chromium.org>
Reviewed-by: Scott Zawalski <scottz@chromium.org>
Commit-Ready: Chris Masone <cmasone@chromium.org>
/external/autotest/site_utils/suite_preprocessor.py
|