Originally test sharding for android was written with performance in mind
(i.e., to scale up the test speed per device).
Now that we're on the main waterfall, we need to improve reliability as
devices may randomly drop offline during tests.
This patch captures exceptions in key places and retries if there are enough
devices available.
BUG=153718
TEST=run android tests, randomly unplugging devices
Review URL: https://chromiumcodereview.appspot.com/11275078
git-svn-id: http://src.chromium.org/svn/trunk/src/build@165918 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
This is not yet used, but helps lay the groundwork for building chrome/
targets for iOS.
This uses exclude-all-and-include since Chrome for iOS uses only a subset
of chrome/browser/, so the include list will be much more manageable and
maintainable than an exclude list.
BUG=156699
Review URL: https://chromiumcodereview.appspot.com/11361056
git-svn-id: http://src.chromium.org/svn/trunk/src/build@165802 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
When chromoting resources were converted from messages.json to .grd format
incorrect branding was used. Beside that simplified how resources are
generated:
1. Now <if> is used to handle branded strings instead of generating grd file in build time
2. Removed resource_ids - ids are now specified in grd files.
BUG=158995
Review URL: https://chromiumcodereview.appspot.com/11275101
git-svn-id: http://src.chromium.org/svn/trunk/src/build@165605 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
- The java files had the issue that findbugd plugin need to find out, they
compiled with the same configuration as chrome for android's.
- The run_findbugs_plugin_tests.py runs the findbugs against the above Java
classes, and expects to find the same issues as those in expected_result.txt.
BUG=143971, 157970
Review URL: https://chromiumcodereview.appspot.com/11343057
git-svn-id: http://src.chromium.org/svn/trunk/src/build@165442 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
When setting a cookie's expiration time in the cookie store we need
to take into account any difference between the HTTP server and the
host machine's real time clock. This reverts 159685 which reverted 146616.
BUG=135131
TEST=net_unittests --gtest_filter=CookieMonster/CookieStoreTest/0.TestCookieDeletion
Review URL: https://chromiumcodereview.appspot.com/11339032
git-svn-id: http://src.chromium.org/svn/trunk/src/build@165323 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
This doesn't work yet without upstream protobuf changes,
but with this infrastructure in place it's going to be
easier to test further updates.
Google Chrome will of course use the bundled version,
there's no change here.
BUG=157155
TEST=none
Review URL: https://codereview.chromium.org/11231046
git-svn-id: http://src.chromium.org/svn/trunk/src/build@165257 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
Instead of hardcoding the list of qualified JNI parameters,
pass it as a parameter so that different modules can inject their
classes.
This is the first step in such decoupling; follow up will start splitting
the class_list.jni list closer to their modules.
BUG=158722
TEST=jni_generator_tests
Review URL: https://chromiumcodereview.appspot.com/11339013
git-svn-id: http://src.chromium.org/svn/trunk/src/build@165250 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
TARGET_PRODUCT and other parameters generated by lunch command is not
necessary any more since the build got switched to being based on
SDK/NDK. This CL lets the target architecture be passed from envsetup.sh.
Currently two arch's values are accepted: arm(default), x86.
TEST=Built successfully with both target architecture values - arm and x86
using following commands:
. build/android/envsetup.sh -> arm
. build/android/envsetup.sh -t arm -> arm
. build/android/envsetup.sh -t x86 -> x86
Other commands tested:
. build/android/envsetup.sh -h -> prints help
. build/android/envsetup.sh -t bogus -> prints help and stops
BUG=
Review URL: https://codereview.chromium.org/11260008
Patch from Jinsuk Kim <jinsukkim@google.com>.
git-svn-id: http://src.chromium.org/svn/trunk/src/build@165185 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
- findbugs_diff.py analyzes the org.chrome.* classes by calling findbug.py.
- findbugs.py is python lib, it calls the FindBugs by different configration.
The caller could configure the classes to analyze, filter, known_bugs,
whether rebaseline etc.
BUG=156116
Review URL: https://codereview.chromium.org/11273026
git-svn-id: http://src.chromium.org/svn/trunk/src/build@165024 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
This is not yet used, but helps lay the groundwork for building chrome/
targets for iOS.
This uses exclude-all-and-include since Chrome for iOS uses only a very
small portion of chrome/browser/ui/, so the include list will be much more
manageable and maintainable than an exclude list.
BUG=156699
Review URL: https://chromiumcodereview.appspot.com/11339010
git-svn-id: http://src.chromium.org/svn/trunk/src/build@164908 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
Several auxiliary tools used when building Chrome for iOS are generated via the
following two-step pattern: (1) compiling the executable with ninja, and (2)
copying the executable into a location that is shared with other projects.
Previously, these two steps were specified as actions in the same target.
However, as the ordering of multiple actions in one target is defined only by
inputs and outputs and the compilation action had no inputs/outputs set, the
copying action wasn't properly depending on the compilation action.
As it's challenging to set correct inputs for the ninja build, this CL
separates these actions into two targets in order to be able to specify that
the second action should not run until the first action finishes.
Review URL: https://chromiumcodereview.appspot.com/11301003
git-svn-id: http://src.chromium.org/svn/trunk/src/build@164743 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
The intention is to allow to build iOS Chrome/tests with asan=1, which is only possible with a custom Clang at the moment.
The resulting binaries can't be shipped to users, but can be used to debug memory corruptions.
Review URL: https://codereview.chromium.org/11273012
git-svn-id: http://src.chromium.org/svn/trunk/src/build@164619 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
blundell@chromium.org
mkosiba@chromium.org
bulach@chromium.org
cmp@chromium.org
michaelbai@chromium.org
stuartmorgan@chromium.org
hans@chromium.org
nileshagrawal@chromium.org
ilevy@chromium.org
kaiwang@chromium.org
sullivan@chromium.org
hbono@chromium.org
sergeyu@chromium.org
aberent@chromium.org
glider@chromium.org
pauljensen@chromium.org
phajdan.jr@chromium.org
frankf@chromium.org
yfriedman@chromium.org
marja@chromium.org
michaelbai@google.com
shashishekhar@chromium.org
mnaganov@chromium.org
jcivelli@chromium.org
ivankr@chromium.org
thakis@chromium.org
tfarina@chromium.org
msarda@chromium.org
chrisha@chromium.org
rohitrao@chromium.org
shouqun.liu@intel.com