This patch makes it possible to use glob-style gtest filters with
the content browser tests. An example of such a filter is
WebGLConformanceTest.*, which should cause all the WebGL conformance
tests to be run.
Previously the gtest filter was passed directly to the test executable,
causing it to run all matching tests successively in the same process.
Normally this would be fine, but with content browsertests we must run
each test in a fresh process to avoid issues with double initialization.
The fix is to expand the filter to a flat list of tests in the test
dispatcher. After this, the tests are sharded and run in exactly the
same way as when no gtest filter is provided.
BUG=138226
Review URL: https://chromiumcodereview.appspot.com/14882007
git-svn-id: http://src.chromium.org/svn/trunk/src/build@204680 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
- Rename ContentVideoViewContextDelegate to ContentVideoViewClient, instead of having the getContext() method, passing the context to ContentVideoView when it is created.
- Add getContentVideoViewClient method in ContentViewClient, so it will be created when it actually used.
BUG=http://b/8315237
Review URL: https://chromiumcodereview.appspot.com/13669003
git-svn-id: http://src.chromium.org/svn/trunk/src/build@204353 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
Removes check install step and moves it into the device status check. This will allow us to examine Android install speeds, which have recently caused timeout problems when installing large APK's. Unlike the original CL, low install speed only causes a warning (i.e. does not fail the step). The step fails if the battery of an online device is less than 5%.
BUG=230970, 224004, 242237
---------------------------------------------------
Original CL:
Move CheckInstall to device status and fail on low install speed and battery.
Removes the recently added CheckInstall step and moves the checking to the
device status check step. Recently, devices will install very slowly causing
tests to fail with device problems. We have also seen battery issues. The new
device status check step will fail if any devices install unreasonably slow
(i.e. < 800 KB/s) or have critically low battery level (i.e. < 5%).
BUG=230970, 224004, 242237
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=203587
Review URL: https://chromiumcodereview.appspot.com/16110005
git-svn-id: http://src.chromium.org/svn/trunk/src/build@204013 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
Broke android tests.
> Move CheckInstall to device status and fail on low install speed and battery.
>
> Removes the recently added CheckInstall step and moves the checking to the
> device status check step. Recently, devices will install very slowly causing
> tests to fail with device problems. We have also seen battery issues. The new
> device status check step will fail if any devices install unreasonably slow
> (i.e. < 800 KB/s) or have critically low battery level (i.e. < 5%).
>
> BUG=230970, 224004, 242237
>
> Review URL: https://chromiumcodereview.appspot.com/16110005TBR=navabi@google.com
Review URL: https://codereview.chromium.org/16299003
git-svn-id: http://src.chromium.org/svn/trunk/src/build@203594 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
Removes the recently added CheckInstall step and moves the checking to the
device status check step. Recently, devices will install very slowly causing
tests to fail with device problems. We have also seen battery issues. The new
device status check step will fail if any devices install unreasonably slow
(i.e. < 800 KB/s) or have critically low battery level (i.e. < 5%).
BUG=230970, 224004, 242237
Review URL: https://chromiumcodereview.appspot.com/16110005
git-svn-id: http://src.chromium.org/svn/trunk/src/build@203587 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
There's no reason for the webkit user_agent target to be included from
webkit_support.gyp, doing so just makes life really confusing and makes it
easier to accidentally introduce gyp cycles. This makes webkit_user_agent.gyp
a normal standalone gyp file.
BUG=245477
Review URL: https://chromiumcodereview.appspot.com/15709006
git-svn-id: http://src.chromium.org/svn/trunk/src/build@203493 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
The main reason for making this change is the fact that when pulling
Chromium and Blink code into Android, we have to make automatic changes
to the repository (for example, for generating *.mk files), and the Blink
commit we have as HEAD doesn't match any public commit in the main
Blink repo. While via the LASTCHANGE file we could report a publicly
visible revision.
Also, the way webkit_version.h header is generated now appears to be silly.
First, it doesn't leverage enough existing tools. Second, as it is noted in
webkit_user_agent.gypi, it is broken for incremental builds.
Review URL: https://chromiumcodereview.appspot.com/14973005
git-svn-id: http://src.chromium.org/svn/trunk/src/build@203387 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
This code is simple/test/mock implementations of APIs to use in DumpRenderTree,
webkit_unit_tests, and various other bits of unit test code around the codebase.
Nothing here is used for test_shell since there is no test_shell any more.
This moves the code to webkit/support/ along with the rest of DRT/w_u_t support
code. Hopefully we'll be able to delete most of this soon along with
DumpRenderTree. In the meantime this simplifies webkit/
R=darin@chromium.org
Review URL: https://codereview.chromium.org/15946006
git-svn-id: http://src.chromium.org/svn/trunk/src/build@203242 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
We don't have any jarjar rules yet, but add the empty file now in order
that the downstream build can enable jarjar. This way, when rules are
added later it will just work, instead of breaking the downstream build
temporarily.
Also, make sure that when a jarjar rule file is being used, it's
considered as an input to the JNI generator step, to make sure the JNI
header files get regenerated when the rules change.
BUG=
Review URL: https://chromiumcodereview.appspot.com/15888011
git-svn-id: http://src.chromium.org/svn/trunk/src/build@203141 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
frankf@chromium.org
sivachandra@chromium.org
groby@chromium.org
kkimlabs@chromium.org
jochen@chromium.org
bulach@chromium.org
cpu@chromium.org
scottmg@chromium.org
bshe@chromium.org
skyostil@chromium.org
scherkus@chromium.org
dpranke@chromium.org
michaelbai@chromium.org
thestig@chromium.org
phajdan.jr@chromium.org
xians@chromium.org
navabi@google.com
adamk@chromium.org
pasko@chromium.org
thakis@chromium.org
ilevy@chromium.org
szager@chromium.org
justinlin@chromium.org
tfarina@chromium.org
glider@chromium.org
cmp@chromium.org
pkasting@chromium.org
jamesr@chromium.org
mnaganov@chromium.org
pan.deng@intel.com
dmazzoni@chromium.org
blundell@chromium.org
torne@chromium.org