In preparation to moving release tester to main waterfall,
add zip_step to release builder.
Also adding release trybot configs at same time.
Some configs are implicit by using bot_id substring match.
BUG=164995,167393
TBR=yaron
NOTRY=True
Review URL: https://chromiumcodereview.appspot.com/11975033
git-svn-id: http://src.chromium.org/svn/trunk/src/build@177357 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
We want certain Android specific files, like findbugs_known_bugs.txt, to only have deletions (not even modifications to existing lines). The presubmit check added in this CL checks that a certain list of files only have deletions.
BUG=165608
NOTRY=True
Review URL: https://chromiumcodereview.appspot.com/11583028
git-svn-id: http://src.chromium.org/svn/trunk/src/build@177241 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
The optimize code is based on pngslim. A few steps are omitted, but it runs all other processes. I'll check if it
worth fixing them (for example, advdef didn't make much difference)
Using -o option requires new third party program: optpng, pngout and advdef.
The script asks to install if they're not installed.
So for, I've got ~30% reduction in ash/resources (it's probably because pngslim was never run on this directory), I'd expect less
on other places where pngslim was run before.
Print results
BUG=150046
TEST=none
NOTRY=true
Review URL: https://chromiumcodereview.appspot.com/11905002
git-svn-id: http://src.chromium.org/svn/trunk/src/build@177202 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
This generates localized strings.xml files (e.g.
values-fr/strings.xml) from grd and xtb files at build time. This
means we no longer need to check in localized strings.xml files. Note:
the xtb files are empty until translations are available.
Benefits:
- 41 fewer extraneous results when grepping Java string IDs
- Switching from maintaining strings in strings.xml over to using a
grd file is One Trivial CL* away: just include English in the list
of languages for which we generate strings.xml files.
*Restrictions may apply
Originally landed as https://codereview.chromium.org/11659006/
This can be re-landed as of https://codereview.chromium.org/11880050/
BUG=167248
TBR=yfriedman@chromium.org,thakis,jam@chromium.org,cjhopman,shashishekhar@chromium.org
Review URL: https://codereview.chromium.org/11967005
git-svn-id: http://src.chromium.org/svn/trunk/src/build@177170 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
This removes unneeded gyp defines from envsetup. I still left the environment variables because some scripts (e.g. findbugs) still depend on them. I'll remove those usages and the environment variables separately.
Review URL: https://codereview.chromium.org/11886053
git-svn-id: http://src.chromium.org/svn/trunk/src/build@177169 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
The benchmarks first print results to stdout, then information about skipped /
failed page to stderr. The test runners also redirect both streams to the same
file. If stdout is not properly flushed, the stderr output might appear in the
middle of the stdout output, and this makes the log parser fail.
R=bulach
BUG=none
Review URL: https://codereview.chromium.org/11886071
git-svn-id: http://src.chromium.org/svn/trunk/src/build@177162 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
The test code was incorrectly counting the number of CPUs, and hence was only
setting performance mode on, at most, n-1 of them. This meant that the
results of the perf tests (at least the startup tests) depended on how Chrome
distributed itself between CPUs.
BUG=163336
Review URL: https://chromiumcodereview.appspot.com/11938002
git-svn-id: http://src.chromium.org/svn/trunk/src/build@177143 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
Add an option --unsupported to install-build-deps.sh which allows the
installation to be attempted on a system we don't support. Omit
mentioning this in the error, in the hope that anyone who can deal with
the fallout from this will find it in the script. Also, add GCEL
(Ubuntu-derived image used by Compute Engine) to the list of supported
systems.
BUG=
Review URL: https://codereview.chromium.org/11863012
git-svn-id: http://src.chromium.org/svn/trunk/src/build@176982 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
This brings the Linux build into line with the Windows and Mac builds,
where Breakpad is compiled in by default. This allows us to test
Breakpad on the trybots and buildbots.
It's still possible to omit Breakpad support using a Gyp option.
As with Windows and Mac, we don't want to enable Breakpad in Chromium
at run time by default (since that would spam the crash server, which
doesn't have symbols for Chromium builds anyway), so we put this
behind a run time flag. We also don't compile in debug info (-g) by
default.
We extend NaCl's Breakpad tests to be able to locate crash dumps on
Linux.
We add some "#ifdef GOOGLE_CHROME_BUILD"s to prevent Breakpad from
being enabled accidentally without the run time flag, but this is just
in case because there should be no GUI option for enabling stats/crash
reporting inside non-Chrome Chromium builds.
BUG=105778
TEST=breakpad_browser_process_crash_test in nacl_integration
Review URL: https://chromiumcodereview.appspot.com/10407058
git-svn-id: http://src.chromium.org/svn/trunk/src/build@176911 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
This is the client-side change for uploading the following
instrumentation test types:
androidwebview_instrumentation_tests
chromiumtestshell_instrumentation_tests
contentshell_instrumentation_tests
Actuall uploading of results will first be done
on a staging server.
BUG=150801
Review URL: https://codereview.chromium.org/11885010
git-svn-id: http://src.chromium.org/svn/trunk/src/build@176758 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
The code was making a call to android_commands.py, which
relied on a copy of adb existing in the path. The CQ
bot does not have third_party/android_tools, and in general
it seems advantageous to not require a full checkout for
syntax checks.
NOTRY=True
Review URL: https://chromiumcodereview.appspot.com/11883019
git-svn-id: http://src.chromium.org/svn/trunk/src/build@176723 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
This should move the last dependence on adb out of buildbot_functions. Also includes various other android buildbot fixes:
- Start logcat monitor before reboot command to catch JB crash.
- Rename bb_tests to bb_device_steps.
Review URL: https://codereview.chromium.org/11857014
git-svn-id: http://src.chromium.org/svn/trunk/src/build@176651 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
This should not affect upstream build configuration. This should only
affect build when building as part of the Android System build.
Disabling since we do not yet merge the necessary third_party
repositories so it is breaking downstream build.
dcommitted after all the bots have passed compile
BUG=161417
TBR=wjia@chromium.org
Review URL: https://codereview.chromium.org/11884010
git-svn-id: http://src.chromium.org/svn/trunk/src/build@176518 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
Usage: run_update_verification.py [options]
Performs semi-automated application update verification testing. When given
--save, it takes a snapshot of the application data on the device. (A dialog
on the device will prompt the user to grant permission to backup the data.)
Otherwise, it performs the update testing as follows: 1. Installs the |from-
apk|. 2. Restores the previously stored snapshot of application data given by
|app-data|. (A dialog on the device will prompt the user to grant permission
to restore the data.) 3. Verifies that |to-apk| cannot be installed side-by-
side. 4. Verifying that |to-apk| can replace |from-apk|.
Options:
-h, --help show this help message and exit
--package-name=PACKAGE_NAME
Package name for the application.
--save Save a snapshot of application data. This will be
saved as backup.db in the current directory.
--from-apk=FROM_APK APK to update from.
--to-apk=TO_APK APK to update to.
--app-data=APP_DATA Path to the previously stored application data
BUG=167778
Review URL: https://codereview.chromium.org/11672004
git-svn-id: http://src.chromium.org/svn/trunk/src/build@176218 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
ilevy@chromium.org
frankf@chromium.org
sivachandra@chromium.org
yfriedman@chromium.org
oshima@chromium.org
peter@chromium.org
newt@chromium.org
marja@chromium.org
aberent@chromium.org
skyostil@chromium.org
nileshagrawal@chromium.org
torne@chromium.org
phajdan.jr@chromium.org
mseaborn@chromium.org
cjhopman@chromium.org
frankf@google.com
bulach@chromium.org
kaiwang@chromium.org
kristianm@chromium.org
apatrick@chromium.org
boliu@chromium.org
wjia@chromium.org
tony@chromium.org
viettrungluu@chromium.org
eugenis@chromium.org
jln@chromium.org
kalman@chromium.org
smckay@chromium.org