- 13 Apr, 2020 28 commits
-
-
Koji Ishii authored
This patch changes |NGFragmentItems| to flexible array, saving the overhead of |Vector| and possible unused capacity. Bug: 982194 Change-Id: I824ab7cfba8e707a2e8d41e2d54cbd85dee6f111 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2142888Reviewed-by:
Yoshifumi Inoue <yosin@chromium.org> Reviewed-by:
Kent Tamura <tkent@chromium.org> Reviewed-by:
Ian Kilpatrick <ikilpatrick@chromium.org> Commit-Queue: Koji Ishii <kojii@chromium.org> Cr-Commit-Position: refs/heads/master@{#758461}
-
chromium-autoroll authored
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/3f138576af56..6124b5308bbe git log 3f138576af56..6124b5308bbe --date=short --first-parent --format='%ad %ae %s' 2020-04-13 devtools-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com Update DevTools DEPS. Created with: gclient setdep -r src/third_party/devtools-frontend/src@6124b5308bbe If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/devtools-frontend-chromium Please CC devtools-waterfall-sheriff-onduty@grotations.appspotmail.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md Bug: None Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com Change-Id: I34dc3242bf1934a17cefacae533cd41672b93b6d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2146854Reviewed-by:
chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#758460}
-
Johann authored
Use HeapMojoRemote wrapper so that Oilpan will GC the object. Bug: chromium:1049056 Change-Id: If487b9dd2ff48464691c300198efe6134d7aeba4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2143023 Commit-Queue: Johann Koenig <johannkoenig@google.com> Reviewed-by:
Kouhei Ueno <kouhei@chromium.org> Reviewed-by:
Mugdha Lakhani <nator@chromium.org> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Cr-Commit-Position: refs/heads/master@{#758459}
-
John Z Wu authored
This will help with manual testing in the shell app Change-Id: Ie331c62e08a1d1aeab9a5d9122df134a6aa29769 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2145683 Auto-Submit: John Wu <jzw@chromium.org> Reviewed-by:
Hiroshi Ichikawa <ichikawa@chromium.org> Commit-Queue: Hiroshi Ichikawa <ichikawa@chromium.org> Cr-Commit-Position: refs/heads/master@{#758458}
-
Tsuyoshi Horo authored
This syscall is required by CRYPTO_BUFFER of BoringSSL. Bug: 1050158 Change-Id: I3b14a263c81ab614005a8f879e64bf4b3634ad76 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2143884Reviewed-by:
Greg Kerr <kerrnel@chromium.org> Commit-Queue: Tsuyoshi Horo <horo@chromium.org> Cr-Commit-Position: refs/heads/master@{#758457}
-
Igor Makarov authored
- added .style.yapf file - reformat *.py files Bug: 1051750 Change-Id: I4d1e6054ce940d975710d8114f2f193304b554c2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2134236Reviewed-by:
-
John Z Wu authored
Change-Id: Iad60ec64d0633faac2083f5cdf9dfa67fc52ff0a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2143862 Auto-Submit: John Wu <jzw@chromium.org> Reviewed-by:
-
Jinsuk Kim authored
This CL adds a build target chrome/browser/tab:java and a dummy class file to get the build working. This will be used to keep the build green while a 2-side patch https://crrev.com/c/2102998 lands. The build target doesn't affect any upstream builds for now. Will be used for the downstream build only, and updated immediately to be a real target for the upstream. TBR=twellington@chromium.org Bug: 995903 Change-Id: I2941cc0066edc083981ee3e386a7225618a3789f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2146406Reviewed-by:
Jinsuk Kim <jinsukkim@chromium.org> Commit-Queue: Jinsuk Kim <jinsukkim@chromium.org> Cr-Commit-Position: refs/heads/master@{#758454}
-
Igor Makarov authored
- added .style.yapf file - reformat *.py files Bug: 1051750 Change-Id: I711a0c7f3676e6a423152ad02175ab7adb9260a8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2139815Reviewed-by:
-
chromium-autoroll authored
If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/fuchsia-sdk-chromium-autoroll Please CC cr-fuchsia+bot@chromium.org on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:fuchsia-arm64-cast;luci.chromium.try:fuchsia-x64-cast Tbr: cr-fuchsia+bot@chromium.org Change-Id: Ia096be5c18301a05b5e770649c5a86a9881d485a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2146850Reviewed-by:
-
Igor Makarov authored
- added .style.yapf file - reformat *.py files Bug: 1051750 Change-Id: I902200e328a800ec23a4c34ce7896b5d25122b19 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2132791Reviewed-by:
-
Igor Makarov authored
- added .style.yapf file - reformat *.py files Bug: 1051750 Change-Id: Id52422ad244199d802c3c66afe480646e1672d37 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2127112Reviewed-by:
-
Igor Makarov authored
- added .style.yapf file - reformat *.py files Bug: 1051750 Change-Id: I6ddf9f7e91c6a01bab7eed59d5d4f9b990636e65 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2142231Reviewed-by:
-
Yuki Shiino authored
Fixes the bindings generator not to expose IDL constructs by default, i.e. exposes only when [Exposed] is applied. No user visible behavior change. Change-Id: I3f16ff87afbf66c12e258bcd2c7f146e8afa4e51 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2145735Reviewed-by:
Hitoshi Yoshida <peria@chromium.org> Commit-Queue: Yuki Shiino <yukishiino@chromium.org> Cr-Commit-Position: refs/heads/master@{#758448}
-
CQ_INCLUDE_TRYBOTS=luci.chrome.try:chromeos-betty-pi-arc-chrome CQ_INCLUDE_TRYBOTS=luci.chrome.try:chromeos-eve-compile-chrome CQ_INCLUDE_TRYBOTS=luci.chrome.try:chromeos-kevin-compile-chrome BUG=762641 TBR=chrome-os-gardeners@google.com Change-Id: I3124b3c0363e25b9e7bc1573665897dae898633f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2146790Reviewed-by:
ChromeOS bot <3su6n15k.default@developer.gserviceaccount.com> Commit-Queue: ChromeOS bot <3su6n15k.default@developer.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#758447}
-
Igor Makarov authored
- added .style.yapf file - reformat *.py files Bug: 1051750 Change-Id: Id46a74411f7053437297e6857530aaa5f351efca Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2135687Reviewed-by:
-
Yuki Shiino authored
Bug: 839389 Change-Id: I497af4ab58c53f37825374e4423897f4b2c842e6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2142889Reviewed-by:
-
Kenichi Ishibashi authored
These methods are wrappers of corresponding methods defined in ServiceWorkerStorage. Bug: 1055677 Change-Id: I9acefbd627af1f9b495b9e47815bb109d07dc711 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2141813 Commit-Queue: Kenichi Ishibashi <bashi@chromium.org> Reviewed-by:
Makoto Shimazu <shimazu@chromium.org> Reviewed-by:
Kinuko Yasuda <kinuko@chromium.org> Cr-Commit-Position: refs/heads/master@{#758444}
-
Wanming Lin authored
This CL upstreams most device orientation tests to WPT. - Moves device orientation tests from web_tests/device_orientation/, web_tests/http/tests/security/powerfuFeatureRestrictions/, to web_tests/external/wpt/orientation-event with some necessary updates to adapt to WPT test framework. - Retains two page-visibility.html tests as which could not be automated in WPT at present and adds two similar manual tests there to keep test coverage sufficient. - Leaves existing tests as is, further improvement (e.g. remove duplicate tests, use EventWatcher, etc.) will be arranged in a follow-up. - Updates test paths in some profiles. Bug: 816462 Change-Id: I1b91168c5362fc6e059b2529dd4a1d8119f5dad6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2135059 Commit-Queue: Wanming Lin <wanming.lin@intel.com> Reviewed-by:
Reilly Grant <reillyg@chromium.org> Cr-Commit-Position: refs/heads/master@{#758443}
-
Yuki Shiino authored
Bug: 839389 Change-Id: I802b01943d6c6a5a178c40f516ac367d43981c82 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2145424 Commit-Queue: Yuki Shiino <yukishiino@chromium.org> Reviewed-by:
-
Christian Biesinger authored
Change-Id: I5dbd39bf616354d715968b591912abbb427d5954 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2146214 Auto-Submit: Christian Biesinger <cbiesinger@chromium.org> Reviewed-by:
Gyuyoung Kim <gyuyoung@igalia.com> Commit-Queue: Christian Biesinger <cbiesinger@chromium.org> Cr-Commit-Position: refs/heads/master@{#758441}
-
Igor Makarov authored
- added .style.yapf file - reformat *.py files Bug: 1051750 Change-Id: I97258536ef73d8b714cd1ccbba6ab2fc20b7d23b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2132193Reviewed-by:
-
Koji Ishii authored
This patch removes unused function |NGBoxFragmentPainter:: PaintLineBoxItem|. This became unused when r731835 crrev.com/c/1994556 switched line box painter to |PaintBlockFlowContents|. Bug: 982194 Change-Id: I51f9f1661f2462c6faba55e646c251e9992ecc78 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2143889 Auto-Submit: Koji Ishii <kojii@chromium.org> Commit-Queue: Kent Tamura <tkent@chromium.org> Reviewed-by:
-
Yuki Shiino authored
Bug: 839389 Change-Id: I20ca170b3536309e887f97a50710e075cd1caaed Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2142669 Commit-Queue: Hitoshi Yoshida <peria@chromium.org> Reviewed-by:
-
Igor Makarov authored
- added .style.yapf file - reformat *.py files Bug: 1051750 Change-Id: I8288aa519ff5a4634728b16005d46377a7a2cdc5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2141988Reviewed-by:
-
Timothy Gu authored
This reverts commit 103ac117. It appears that we were overly optimistic. There can be intermediate states where Element::GetIdAttribute() is called from Element::UpdateId(), which violates the DCHECK() put into place in the reverted commit. Original change's description: > Filter out empty ID in attribute changed callback > > Per spec [1], empty ID attributes must be treated identically as > nonexistent. This CL implements these steps faithfully, and results in > DocumentFragment::getElementById() always returning nullptr when the > empty string is given, thus fixing bug 1068580. > > Additionally, previously Document::getElementById() explicitly returned > nullptr when the empty string or the null string is given. The empty > string handling is no longer necessary after this CL, and thus removed. > (The null string handling is still necessary for internal C++ code that > relies on the short-circuiting behavior). > > [1]: https://dom.spec.whatwg.org/#concept-id > > Change-Id: Ia65024efef9e5ef54d9db233590a17b372282ed1 > Fixed: 1068580 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2140054 > Reviewed-by: Kent Tamura <tkent@chromium.org> > Commit-Queue: Timothy Gu <timothygu@chromium.org> > Cr-Commit-Position: refs/heads/master@{#757310} Fixed: 1069728 Change-Id: I70b2fd8d14456ec0b063cb18e5982384bd1285bf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2146924Reviewed-by:
-
Yuki Shiino authored
Bug: 839389 Change-Id: I95db56fa113354486742149024cd34173364eb46 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2142074Reviewed-by:
-
chrome-release-bot authored
# This is an automated release commit. # Do not revert without consulting chrome-pmo@google.com. NOAUTOREVERT=true TBR=lakpamarthy@chromium.org Change-Id: Ia981b9a58c02eff74658022b67e9113ee04fa9ca Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2146925Reviewed-by:
Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#758434}
-
- 12 Apr, 2020 12 commits
-
-
Anthony Fandrianto authored
Currently, a CIPD staging directory is populated by copying specified `sources` into it, and producing a .yaml manifest which reflects the copied files. This change refactors the template to invoke a pytho script to do the above instead of in GN, using the `yaml` library to write the file data in the proper format. Also make the license filepath explicitly passed through sources. Renames "archive" -> "package" and "manifest" -> "package definition" to be consistent with CIPD semantics (crbug.com/1042819#c8). Finally, have the script emit a depfile for all files tracked by the .yaml manifest. This refactor is desirable, as we want to create CIPD packages with more complicated rules than simply "copy and include these files" (see crrev.com/c/1925446, which extends the functionality of the template to allow for the inclusion of directories). Wriiting yamls with a library reduces the error-proneness of trying to recreate yaml's format in pure GN. Also, emitting a depfile ensure that we track and rebuild if the CIPD package is modified. Currently the potential danger of this change is limited in scope to fuchsia, as they are the only users of the template. I've checked locally that the produced CIPD packages for fuchsia are identical prior to this change. Bug: fuchsia:41443 Change-Id: If1b27d6a8fbbffdf767aaa4230bf7b527a553170 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2135186 Commit-Queue: Anthony Fandrianto <atyfto@google.com> Reviewed-by:
Bruce Dawson <brucedawson@chromium.org> Reviewed-by:
Kevin Marshall <kmarshall@chromium.org> Cr-Commit-Position: refs/heads/master@{#758433}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/16297237f8cc..fd5072e45780 Created with: gclient setdep -r src-internal@fd5072e45780 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://skia-autoroll.corp.goog/r/src-internal-chromium-autoroll Please CC nhiroki@google.com,reillyg@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md Cq-Include-Trybots: luci.chrome.try:linux-chromeos-chrome Bug: None Tbr: nhiroki@google.com,reillyg@google.com Change-Id: I2e96594a981f8509b1b853c3a450f98c78ae7269 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2146846Reviewed-by:
chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#758432}
-
chromium-autoroll authored
If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/fuchsia-sdk-chromium-autoroll Please CC cr-fuchsia+bot@chromium.org on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:fuchsia-arm64-cast;luci.chromium.try:fuchsia-x64-cast Tbr: cr-fuchsia+bot@chromium.org Change-Id: Ia016e89d022b541d676003bf1ea16865e37cc6f3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2146844Reviewed-by:
-
Bo Liu authored
It is unsafe and generally not possible to delete the profile data of a profile that has already been "loaded". The only safe implementation is to mark the profile data as deleted, wait until the next time browser process starts, ensure the profile data is not loaded, and find a time to delete the data. This CL implements this for weblayer. * Deletion marker are empty files in <data>/profiles_to_delete matching the directory names of profiles. If <data>/profiles_to_delete/foo exists, then <data>/profiles/foo is marked for deletion. * If client create with a name (say "foo") matching a deleted profile, will try to linearly check for directory with a suffix (eg "foo.1", "foo.2", etc) until a directory that is not marked for deletion is found. "." is not part of a valid profile name, so there is no risk of collision. * Now DestroyAndDeleteDataFromDisk will mark the profile for deletion, and only remove data with BrowsingDataRemover. It will not attempt to delete the profile directory. * Nuke and Mark are run in the same SequencedTaskRunner to ensure Nuke is called first in a process before any mark. This ensures Nuke will never remove a newly marked Profile during the current process's lifetime. * Nuke will delete the data and cache directories first, and only remove the marker if both succeeds. This ensures there is no race in reusing a profile path. Add weblayer_unittests and add some unit tests for profile_disk_operations. Bug: 1065585 Change-Id: I4b936c9a1f31da56612095bb1088b93232c5751f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2140101 Commit-Queue: Bo <boliu@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Cr-Commit-Position: refs/heads/master@{#758430}
-
CQ_INCLUDE_TRYBOTS=luci.chrome.try:chromeos-betty-pi-arc-chrome CQ_INCLUDE_TRYBOTS=luci.chrome.try:chromeos-eve-compile-chrome CQ_INCLUDE_TRYBOTS=luci.chrome.try:chromeos-kevin-compile-chrome BUG=762641 TBR=chrome-os-gardeners@google.com Change-Id: I5715a8a0e6ee4fc53ea793f7eef832deab377e71 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2146780Reviewed-by:
Achuith Bhandarkar <achuith@chromium.org> Commit-Queue: ChromeOS bot <3su6n15k.default@developer.gserviceaccount.com> Commit-Queue: Achuith Bhandarkar <achuith@chromium.org> Cr-Commit-Position: refs/heads/master@{#758429}
-
Rainhard Findling authored
Bug: 1015841 Change-Id: I2554be24bccc2c7fe2dfa76ecc380e0b98a7d32c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2135757Reviewed-by:
Esmael Elmoslimany <aee@chromium.org> Commit-Queue: Rainhard Findling <rainhard@chromium.org> Cr-Commit-Position: refs/heads/master@{#758428}
-
Guido Urdaneta authored
Bug: 1065838 Change-Id: Id87979155a33bb8bc6daf18555fc4135ab21f3d9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2144276Reviewed-by:
Marina Ciocea <marinaciocea@chromium.org> Commit-Queue: Guido Urdaneta <guidou@chromium.org> Cr-Commit-Position: refs/heads/master@{#758427}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/639083a98906..6dfc55454671 git log 639083a98906..6dfc55454671 --date=short --first-parent --format='%ad %ae %s' 2020-04-12 skia-recreate-skps@skia-swarming-bots.iam.gserviceaccount.com Update SKP version Created with: gclient setdep -r src/third_party/skia@6dfc55454671 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/skia-autoroll Please CC kjlubick@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux-blink-rel;luci.chromium.try:linux-chromeos-compile-dbg;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel Bug: None Tbr: kjlubick@google.com Change-Id: I100cc5c489812eb5e5605588090b9b4dc22c5b79 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2146839Reviewed-by:
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/459ecee2cbdc..639083a98906 git log 459ecee2cbdc..639083a98906 --date=short --first-parent --format='%ad %ae %s' 2020-04-12 skia-recreate-skps@skia-swarming-bots.iam.gserviceaccount.com Update Go Deps Created with: gclient setdep -r src/third_party/skia@639083a98906 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/skia-autoroll Please CC kjlubick@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux-blink-rel;luci.chromium.try:linux-chromeos-compile-dbg;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel Bug: None Tbr: kjlubick@google.com Change-Id: I0e606ff64dc0076f4d111a5ffe1b8f5826e52e41 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2146521Reviewed-by:
-
chromium-autoroll authored
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/30c590849d00..3f138576af56 git log 30c590849d00..3f138576af56 --date=short --first-parent --format='%ad %ae %s' 2020-04-12 devtools-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com Update DevTools Chromium DEPS. Created with: gclient setdep -r src/third_party/devtools-frontend/src@3f138576af56 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/devtools-frontend-chromium Please CC devtools-waterfall-sheriff-onduty@grotations.appspotmail.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md Bug: None Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com Change-Id: I85f35ca5b07bdf91fef842e16acee941a736b2dc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2146519Reviewed-by:
-
chromium-autoroll authored
If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/fuchsia-sdk-chromium-autoroll Please CC cr-fuchsia+bot@chromium.org on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:fuchsia-arm64-cast;luci.chromium.try:fuchsia-x64-cast Tbr: cr-fuchsia+bot@chromium.org Change-Id: Icf4c30a505f4fa79d8b766acb47ecd226cdf9328 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2146520Reviewed-by:
-
chromium-autoroll authored
This CL may cause a small binary size increase, roughly proportional to how long it's been since our last AFDO profile roll. For larger increases (around or exceeding 100KB), please file a bug against gbiv@chromium.org. Additional context: https://crbug.com/805539 Please note that, despite rolling to chrome/android, this profile is used for both Linux and Android. If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/afdo-chromium-autoroll Please CC gbiv@chromium.org on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md Tbr: gbiv@chromium.org Change-Id: I9c397002854c1ced07ae994031d1dd8fa0225687 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2146518Reviewed-by:
-
