We now consider the _by_url data important for histograms, and only print out
histograms one by one. So we don't need hacks in perf_tests_helper for printing
out a list of histograms (for which we don't any more know which page they refer to).
BUG=158323
NOTRY=true
Review URL: https://chromiumcodereview.appspot.com/11573008
git-svn-id: http://src.chromium.org/svn/trunk/src/build@172939 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
This improves SystemMonitor on Android by firing RESUME/SUSPEND events when the
Android main activity goes to foreground/background.
This lets the Android port use the same code path as other platforms to support
the close idle network connections functionnality.
SUSPEND events are now fired 1 minute after the main activity goes to
background.
Additionnally this CL cleans up ActivityStatus used by the Java side
SystemMonitor class. ActivityStatus was suffering from various refactorings and
was providing a counter intuitive interface with the Listener/StateListener
duality.
In particular it was possible to call SystemMonitor.onPause/Resume() as opposed
to onStateChange(). This could lead to SystemMonitor.getActivity() returning
null. The issue was raised while this CL was prepared.
BUG=164495
Review URL: https://codereview.chromium.org/11538008
git-svn-id: http://src.chromium.org/svn/trunk/src/build@172864 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
This generates the copy of R.java used to compile the library jar (formerly
done in gyp) and adds a new step to crunch image resources.
The imaging crunching step fixes the link preview 9-patch drawing artifact,
among other benefits.
BUG=163602
Review URL: https://codereview.chromium.org/11516024
git-svn-id: http://src.chromium.org/svn/trunk/src/build@172655 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
The build/android/ scripts could not run the breakpad_unittests script
properly for two reasons:
- First, a special helper binary needs to be pushed to the device.
This patch modifies test_package.py to take care of that.
- Second, the GTest result value file is stored in /data/local/tmp/
for executable tests, instead of /sdcard/, as assumed by
test_package_executable.py.
BUG=165355
Review URL: https://chromiumcodereview.appspot.com/11536006
git-svn-id: http://src.chromium.org/svn/trunk/src/build@172513 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
Currently we are unable to plant our test root certificate in Android trust store to run our certificate verification tests against it.
The patch adds custom test trust store to the java backend, allowing to run the certificate verification tests against custom set of root certificates.
The actual installation of our test root certificate is being done by TestRootCerts class, consistently with what we do on other platforms.
BUG=147786
Review URL: https://chromiumcodereview.appspot.com/11316210
git-svn-id: http://src.chromium.org/svn/trunk/src/build@172488 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
Print an info message giving the temperature at which the OMAP decided to
thermally throttle.
Print an info message giving the current OMAP temperature every time there is
a check for thermal throttling.
Include the device serial number in all thermal throttling messages.
BUG=164989
Review URL: https://chromiumcodereview.appspot.com/11499010
git-svn-id: http://src.chromium.org/svn/trunk/src/build@172357 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
This script allows to:
1. run all telemetry tests in N devices as a single step in the buildbot.
Each run will save its results in the buildbot.
2. A separate step will then essentially print them.
This is very similar mechanism to the existing one downstream, which will be deprecated
and replaced by this as soon as it lands.
BUG=163503
TEST=build/android/bb_run_sharded_steps.py
Review URL: https://chromiumcodereview.appspot.com/11308344
git-svn-id: http://src.chromium.org/svn/trunk/src/build@172044 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
This patch adds a new .gypi file that allows one to generate Java source
files by parsing template files with the host C pre-processor. The main
use case is the ability to generate Java sources defining constants matching
their C/C++ counterparts.
This is actually a generalisation of the technique that was used in net/net.gyp
to generate a NetError.java source mirroring the definitions found in
net/base/net_error_list.h
BUG=none
Review URL: https://chromiumcodereview.appspot.com/11415152
git-svn-id: http://src.chromium.org/svn/trunk/src/build@172041 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
AppCacheEnabled is mapped onto WebPreferences.application_cache_enabled, which goes directly into WebKit Settings.
AppCachePath is only used as a flag to enable AppCache. We can't make use of the full path given, because in Chromium the Application Cache directory lives inside the browser context (profile).
The tests added trigger a DCHECK in disk cache, unless the profile is empty when the test starts. This makes impossible to run them both now, so only one of them is enabled for now.
Android CTS tests WebSettings.testAppCache{Disabled|Enabled} are passing with this patch.
Review URL: https://chromiumcodereview.appspot.com/11411229
git-svn-id: http://src.chromium.org/svn/trunk/src/build@171074 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
The Skia build depends on arm_neon_optional=1 being defined in GYP_DEFINES
to enable dynamic NEON support. It looks like this option was lost in
translation during the upstreaming of build/android/.
Note that this won't fix crbug.com/161834, i.e. on JB and higher, the
sandboxing currently prevents the CPU feature detection from working, but
it's a first step in the right direction (it fixes the code for ICS devices
though).
BUG=164002
R=joth@chromium.org,torne@chromium.org,djsollen@chromium.org,tomhudson@chromium.org,reed@chromium.org
Review URL: https://chromiumcodereview.appspot.com/11419299
git-svn-id: http://src.chromium.org/svn/trunk/src/build@171001 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
This fixes the following issue:
- TestSharder.SetupSharding() in run_java_tests.py wasn't calling
the super class' SetupSharding() method which kills host_forwarder. The call
to Forwarder.KillHost() was moved to RunShardedTest() which isn't supposed to
be overridden. This should be more robust.
Additionally in case '$ host_forwarder kill-server' failed for any reason,
Forwarder.KillHost() now falls back to pkill.
BUG=163036
Review URL: https://chromiumcodereview.appspot.com/11421149
git-svn-id: http://src.chromium.org/svn/trunk/src/build@170437 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
The URLFetcherDownloadProgressTest assumes that the file being
downloaded is present on the machine runing the tests. This is
not true on Android, where a remote server is used instead.
Access to the file before starting the download is not necessary
to verify the consistency of data reported in download progress
callbacks, which is the aim of the test.
The patch checks if the total download size reported in the
callback remains constant, consistently with the way in which
download progress already is being verified.
BUG=161242
Review URL: https://chromiumcodereview.appspot.com/11308035
git-svn-id: http://src.chromium.org/svn/trunk/src/build@170206 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
On Android the ashmem API is used to deal with shared memory. This API doesn't
provide any way to open a memory region created by another process for security
reasons. The only way to share memory on Android is to share the underlying
file descriptor between processes.
This can be accomplished by:
- Creating a new shared memory region in a process. Note that this region can
be anonymous (i.e. the string provided to ashmem_create_region() can be
empty).
- Forking and keeping open both in the parent and child processes the file
descriptor corresponding to the previously created memory region.
- Doing an mmap() in both processes (nothing special here).
The unit test was deadlocking (stuck in the while loop in the child process)
since the call to CreateNamed() wasn't opening the existing shared memory
region (created by the parent process) but was actually creating a new shared
memory region.
This means that the two processes were actually seeing different memory
regions.
Since this also works on POSIX platforms, the unit test was modified to follow
this strategy on all POSIX systems (including Android). On Windows the old
strategy (using non-anonymous shared memory) is still used.
BUG=136720
Review URL: https://chromiumcodereview.appspot.com/11299159
git-svn-id: http://src.chromium.org/svn/trunk/src/build@169662 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
This appears to break Chrome for Android perf tests, in addition to
the kraken benchmark upstream.
-------------------
Log output:
Traceback (most recent call last):
File "clank/build/run_crossbrowser_perftests.py", line 1429, in <module>
sys.exit(main(sys.argv))
File "clank/build/run_crossbrowser_perftests.py", line 1416, in main
passed &= chrome_benchmarks.Run()
File "/usr/local/google/b/build/slave/soju-official-perf-noflash-clankium/build/src/clank/build/../../build/android/pylib/base_test_runner.py", line 79, in Run
return self.RunTests()
File "clank/build/run_crossbrowser_perftests.py", line 329, in RunTests
return self.RunCrossBrowserPerfTests(options.filter, options.force_disabled)
File "clank/build/run_crossbrowser_perftests.py", line 379, in RunCrossBrowserPerfTests
passed &= bool(RunTheTest())
File "clank/build/run_crossbrowser_perftests.py", line 368, in RunTheTest
return test_fn()
File "clank/build/run_crossbrowser_perftests.py", line 1222, in PaintBlankBenchmark
timeout)
File "clank/build/run_crossbrowser_perftests.py", line 426, in RunPaintBenchmarkHelper
timeout=timeout))
File "/usr/local/google/b/build/slave/soju-official-perf-noflash-clankium/build/src/clank/build/perf_test_runner.py", line 629, in RunPerfTest
result, units, result_type=result_type)
File "/usr/local/google/b/build/slave/soju-official-perf-noflash-clankium/build/src/clank/build/../../build/android/pylib/perf_tests_helper.py", line 127, in PrintPerfResult
output += '\nAvg %s: %f%s' % (measurement, avg, units)
TypeError: float argument required, not str
-------------------
Original commit:
The previous version was printing out only the first histogram.
BUG=
Review URL: https://codereview.chromium.org/11413144TBR=marja@chromium.org
Review URL: https://codereview.chromium.org/11418165
git-svn-id: http://src.chromium.org/svn/trunk/src/build@169510 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
This lets device_forwarder be controlled (started and killed) like
host_forwarder (see r167167).
This has the main benefit of moving the setup/tear down complexity from the
Python Forwarder wrapper code to the forwarder itself so that various clients
(including WebKit) can use forwarder2 more easily (e.g. no need to use pexpect
anymore (which is not available in WebKit)).
This implied a refactoring in the Daemon class so that its clients don't have
to duplicate the socket-related code.
Review URL: https://chromiumcodereview.appspot.com/11360248
git-svn-id: http://src.chromium.org/svn/trunk/src/build@169334 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
The WebView build doesn't have third_party/android_tools/ndk with the
added gyp file, but the cpufeatures code has already been built as part
of the system. Introduce a .gypi that can be included to get the
appropriate dependency for the current build type.
BUG=
Review URL: https://codereview.chromium.org/11417114
git-svn-id: http://src.chromium.org/svn/trunk/src/build@169026 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
The NoCache test for the PAC fetcher verifies that an attempt to
fetch a PAC script fails once the server is killed, thus assuring
that PAC files are not cached.
Due to the device-server / port forwarding layout of running
gtests on Android, the specific error being returned by the
fetch attempt is "Connection reset by peer" rather than
"Connection refused". This patch takes this into consideration.
BUG=161763
Review URL: https://chromiumcodereview.appspot.com/11412070
git-svn-id: http://src.chromium.org/svn/trunk/src/build@168805 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
This adds Java resources directly to the content and chrome folders and starts
accessing them through the Java classes org.chromium.content.R and
org.chromium.chrome.R instead of using AppResource.
A following CL will remove these resources from ContentShell and other build
targets that currently provide duplicates of these resources. The following CL
will also remove remaining references to AppResource.
This is the second of three CLs to replace AppResource with R:
1. http://codereview.chromium.org/11363150 - Support Java resources within content
2. http://codereview.chromium.org/11360207 - Add Java resources to content and chrome
3. http://codereview.chromium.org/11377117 - Remove AppResource and unneeded resources
BUG=136704
Review URL: https://chromiumcodereview.appspot.com/11360207
git-svn-id: http://src.chromium.org/svn/trunk/src/build@168759 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
In Android 4.2, pinch gestures send both pinch events (for the
zoom-in/out part of the pinch) and scroll events (for double-finger
panning). The previous logic in LayerTreeHostImpl created a pan from
the pinch event, resulting in 2x overpanning on Android 4.2.
In order to have compatible gesture generation in older Android versions as
well, I copy-pasted the latest Android GestureDetector.java file into the
Chromium tree and use that instead of the system file.
BUG=161909
Review URL: https://chromiumcodereview.appspot.com/11299083
git-svn-id: http://src.chromium.org/svn/trunk/src/build@168721 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
The WebView will eventually need to be built for multiple target
architectures. Prepare for this by passing --suffix .arm to gyp when
generating the makefiles, and including an architecture-specific
makefile at the top level. Also, remove the hardcoding of arm as the
target architecture in envsetup.sh.
The previous change I made to .gitignore to only ignore *.host.mk and
*.target.mk instead of *.mk has been reverted in favour of just
specifically un-ignoring files called Android.mk (which are
handwritten).
BUG=
Review URL: https://codereview.chromium.org/11416036
git-svn-id: http://src.chromium.org/svn/trunk/src/build@168506 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
This provides support for android-style resource folders in content and other
non-apk Java targets. The AppResource hack can then be removed shortly.
Details: while building a non-apk target (e.g. chromium_content.jar), we
generate an R.java file with non-final constants and in the appropriate Java
package (e.g. org.chromium.content.R) using the resources in the target (e.g.
content/public/android/java/res). This R.java is used to produce the jar, but is
not included in the jar itself.
When we later build an apk, we merge the resources from the apk (e.g.
org/chromium/content_shell/res) with the resources from the non-apk targets it
depends on (e.g. content/public/android/java/res). A new R.java is generated
using the merged resources with the correct mapping from resources to integer
IDs. This R.java file is copied into each needed package (e.g.
org.chromium.content.R and org.chromium.content_shell.R) and included in the
apk.
This is the first of three CLs to replace AppResource with R:
1. http://codereview.chromium.org/11363150 - Support Java resources within content
2. http://codereview.chromium.org/11360207 - Add Java resources to content and chrome
3. http://codereview.chromium.org/11377117 - Remove AppResource and unneeded resources
BUG=136704
Review URL: https://codereview.chromium.org/11363150
git-svn-id: http://src.chromium.org/svn/trunk/src/build@168283 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
This adds a new extensions::ImageLoader class, which mostly serves the same purpose as ImageLoadingTracker, but with some differences. It currently doesn't do any caching, and it uses callbacks instead of a delegate to pass the loaded image back to the caller. This should make this new class much nicer to use.
Also ported some ILT usage to the new ImageLoader class.
BUG=141673
Review URL: https://chromiumcodereview.appspot.com/11027044
git-svn-id: http://src.chromium.org/svn/trunk/src/build@168155 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
Previously, we had to keep this name in sync in multiple places, the
"fake" xxx_java target and in sdk-targets.xml. Instead, it should be set
only in java_apk.gypi and then passed along to each of the places that
we were specifying it before.
Also, delete unused 'output' block and unneeded xxx_java dependencies.
BUG=
Review URL: https://chromiumcodereview.appspot.com/11363131
git-svn-id: http://src.chromium.org/svn/trunk/src/build@168148 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
This patch changes build/android/envsetup.sh to detect that the user
is running on a 32-bit host system, and print an error message
in this case, since a full build will fail (linker runs out of memory,
because the generated files are too large).
This can be overriden with the new --try-32 flag, in case someone
really wants to try a build. This would only be useful if one
needs to rebuild a "small" target, not do a complete build.
BUG=
Review URL: https://chromiumcodereview.appspot.com/11366243
git-svn-id: http://src.chromium.org/svn/trunk/src/build@168009 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
In order to avoid duplicating most of the run-tests-on-devices logic, make
sure that the Android scripts are able to be usable from a WebKit checkout.
Two flags have been added for this: --webkit, which is necessary as a file's
path on the host and device are not per se equal anymore, and --out-directory,
accepting a path as it's not always in the Chromium source directory.
BUG=
Review URL: https://chromiumcodereview.appspot.com/11312239
git-svn-id: http://src.chromium.org/svn/trunk/src/build@167999 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
The cacheinvalidation_java target is also added to build/all_android.gyp to
ensure it is always built since nothing currently depends on it upstream.
When all of Android-specific sync code is upstreamed, a target for sync
should be used instead of cacheinvalidation.
BUG=158382
Review URL: https://chromiumcodereview.appspot.com/11146005
git-svn-id: http://src.chromium.org/svn/trunk/src/build@167746 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
1. Move chrome/browser/component/web_contents_delegate_android to
content/components/web_contents_delegate_android.
2. Rename package org.chromium.chrome.browser.component.
web_contents_delegate_android to org.chromium.content.components.
web_contents_delegate_android.
3. Remove shouldOverrideUrlLoading from WebContentsDelegateAndroid
interface, which is no longer required.
I will follow up with a second change to completely remove
chrome/browser/component/web_contents_delegate_android once
external dependencies on it have been removed.
BUG=157575
Review URL: https://chromiumcodereview.appspot.com/11365199
git-svn-id: http://src.chromium.org/svn/trunk/src/build@167670 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
This changes forwarder2 to support both test-server spawner and HTTP server
forwarding.
The main issue was that the device_forwarder was killed when instantiating a
second Forwarder (Python object).
Test server based unit tests require two device-to-host redirections, one for
the test server spawner and one for the HTTP server.
The port used by the HTTP server is allocated dynamically which means that we
can't know the full forwarding configuration before we spawn a HTTP server
(through the test server spawner).
This CL changes the forwarder to let it forward new ports while it is running
by making host_forwarder a daemon. This is similar to how ADB works.
This also means that a single host_forwarder process (daemon) can now handle
multiple devices.
BUG=146979
Review URL: https://chromiumcodereview.appspot.com/11269036
git-svn-id: http://src.chromium.org/svn/trunk/src/build@167167 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
1. Move C++ source from chrome/browser/component/navigation_interception
to content/components/navigation_interception.
2. Change the namespace from navigation_interception:: to content::
3. Change Java package from org.chromium.chrome.browser.components.
navigation_interception to org.chromium.content.components.
navigation_interception.
I will follow up with another patch to completely remove
chrome/browser/component/navigation_interception once external
dependencies have been updated to use the component at its new
component
BUG=157575
Review URL: https://chromiumcodereview.appspot.com/11293017
git-svn-id: http://src.chromium.org/svn/trunk/src/build@166883 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
A superset of this change was needed to fix a bug downstream. Note that the bug
doesn't exist upstream since it was caused by a piece of code not upstreamed.
Therefore the only purpose of this change is to decrease the upstream vs
downstream diff.
Review URL: https://chromiumcodereview.appspot.com/11365147
git-svn-id: http://src.chromium.org/svn/trunk/src/build@166699 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
Currently when tests time out, we retry them but still mark the step as
a warning, which does not cause a step failure.
We should report a failure when tests time out. Also adding more stats
on how many tests we were supposed to run and how many we failed to run.
BUG=
Review URL: https://chromiumcodereview.appspot.com/11363088
git-svn-id: http://src.chromium.org/svn/trunk/src/build@166132 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
It looks like this made win extract_build fail.
Adds the ability for devs/troopers/etc. to set 'landmines' in the tree so that
the build will selectively clobber when a builder moves over a revision with such
a change.
This cl has an basis landmines.py, and hooks the clobber mechanism to the android
build scripts.
The relevant cl which implements this for
compile.py is here: https://chromiumcodereview.appspot.com/11234013/
I'm planning to also implement an informational invocation for gclient to let devs know
about any potential landmines so they can decide if they need to clobber.
R=cmp,maruel@chromium.org
BUG=121897
Review URL: https://chromiumcodereview.appspot.com/11175016TBR=iannucci@chromium.org
Review URL: https://codereview.chromium.org/11293111
git-svn-id: http://src.chromium.org/svn/trunk/src/build@166105 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
Adds the ability for devs/troopers/etc. to set 'landmines' in the tree so that
the build will selectively clobber when a builder moves over a revision with such
a change.
This cl has an basis landmines.py, and hooks the clobber mechanism to the android
build scripts.
The relevant cl which implements this for
compile.py is here: https://chromiumcodereview.appspot.com/11234013/
I'm planning to also implement an informational invocation for gclient to let devs know
about any potential landmines so they can decide if they need to clobber.
R=cmp,maruel@chromium.org
BUG=121897
Review URL: https://chromiumcodereview.appspot.com/11175016
git-svn-id: http://src.chromium.org/svn/trunk/src/build@166085 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
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
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
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
SkCanvasVideoRenderer will be used for rendering YUV video streams by
the software compositor. To avoid circular dependencies cc/ cannot depend
on webkit/ hence the move.
Also changed the interface of SkCanvasVideoRenderer::Paint to accept
gfx::RectF instead of gfx::Rect. The gfx::Rect was converted to a
floating point SkRect anyway and we actually use the floating point
version from the software compositor.
BUG=150016
Review URL: https://chromiumcodereview.appspot.com/11234071
git-svn-id: http://src.chromium.org/svn/trunk/src/build@163829 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
- fix some "forwarder" issues on chrome_remote_control.
- adds a "platform" interface to crc so that tests can grab stats from
the platform, where possible.
- integrates "surface stats collector" with scrolling tests.
BUG=155678,11187036,138479
TEST=./tools/perf/run_tests --browser=android-chrome testScrolling
Review URL: https://chromiumcodereview.appspot.com/11187036
git-svn-id: http://src.chromium.org/svn/trunk/src/build@163361 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
yfriedman@chromium.org
jcivelli@chromium.org
frankf@google.com
mnaganov@chromium.org
marja@chromium.org
jknotten@chromium.org
nileshagrawal@chromium.org
fischman@chromium.org
pliard@chromium.org
tonyg@chromium.org
newt@chromium.org
digit@chromium.org
ppi@chromium.org
aberent@chromium.org
aruslan@chromium.org
bulach@chromium.org
shashishekhar@chromium.org
dtrainor@chromium.org
ilevy@chromium.org
jamesr@chromium.org
michaelbai@chromium.org
tfarina@chromium.org
dfalcantara@chromium.org
peter@chromium.org
torne@chromium.org
mkosiba@chromium.org
aelias@chromium.org
mek@chromium.org
cjhopman@chromium.org
skyostil@chromium.org
nyquist@chromium.org
iannucci@chromium.org
frankf@chromium.org
cramya@chromium.org
eugenis@chromium.org
tedchoc@chromium.org
pkotwicz@chromium.org
vandebo@chromium.org
kaiwang@chromium.org
pauljensen@chromium.org
michaelbai@google.com
shouqun.liu@intel.com
yongsheng.zhu@intel.com
skaslev@chromium.org