This change may be controversial -- it will basically make the x86-generic
full buildbot fail if tests fail to build.
There are a few options:
1. do this and see how it goes;
2. don't do this and rely on the test failing to run;
3. do this but also change buildbot to pass --nobuildcheck to build_autotest
Review URL: http://codereview.chromium.org/848005
This saves almost 1 minute (out of 6) on my build host for the current full
build_autotest.sh. The savings will be more significant once the Chrome tests
(200MB+) also get into autotest.
Alternatively, we could still build the binary package and use it as part of
archive_build.sh (i.e., just copy it there instead of creating a new one).
But most people don't run archive_build so it may be better to not create
the binary package as part of build_autotest.sh.
Review URL: http://codereview.chromium.org/661473
ecee13e13945c7df79e397012054206cac6cb2f0 back to the previous revision.
This new file should be identical to the one at
ce18a0349a88ffbe01a2e88526aeb271b54dec60
Review URL: http://codereview.chromium.org/646057
1. work with the new portage build system. Yes, cross compiling works.
2. work with new upstream changes to build a single or a subset of site test which specified from command line.
I will update the how-to document after all code checked in.
Please also refer to change from 582012 which had been included here and 582012 will be abandoned after this CL checked in.
Review URL: http://codereview.chromium.org/596110
this is necessary for portage-based builds which change the
chroot. You must pass --chroot to the run_remote_tests in this
case.
Review URL: http://codereview.chromium.org/588010
Don't punish the good people trying to write python-only autotests by
requiring them to sit through a long build_autotest run to test
every change. run_remote_tests and build_autotest both update
the chroot copy now.
Review URL: http://codereview.chromium.org/578027
