| 2c4ce07ee5e885b7da219ac0204786f1e428a9d9 |
|
26-Jun-2015 |
Don Garrett <dgarrett@google.com> |
full_release_test: Stop importing cbuildbot_config.
full_release_test was importing cbuildbot_config so that it could
get a full list of all boards that exist in our build config. Since
we're trying to stop hardcoding the config, this was problematic.
Remove the "--all_boards" command line option. It doesn't appear to be
used automatically, and I'm pretty sure it's no longer a sane thing to
do.
Remove validation that all boards listed on the command line are real,
and just let errors happen. Since we mostly only call this
automatically, this isn't much of an issue.
Also redo tests to match.
BUG=chromium:483566
TEST=Unittests.
Change-Id: I639caa2a56e55fe9aff8ae1e3e8a788aa2906b8f
Reviewed-on: https://chromium-review.googlesource.com/282068
Trybot-Ready: Don Garrett <dgarrett@chromium.org>
Tested-by: Don Garrett <dgarrett@chromium.org>
Reviewed-by: Dan Shi <dshi@chromium.org>
Commit-Queue: Don Garrett <dgarrett@chromium.org>
/external/autotest/site_utils/autoupdate/full_release_test_test.py
|
| 34c908239317a5041b69346d4720b23cf81117a7 |
|
16-Dec-2014 |
Gaurav Shah <gauravsh@chromium.org> |
full_release_test.py: Handle delta payload file names on non-release builds
Non-release builds have a date fragment in the version file name. Handle
it as well.
This change was previously reviewed on https://chromium-review.googlesource.com/236675 ,
landed and reverted. This patch includes a fix for the case where the
source and target version are the same (npo) in release builds.
BUG=chromium:425404
BUG=chromium:390828
TEST=New unit test
TEST=Manual test (see below)
Manual test:
* Regression test on release builds:
$ site_utils/autoupdate/full_release_test.py --npo --nmo --dump --dump_dir /tmp/au_test --archive_url gs://chromeos-image-archive/swanky-release/R41-6630.0.0 6630.0.0 swanky '--log=debug' --dry_run
This command generates a control file in /tmp/au_test with no
differences in the uris when comparing it with the one stored in
gs://chromeos-image-archive/swanky-release/R41-6630.0.0/au_control.tar.bz2
which was green. This fixes the regression introduced in CL:236675
(already reverted) where the source_image_uri was missing the full
payload filename.
* Trybot test:
Ran a lumpy-release trybot with --hwtest enabled, that uploaded the
build artifacts to
gs://chromeos-image-archive/trybot-lumpy-release/R43-6831.0.0-b2425
where the version will include the '-a1' suffix in the payloads.
Ran the same command using the trybot urls and checked the generated
source_image_uri variable in the control file has the right full payload
(found in the same artifacts directory):
$ site_utils/autoupdate/full_release_test.py --npo --nmo --dump --dump_dir /tmp/au_test --archive_url gs://chromeos-image-archive/trybot-lumpy-release/R43-6831.0.0-b2425 6831.0.0-a1 lumpy '--log=debug' --dry_run
Change-Id: I2ed839f16883130b5601701e99ebf76fad589312
Reviewed-on: https://chromium-review.googlesource.com/254860
Tested-by: Alex Deymo <deymo@chromium.org>
Reviewed-by: Gaurav Shah <gauravsh@chromium.org>
Commit-Queue: Alex Deymo <deymo@chromium.org>
/external/autotest/site_utils/autoupdate/full_release_test_test.py
|
| 830a55e02a3b41ad85e70b19c473e882ab604797 |
|
29-Dec-2014 |
Chris Sosa <sosa@chromium.org> |
Revert "full_release_test.py: Handle delta payload file names on non-release builds"
This reverts commit 9604b2ae01aec7c0243bbd8b208cd8d18797f5a7.
Change-Id: I33c574484b89b044c370ba010945e02b281c3e26
Reviewed-on: https://chromium-review.googlesource.com/237930
Reviewed-by: Chris Sosa <sosa@chromium.org>
Tested-by: Chris Sosa <sosa@chromium.org>
/external/autotest/site_utils/autoupdate/full_release_test_test.py
|
| 9604b2ae01aec7c0243bbd8b208cd8d18797f5a7 |
|
16-Dec-2014 |
Gaurav Shah <gauravsh@chromium.org> |
full_release_test.py: Handle delta payload file names on non-release builds
Non-release builds have a date fragment in the version file name. Handle
it as well.
Also fix assumptions about the source_uri for npo full updates.
Specifically, use the target version to find the full update
payload when source and targets are the same. This ensures the
logic correctly handles developer build version names (with the date).
BUG=chromium:425404
BUG=chromium:390828
TEST=New unit test
TEST=trybots on storm-release, storm-paladin, lumpy-release, lumpy-paladin
Change-Id: I3f5f454702269a93020d266eebc917966ea79ce8
Reviewed-on: https://chromium-review.googlesource.com/236675
Reviewed-by: Chris Sosa <sosa@chromium.org>
Commit-Queue: Gaurav Shah <gauravsh@chromium.org>
Tested-by: Gaurav Shah <gauravsh@chromium.org>
/external/autotest/site_utils/autoupdate/full_release_test_test.py
|
| 5a417084ed5637ceeb4b6efb0b33871ed4b0fdcc |
|
09-Dec-2014 |
Gaurav Shah <gauravsh@chromium.org> |
full_release_test.py: Sanity checking board against all known chromite configs
The current logic restricts itself to only those boards that have
hw_tests enabled. This isn't necessary as we may want to generate AU
test artifacts even for boards not currently being hw tested.
BUG=chromium:425404
TEST=unit test
Change-Id: Icdd383e44042b922d887944c5af1cf217065f679
Reviewed-on: https://chromium-review.googlesource.com/234849
Reviewed-by: Alex Deymo <deymo@chromium.org>
Reviewed-by: Chris Sosa <sosa@chromium.org>
Tested-by: Gaurav Shah <gauravsh@chromium.org>
Commit-Queue: Gaurav Shah <gauravsh@chromium.org>
/external/autotest/site_utils/autoupdate/full_release_test_test.py
|
| e1417e13e50201ae82cc82652bc290218662cdd9 |
|
30-Oct-2013 |
Gilad Arnold <garnold@chromium.org> |
autotest: extend AU test name to include delta/full
This is needed since we are now starting to test full test payloads from
paygen, in addition to delta ones. Without it, we'll be causing name
collisions (control file names, Autotest job names).
BUG=chromium:303963
TEST=Unique test name includes delta/full qualifier.
Change-Id: I66c44436ab3be865786155be5fe95053ce0e60ca
Reviewed-on: https://chromium-review.googlesource.com/175159
Reviewed-by: Gilad Arnold <garnold@chromium.org>
Commit-Queue: Gilad Arnold <garnold@chromium.org>
Tested-by: Gilad Arnold <garnold@chromium.org>
/external/autotest/site_utils/autoupdate/full_release_test_test.py
|
| 67dbe59a00e09c5357fd3667487d2ee58dc30993 |
|
22-Oct-2013 |
Chris Sosa <sosa@chromium.org> |
Get boards dynamically from chromite's cbuildbot_config and remove FSI logic.
This change gives us two less thing to maintain in full_release_test. Instead
of having to add new boards in we dynamically read all boards that are
configured for hwtests from cbuildbot_config. I've gone ahead and added a
sanity test in case anyone changes the interface (i.e. hw_tests to hwtests)
we'll catch it in the CQ / canaries. In addition, we no longer have to worry
about maintaining the FSI logic.
BUG=chromium:309751
TEST=Tests + npo sanity test.
Change-Id: I859fc59bfe0f726167e7f5f1729d65bdb5fab11a
Reviewed-on: https://chromium-review.googlesource.com/174061
Reviewed-by: Chris Sosa <sosa@chromium.org>
Commit-Queue: Chris Sosa <sosa@chromium.org>
Tested-by: Chris Sosa <sosa@chromium.org>
/external/autotest/site_utils/autoupdate/full_release_test_test.py
|
| db6d3ac54392502594a1da38f579cde59cf18db2 |
|
11-Oct-2013 |
Chris Sosa <sosa@chromium.org> |
Add a decent set of integration tests for full_release_test.py.
I'm checking in a set of integration tests that cover the common workflows
for full_release_test used by test engineers and ourselves when testing
our changes to full_release_test. These are framed as unittests so that
they are run as part of the autotest unittests on every build thus
rejecting a bad change in the CQ from breaking our workflows.
I refrained from mocking anything out except the gsutil call as I expect
that to be stable and wanted to not have any external dependencies. For
the most part I use --dump to actually test the output of the control
files we expect.
Finally adding this to unittests had some crazy import issues. I've resolved
those by force loading devserver using imp.
BUG=chromium:266426
TEST=Ran it separately and as part of utisl/unittest_suite
Change-Id: I63678bfcc397bc058ba745aa5e0219b58f37228f
Reviewed-on: https://chromium-review.googlesource.com/172692
Reviewed-by: Chris Sosa <sosa@chromium.org>
Commit-Queue: Chris Sosa <sosa@chromium.org>
Tested-by: Chris Sosa <sosa@chromium.org>
/external/autotest/site_utils/autoupdate/full_release_test_test.py
|