Adds new frame-level service with one initial method to handle host zoom
level.
This moves zoom level supply from async_resource_handler.cc to being a
request made when render_frame_impl handles a willSendRequest.
The goal of this change is to remove the dependency of
content/browser/loader on the rest of content/browser in particular
here, removing the use of c/b/host_zoom_map_impl.h in
content/browser/loader/async_resource_handler.cc.
BUG=598073,609607
CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:linux_site_isolation
Review-Url: https://codereview.chromium.org/1964273002
Cr-Original-Commit-Position: refs/heads/master@{#394547}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: 68c6f2ce16d9807b5cb82679099c82c40f39e911
Currently, Java exceptions hit while running native tests -- e.g. on JNI link
failure -- are lost to the logcat. This surfaces them to the test runner's
stdout.
BUG=
Review-Url: https://codereview.chromium.org/1982493002
Cr-Original-Commit-Position: refs/heads/master@{#393921}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: 6cdb933c8d2c4cadbf842fbb3ceb9cecd0f70920
Previously, we were only processing resources on aapt or sdk jar _path_
change.
This also removes an unrelated debug print statement.
BUG=603138
Review-Url: https://codereview.chromium.org/1967153002
Cr-Original-Commit-Position: refs/heads/master@{#392957}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: a211f7633c4dc0f2b1fb1c8a40040e84e9568d47
Reason for revert:
Seemingly breaks incremental builds.
Original issue's description:
> Add directory option for JUnit coverage files.
>
> Added runtime option --coverage-dir to let the users decide where to store
> coverage.ec.
>
> BUG=608072
>
> Committed: https://crrev.com/de08f6f711ebd74fe493584e0694bcce51693318
> Cr-Commit-Position: refs/heads/master@{#392727}
TBR=mikecase@chromium.org,hzl@google.com
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=608072
Review-Url: https://codereview.chromium.org/1973503002
Cr-Original-Commit-Position: refs/heads/master@{#392908}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: 0b730799f2f2f2d9d07b75f3fadd2ed387336a02
Some Android libraries have started including R.class in their jar
files, so they need to be stripped before dexing.
BUG=585576
Review-Url: https://codereview.chromium.org/1952153002
Cr-Original-Commit-Position: refs/heads/master@{#392620}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: dd2adf0e9718ec28f46dde4c09e379c9df82065e
The removed exception is raised when I am testing link to a jar file which
extract from a .aar file through an action. For example:
action("extract_aar") {
script = ".."
...
outputs = ["$root_out_dir/test.jar",]
}
android_java_prebuilt("test_prebuilt") {
jar_path = "$root_out_dir/test.jar"
deps = [":extract_aar"]
}
It looks like the exception is unnecessary anymore so removing it.
BUG=NONE
Review-Url: https://codereview.chromium.org/1929163003
Cr-Original-Commit-Position: refs/heads/master@{#391586}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: 01ec845c3abedb6e8b279386577e521e0e43e9b8
Changes since last one:
SiteSettingsPreferencesTest.testBackgroundSyncPermission now
named as a helper instead of annotated as a test.
TBR=jbudorick@chromium.org,sgurun@chromium.org,yfriedman@chromium.org,mathp@chromium.org
BUG=601464
Review-Url: https://codereview.chromium.org/1950793002
Cr-Original-Commit-Position: refs/heads/master@{#391421}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: 01c2d6a9bdc61d422d8af9589ca0a0830d853ec1
The documentation for forward_variables_from specifies that it will give an error if the variable already exists in the target scope. But this was not implemented. Instead, the value would be silently overwritten.
This change implements the error, and fixes the times this happens in the Linux and Android builds.
Review-Url: https://codereview.chromium.org/1943583002
Cr-Original-Commit-Position: refs/heads/master@{#391136}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: 0785c950dce7221b10c21e911795e181076b90db
Disabling the test suite on ASAN to fix the bot.
The unit_tests_apk was introduced as a followup to internal renaming here:
https://codereview.chromium.org/1924893004
Unfortunately, the internal ASAN recipe does not support the test suite named as
"unit_tests_apk". It tries to run:
out/Debug/bin/run_unit_tests_apk
And fails with "No such file or directory". What ran successfully before:
out/Debug/bin/run_unit_tests
Running the internal recipe has some pitfalls on the way (see
http://crbug.com/607879), so just making things greener for now.
BUG=607850
Review-Url: https://codereview.chromium.org/1934573002
Cr-Original-Commit-Position: refs/heads/master@{#390633}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: 1d0e5bdab075461e4a66cad4a250d67ad1d37fa7
We used to add "_apk" to all targets from this list in the internal waterfall.
With a recent change by mikecase@ we no longer do that.
It works for most targets, but not for "unit_tests", which does not exist in GN.
This change would need to be reverted if we decide to switch back to GYP, but
it is unlikely to happen.
BUG=607455
Review-Url: https://codereview.chromium.org/1924893004
Cr-Original-Commit-Position: refs/heads/master@{#390342}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: 9954a78c165554ffed0a978c5b84738f5fa83531
After setting emma_coverage as true, and then run JUnit testcases, code
coverage information will be stored in coverage.ec. In order to read
coverage.ec file, you will need to find the corresponding <name>.em file
in out-gn/Debug and then merge the .em and .ec file into a txt or html.
BUG=604900
Review URL: https://codereview.chromium.org/1913593002
Cr-Original-Commit-Position: refs/heads/master@{#389902}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: 071f7c486154a89e15c8b796a8bd0f64573a7096
Before we only make sure that list of test cases are not None, but then
we realise that list of test cases should not be empty too, since
sometimes when devices fail to list tests, they will not return None,
but will return an empty list.
BUG=585585
Review URL: https://codereview.chromium.org/1915273002
Cr-Original-Commit-Position: refs/heads/master@{#389576}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: 3d73e44f7177fe1dbb6e868120b985a6c9fb8a30
Contains fix for ui_base_tests not having data set correctly for android.
TBR=sgurun@chromium.org,vollick@chromium.org,dpranke@chromium.org,jochen@chromium.org,apacible@chromium.org
NOTRY=true
BUG=589318
CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel
Review URL: https://codereview.chromium.org/1916503002
Cr-Original-Commit-Position: refs/heads/master@{#389470}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: e41ae190dadf81f1561c8cdfd8b308b213817210
Now uses gen.runtime rather than gen to be included by
builder/tester configurations.
TBR=sgurun@chromium.org,vollick@chromium.org,dpranke@chromium.org,jochen@chromium.org,agrieve@chromium.org
NOTRY=true
BUG=589318
Review URL: https://codereview.chromium.org/1914573002
Cr-Original-Commit-Position: refs/heads/master@{#389148}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: 5d205baf70287fec693da0166aa7aa8051b5985e
Tests use write_runtime_deps to have GN write out all runtime_deps, then
use a new script "generate_isolate.py" to filter the files and create a
.isolate.
TBR=vollick
BUG=589318
CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel
Review URL: https://codereview.chromium.org/1904823003
Cr-Original-Commit-Position: refs/heads/master@{#389105}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: 964da0f3923afb10a52dfe81484d7f3dcb18bad6
Currently, the package_info used by the test apk is looked up by
by looking at the test_apk package in the list of package_infos.
Instead, we can just look at the package entries in the list
of package_infos and compare it to the package of the apk_under_test.
This makes things much nicer, when for instance you have multiple
test apks targeting the same package.
BUG=
Review URL: https://codereview.chromium.org/1894233002
Cr-Original-Commit-Position: refs/heads/master@{#388042}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: 9454d5d5b562cce1186b398d6afe9cf3b42c08a1
Reason for revert:
Breaks the MogoTests due to this error.
AttributeError: 'NoneType' object has no attribute 'GetPackageName'
Original issue's description:
> [Android] Get package_info by using apk_under_test package.
>
> Currently, the package_info used by the test apk is looked up by
> by looking at the test_apk package in the list of package_infos.
> Instead, we can just look at the package entries in the list
> of package_infos and compare it to the package of the apk_under_test.
>
> This makes things much nicer, when for instance you have multiple
> test apks targeting the same package.
>
> BUG=
>
> Committed: https://crrev.com/f6c372aea4a4c79598b9414a9049b7ac5f659f2e
> Cr-Commit-Position: refs/heads/master@{#387943}
TBR=agrieve@chromium.org,rnephew@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=
Review URL: https://codereview.chromium.org/1900873002
Cr-Original-Commit-Position: refs/heads/master@{#387996}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: 56023c5c64b3c0af9c701b74e33e1f1e00f884eb
scottmg
hzl
jbudorick
agrieve
rnephew
yolandyan
sanfin
bshe
mathp
brettw
pasko
stip
penghuang
apacible
schenney
svaldez
bpastene
mikecase
tedchoc