- 19 Oct, 2018 40 commits
-
-
Leszek Swirski authored
This is a reland of 7bd91635 No changes from the original, revert reason is fixed with https://chromium-review.googlesource.com/c/1283037 Original change's description: > [blink] Control ScriptStreamer with ScriptResource > > Move the ScriptStreamer control logic from ClassicPendingScript to > ScriptResource. In the future, this will allow us to start streaming > a ScriptResource before the ClassicPendingScript is available, e.g on > preload. > > The ClassicPendingScript now only sends one "finished" callback, from > ScriptResource. This callback is either when the streaming completes, > or when there is no streaming and the ClassicPendingScript has told > the ScriptResource that it doesn't intend to start streaming. In the > long run, we want all scripts to go through the streaming interface, > and we want ScriptResource to control when streaming starts, so the > "no more streaming" call will disappear -- however it is necessary to > maintain the current behaviour, and be able to control it with a > runtime flag. > > Bug: chromium:865098 > Change-Id: I2c4cc16635a6538b7ff24a24463fe6f34efd8a2e > Reviewed-on: https://chromium-review.googlesource.com/c/1181430 > Commit-Queue: Leszek Swirski <leszeks@chromium.org> > Reviewed-by: Hiroshige Hayashizaki <hiroshige@chromium.org> > Reviewed-by: Kinuko Yasuda <kinuko@chromium.org> > Reviewed-by: Kouhei Ueno <kouhei@chromium.org> > Cr-Commit-Position: refs/heads/master@{#599148} TBR=kouhei@chromium.org,kinuko@chromium.org Bug: chromium:865098 Change-Id: I0df324ef8e284f4d3d55a1721d71be5a66a3285c Reviewed-on: https://chromium-review.googlesource.com/c/1286450 Commit-Queue: Leszek Swirski <leszeks@chromium.org> Reviewed-by:
Hiroshige Hayashizaki <hiroshige@chromium.org> Cr-Commit-Position: refs/heads/master@{#601143}
-
Vasilii Sukhanov authored
The CL moves the implementation from Android-specific code to the cross-platform component. This is a follow-up to https://chromium-review.googlesource.com/c/chromium/src/+/1195483 https://chromium-review.googlesource.com/c/chromium/src/+/1202204 Bug: 879486, 835234 Change-Id: I03dfe07c19f215bc914c9d564011e68010a1c11a Reviewed-on: https://chromium-review.googlesource.com/c/1283133 Commit-Queue: Vasilii Sukhanov <vasilii@chromium.org> Reviewed-by:
Ilya Sherman <isherman@chromium.org> Reviewed-by:
Ioana Pandele <ioanap@chromium.org> Reviewed-by:
Vadym Doroshenko <dvadym@chromium.org> Cr-Commit-Position: refs/heads/master@{#601142}
-
Joshua Bell authored
Bug: 824533,750452 Change-Id: I103d6b6a3bd106a6a38de03f9ff14d2766c7b269 Reviewed-on: https://chromium-review.googlesource.com/c/1288890Reviewed-by:
John Abd-El-Malek <jam@chromium.org> Reviewed-by:
Ben Kelly <wanderview@chromium.org> Reviewed-by:
Victor Costan <pwnall@chromium.org> Commit-Queue: Joshua Bell <jsbell@chromium.org> Cr-Commit-Position: refs/heads/master@{#601141}
-
Jakob Gruber authored
These tests were badly outdated and had been marked as failing for three years. Issues were: regexp-caching: - RegExp properties were iterated with a for-in loop, but relevant properties are non-enumerable. Fixed by using Object.getOwnPropertyNames instead. - isReadOnly detection was broken, attempting to write a property and then comparing against the result with '=='. Removed just this part since it doesn't add any value. - We attempted to test 'multiline' coercion, but this property hasn't existed for ages. string-replace-2: - The test relied on old unspecced semantics of interactions between RegExp.p.replace and properties on the RegExp object. Updated to the current behavior. - A bunch of other previously failing tests now pass. Bug: chromium:569139 Change-Id: Ia56da800fc44dd3b750d72fd8fe87a19c7f59e2f Reviewed-on: https://chromium-review.googlesource.com/c/1290153Reviewed-by:
Marja Hölttä <marja@chromium.org> Commit-Queue: Jakob Gruber <jgruber@chromium.org> Cr-Commit-Position: refs/heads/master@{#601140}
-
Daniel Bratell authored
allocator/allocator_shim.h and base/base_paths_posix.h were in base's |sources| list twice each in some configuration. This removes the duplicates since that confused some tools. Change-Id: I0dfbf796a73ce28fd66352afe0651e61058506eb Reviewed-on: https://chromium-review.googlesource.com/c/1290910Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Commit-Queue: Daniel Bratell <bratell@opera.com> Cr-Commit-Position: refs/heads/master@{#601139}
-
Michael van Ouwerkerk authored
Change-Id: Ifa4323adbfdf92c148caa2c052397ce0ca49e8f8 Reviewed-on: https://chromium-review.googlesource.com/c/1283253Reviewed-by:
Benoit L <lizeb@chromium.org> Commit-Queue: Michael van Ouwerkerk <mvanouwerkerk@chromium.org> Cr-Commit-Position: refs/heads/master@{#601138}
-
Jérôme Lebel authored
Adding a fix that should have been committed with crrev.com/1286659 When the OK button layout is updated, the container layout should be updated too. Bug: 897105 Change-Id: I80a22e755d3255b4ce2c5f637280a3ac7576f1a5 Reviewed-on: https://chromium-review.googlesource.com/c/1290978Reviewed-by:
Gauthier Ambard <gambard@chromium.org> Commit-Queue: Jérôme Lebel <jlebel@chromium.org> Cr-Commit-Position: refs/heads/master@{#601137}
-
Tom McKee authored
Memory.TabFootprint events give a high-level sample of how much memory is used to render a given URL. To keep these events easy to reason about and analyze, some memory isn't accounted for. Namely, when processes host parts of other tabs, we don't record their contributions. We do, however, make sure that an individual record has all the information nescessary to classify it as a full or partial record. Change-Id: If7a19031502e357be9567ebed760de234f2974ac Reviewed-on: https://chromium-review.googlesource.com/c/1191817Reviewed-by:
Kentaro Hara <haraken@chromium.org> Reviewed-by:
Timothy Dresser <tdresser@chromium.org> Reviewed-by:
Ken Buchanan <kenrb@chromium.org> Reviewed-by:
Steven Holte <holte@chromium.org> Commit-Queue: Tom McKee <tommckee@chromium.org> Cr-Commit-Position: refs/heads/master@{#601136}
-
Hongchan Choi authored
Previously the storage for automatic pull nodes (handlers actually) were using a raw pointer, so when the BaseAudioContext goes away there\ is no object keeping these node alive. This CL adds ref-counting to the storage so the handler can be alive even after BaseAudioContext is swept away. Without this fix, the crash happens in few minutes. Bug: 891187 Test: The repro case does not crash after 2 hours on the local ASAN. Change-Id: I33a1f74c5803f53e1ace2990af3dd0728720d258 Reviewed-on: https://chromium-review.googlesource.com/c/1286823Reviewed-by:
Kentaro Hara <haraken@chromium.org> Commit-Queue: Hongchan Choi <hongchan@chromium.org> Cr-Commit-Position: refs/heads/master@{#601135}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/cd316406e106..1bccae517ace git log cd316406e106..1bccae517ace --date=short --no-merges --format='%ad %ae %s' 2018-10-19 mtklein@google.com Revert "Use OpenGL sampler objects when available." 2018-10-19 skia-bookmaker@skia-swarming-bots.iam.gserviceaccount.com Update markdown files 2018-10-19 skia-recreate-skps@skia-swarming-bots.iam.gserviceaccount.com Update go_deps asset 2018-10-19 skia-autoroll@skia-public.iam.gserviceaccount.com Roll third_party/externals/angle2 c4765aa78267..bc6f52f36d5f (8 commits) 2018-10-19 csmartdalton@google.com ccpr: Unregister path listeners when their cache entries are evicted 2018-10-19 bsalomon@google.com Use OpenGL sampler objects when available. Created with: gclient setdep -r src/third_party/skia@1bccae517ace The AutoRoll server is located here: https://autoroll.skia.org/r/skia-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_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;master.tryserver.blink:linux_trusty_blink_rel TBR=egdaniel@chromium.org Change-Id: Ic944199786bf2bfcd3edbca0400204c5b36dc73b Reviewed-on: https://chromium-review.googlesource.com/c/1291150Reviewed-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@{#601134}
-
Daniel Bratell authored
Some isolate step errors in trybots mentioned these non-existing headers so hoping the trybots will be happier, this patch removes and changes the names to point to existing files. Bug: 881589 Change-Id: I6c7728110a9ce162293c57606824140cdacd8d38 Reviewed-on: https://chromium-review.googlesource.com/c/1286660Reviewed-by:
Julian Pastarmov <pastarmovj@chromium.org> Commit-Queue: Daniel Bratell <bratell@opera.com> Cr-Commit-Position: refs/heads/master@{#601133}
-
Sergio Villar Senin authored
It was using SigninManager API to get account info and also to check whether there was a the primary (authenticated) account available. Migrated to IdentityManager API so it could eventually use the identity service. Bug: 890773 Change-Id: Ic6ed0bfbadbfdead2541571d4ede9c91c24f0077 Reviewed-on: https://chromium-review.googlesource.com/c/1286652Reviewed-by:
Alexander Alekseev <alemate@chromium.org> Reviewed-by:
Colin Blundell <blundell@chromium.org> Commit-Queue: Sergio Villar <svillar@igalia.com> Cr-Commit-Position: refs/heads/master@{#601132}
-
Gabriel Charette authored
And fix CanIncreaseThreadPriority(REALTIME_AUDIO) to use the per-platform path. Bug: 816389 Change-Id: I15409a7e00f8ed0f132d348bb42c93e574a83f73 Reviewed-on: https://chromium-review.googlesource.com/c/1283021Reviewed-by:
François Doray <fdoray@chromium.org> Commit-Queue: Gabriel Charette <gab@chromium.org> Cr-Commit-Position: refs/heads/master@{#601131}
-
Alexandr Ilin authored
The Mojo union more closely matches the actual intent of GpuMemoryBufferHandle, since the handle can store only one of several types of platform handles. GpuMemoryBufferHandle has |id| member that should be present all the time, so mojom::GpuMemoryBufferHandle remains a Mojo struct and the union is embedded into it. Bug: 863011 Change-Id: I5dc9100392cd0a6f701e93ac4c91ca50e5077967 Reviewed-on: https://chromium-review.googlesource.com/c/1288609 Commit-Queue: Alexandr Ilin <alexilin@chromium.org> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Cr-Commit-Position: refs/heads/master@{#601130}
-
Mihai Sardarescu authored
This CL adds information about token events in the chrome://signin-internals page. This is needed to allow developers to debug issues when the Google auth state if changed by the browser (either due to Mirror or Dice). A follow-up CL will add the source for the refresh token events. Bug: 896182 Change-Id: Ie70e3e647947aa771572ed47992e2d0c59bea361 Reviewed-on: https://chromium-review.googlesource.com/c/1286460 Commit-Queue: Mihai Sardarescu <msarda@chromium.org> Reviewed-by:
David Roger <droger@chromium.org> Cr-Commit-Position: refs/heads/master@{#601129}
-
Anders Hartvoll Ruud authored
Currently we accept zero items, which is wrong. R=futhark@chromium.org Bug: 641877 Change-Id: I8acdc4c5c7ba54a71a478e7eed79223271e1e92d Reviewed-on: https://chromium-review.googlesource.com/c/1290889Reviewed-by:
Rune Lillesveen <futhark@chromium.org> Commit-Queue: Anders Ruud <andruud@chromium.org> Cr-Commit-Position: refs/heads/master@{#601128}
-
Christian Dullweber authored
TouchSelectionControllerClientAndroidSiteIsolationTest.SelectionThenPinchInOOPIF is quite flaky. TBR: kenrb@chromium.org Bug: 897062 Change-Id: I7aae2557f42aa8bd1d54d194c6775cb25a03e995 Reviewed-on: https://chromium-review.googlesource.com/c/1290977Reviewed-by:
Christian Dullweber <dullweber@chromium.org> Commit-Queue: Christian Dullweber <dullweber@chromium.org> Cr-Commit-Position: refs/heads/master@{#601127}
-
Mikel Astiz authored
They verify some otherwise-untested but privacy-sensitive requirements of what is being sent on the wire, where most (without custom passphrase) or all (with custom passphrase) proto fields should be encrypted. The actual verification is done using the state in the fake server, which is assumed to store committed content without pruning. This holds true today and is unlikely to change in the future. Bug: 856941,870624 Change-Id: I9198ca69c53d55a80f4b2a0c55cd5265e57741aa Reviewed-on: https://chromium-review.googlesource.com/c/1290809 Commit-Queue: Mikel Astiz <mastiz@chromium.org> Reviewed-by:
Mohamed Amir Yosef <mamir@chromium.org> Cr-Commit-Position: refs/heads/master@{#601126}
-
chromium-autoroll authored
https://chromium.googlesource.com/catapult.git/+log/f608aa22d174..a0b50a9a0590 git log f608aa22d174..a0b50a9a0590 --date=short --no-merges --format='%ad %ae %s' 2018-10-19 perezju@chromium.org [soundwave] Add module to get timeseries data for v8 study Created with: gclient setdep -r src/third_party/catapult@a0b50a9a0590 The AutoRoll server is located here: https://autoroll.skia.org/r/catapult-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;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=chromium:894773 TBR=sullivan@chromium.org Change-Id: If8e1f0cb20d29514f94113a444312891f2194f87 Reviewed-on: https://chromium-review.googlesource.com/c/1291149Reviewed-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@{#601125}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/fa30285b915e..759a2673ff90 Created with: gclient setdep -r src-internal@759a2673ff90 The AutoRoll server is located here: https://autoroll-internal.skia.org/r/src-internal-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. TBR=mmoss@chromium.org Change-Id: Ied856a9be703a5b99df1d414d3defe8f5032b164 Reviewed-on: https://chromium-review.googlesource.com/c/1291050Reviewed-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@{#601124}
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/ea377862..d206a4b9 Please follow these instructions for assigning/CC'ing issues: https://github.com/v8/v8/wiki/Triaging%20issues Please close rolling in case of a roll revert: https://v8-roll.appspot.com/ This only works with a Google account. CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel;luci.chromium.try:android_optional_gpu_tests_rel TBR=hablich@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com Change-Id: I160e2f43613fb5edb80bcc8148fe789f0256804f Reviewed-on: https://chromium-review.googlesource.com/c/1291090Reviewed-by:
v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Commit-Queue: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#601123}
-
Etienne Pierre-doray authored
This is a reland of 7a77c4e0 Death test should run in single thread. Adding testing::GTEST_FLAG(death_test_style) = "threadsafe"; before EXPECT_DCHECK_DEATH() to fix flakiness. Original change's description: > [Task Scheduler]: Merge blocking and non-blocking pools. > > This CL creates a feature experiment that removes blocking worker pools > from the task scheduler. Tasks with MayBlock trait are instead posted to > the usual foreground/background pool, giving us better control over scheduling. > > Note: ScopedBlockingCall is used to add extra workers to the pool when a task is > blocking. In this CL, we take advantage of this behavior to make sure enough > workers are running on the CPU. > > Bug: 874080 > Change-Id: I7889a941f82203388c259b0d96073eb5ddf3de69 > Reviewed-on: https://chromium-review.googlesource.com/c/1249836 > Commit-Queue: Etienne Pierre-Doray <etiennep@chromium.org> > Reviewed-by: François Doray <fdoray@chromium.org> > Reviewed-by: Gabriel Charette <gab@chromium.org> > Reviewed-by: Robert Kaplow (sloooow) <rkaplow@chromium.org> > Cr-Commit-Position: refs/heads/master@{#600401} TBR=rkaplow@chromium.org Bug: 874080 Change-Id: I54665c798d332eead0f81da0f15c93368ec883a8 Reviewed-on: https://chromium-review.googlesource.com/c/1290911 Commit-Queue: François Doray <fdoray@chromium.org> Reviewed-by:
François Doray <fdoray@chromium.org> Cr-Commit-Position: refs/heads/master@{#601122}
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/2461c319ed08..82d432980cff git log 2461c319ed08..82d432980cff --date=short --no-merges --format='%ad %ae %s' 2018-10-19 nisse@webrtc.org Delete unused test class StreamSource Created with: gclient setdep -r src/third_party/webrtc@82d432980cff The AutoRoll server is located here: https://autoroll.skia.org/r/webrtc-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux_chromium_archive_rel_ng;luci.chromium.try:mac_chromium_archive_rel_ng TBR=webrtc-chromium-sheriffs-robots@google.com Change-Id: I37382d8385ad133ccccd6304b764978d1d76af05 Reviewed-on: https://chromium-review.googlesource.com/c/1290783Reviewed-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@{#601121}
-
Caitlin Potter authored
https://github.com/tc39/ecma262/pull/1320 proposes changing the JS language so that the following: ``` let P = {}; Object.defineProperty('prop', { writable: false, value: 1 }); let O = { __proto__: P }; O.prop = 2; console.log(O.prop); ``` will print '2' (instead of '1' in sloppy mode, or throwing a TypeError in strict mode). We intend to measure the frequency of both cases to determine how web compatible the change will be. This is the Chromium side of required changes. The V8-side CL: https://crrev.com/c/1255549 BUG=v8:8175 Change-Id: If74e7aebcac01e034757c0c639bfb5518cd95c91 Reviewed-on: https://chromium-review.googlesource.com/c/1280618Reviewed-by:
Marja Hölttä <marja@chromium.org> Reviewed-by:
Jochen Eisinger <jochen@chromium.org> Commit-Queue: Caitlin Potter <caitp@igalia.com> Cr-Commit-Position: refs/heads/master@{#601120}
-
Xi Han authored
This is caused by not setting chrome channel before initializing FeatureList in early startup, which was introduced in CL (https://crbug.com/1173163). In this CL, we make GetChannel() call the SetChannel() if the channel hasn't been set yet. Bug: 896416 Change-Id: Id89c199779074d762f1d16edc711fedaaab66694 Reviewed-on: https://chromium-review.googlesource.com/c/1287850 Commit-Queue: Xi Han <hanxi@chromium.org> Reviewed-by:
Robert Kaplow (sloooow) <rkaplow@chromium.org> Reviewed-by:
John Abd-El-Malek <jam@chromium.org> Reviewed-by:
Alexei Svitkine <asvitkine@chromium.org> Cr-Commit-Position: refs/heads/master@{#601119}
-
Marc Treib authored
This removes one entry of the ServerConnectionCode enum which is unused, and removes an obsolete TODO. Bug: none Change-Id: I19a6653d30fc8f6c2bfd7d7d45c6a7a57f6f0473 Reviewed-on: https://chromium-review.googlesource.com/c/1290951Reviewed-by:
vitaliii <vitaliii@chromium.org> Commit-Queue: Marc Treib <treib@chromium.org> Cr-Commit-Position: refs/heads/master@{#601118}
-
Tanja Gornak authored
Bug: 801985 Change-Id: I40d0f5819663cf2047344431bfd604cd5a89551f Reviewed-on: https://chromium-review.googlesource.com/c/1280462 Commit-Queue: Tatiana Gornak <melandory@chromium.org> Reviewed-by:
Pavel Yatsuk <pavely@chromium.org> Cr-Commit-Position: refs/heads/master@{#601117}
-
Rune Lillesveen authored
Selectors in UA sheets are added case-sensitively to RuleSet buckets as if they were sheets in non-HTML documents in order to match correctly for xhtml and svg documents. That means we should not use the lower-case element name to lookup element rules as the lower-case of foreignObject would not find the foreignObject rules from the element bucket in the svg.css UA stylesheet. Bug: 819814 Change-Id: I2064f6669f6b7021feab2c93dd6b4d8a5c749b77 Reviewed-on: https://chromium-review.googlesource.com/c/1290849Reviewed-by:
Fredrik Söderquist <fs@opera.com> Commit-Queue: Rune Lillesveen <futhark@chromium.org> Cr-Commit-Position: refs/heads/master@{#601116}
-
Christian Dullweber authored
The test is flaky on windows bots. TBR: lazyboy@chromium.org Bug: 897059 Change-Id: I94deabc16016ffd723d1819ca5ef13b05ae150a1 Reviewed-on: https://chromium-review.googlesource.com/c/1290933Reviewed-by:
Christian Dullweber <dullweber@chromium.org> Commit-Queue: Christian Dullweber <dullweber@chromium.org> Cr-Commit-Position: refs/heads/master@{#601115}
-
chromium-autoroll authored
https://chromium.googlesource.com/catapult.git/+log/2f3bd7e85ec6..f608aa22d174 git log 2f3bd7e85ec6..f608aa22d174 --date=short --no-merges --format='%ad %ae %s' 2018-10-19 perezju@chromium.org [soundwave] Add dashboard_service module 2018-10-19 perezju@chromium.org [soundwave] Add timeseries --output-csv option Created with: gclient setdep -r src/third_party/catapult@f608aa22d174 The AutoRoll server is located here: https://autoroll.skia.org/r/catapult-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;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=chromium:890691,chromium:894773,chromium:879526 TBR=sullivan@chromium.org Change-Id: Ie326b24cd52919b8620f0907de755467ef428687 Reviewed-on: https://chromium-review.googlesource.com/c/1290784Reviewed-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@{#601114}
-
Brian Osman authored
https://skia-review.googlesource.com/c/skia/+/160481 and https://skia-review.googlesource.com/c/skia/+/163520 Change-Id: Icade482f7a82fb4661f76486bc2c85af5abe7dfe Reviewed-on: https://chromium-review.googlesource.com/c/1288853 Commit-Queue: Mike Klein <mtklein@chromium.org> Reviewed-by:
Mike Klein <mtklein@chromium.org> Cr-Commit-Position: refs/heads/master@{#601113}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/0a5c62aa1bec..fa30285b915e Created with: gclient setdep -r src-internal@fa30285b915e The AutoRoll server is located here: https://autoroll-internal.skia.org/r/src-internal-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. TBR=mmoss@chromium.org Change-Id: If5893416ad3cb5ecaa18a4950e216079a89f31c7 Reviewed-on: https://chromium-review.googlesource.com/c/1290778Reviewed-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@{#601112}
-
Marc Treib authored
It's unused - in practice, the value is queried through SyncClient::GetLocalSyncBackendFolder (which contains some extra logic). Bug: none Change-Id: Icc2dc605ea66ba86f6e6055c126739c37efbcb05 Reviewed-on: https://chromium-review.googlesource.com/c/1290275Reviewed-by:
vitaliii <vitaliii@chromium.org> Commit-Queue: Marc Treib <treib@chromium.org> Cr-Commit-Position: refs/heads/master@{#601111}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/80c79964c796..7a5d83bcb62f git log 80c79964c796..7a5d83bcb62f --date=short --no-merges --format='%ad %ae %s' 2018-10-18 fmayer@google.com profiling: Add heapprofd.rc. 2018-10-18 fmayer@google.com profiling: Add malloc hooks. Created with: gclient setdep -r src/third_party/perfetto@7a5d83bcb62f The AutoRoll server is located here: https://autoroll.skia.org/r/perfetto-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. TBR=perfetto-bugs@google.com Change-Id: I1d8618dccb54f33d72d0439b60d28e278d5f58a1 Reviewed-on: https://chromium-review.googlesource.com/c/1290780Reviewed-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@{#601110}
-
Gauthier Ambard authored
This CL converts the DataplanUsageCollectionViewController to UITableViewController. It also adds the cellBackgroundColor property to the styler so the cells can have a background color different from the table view's background. It also adds an accessoryType for the DetailTextItem. Bug: 894791 Cq-Include-Trybots: luci.chromium.try:ios-simulator-cronet;luci.chromium.try:ios-simulator-full-configs Change-Id: Ie1332811d3df6d8ef7650fb34fa3a17a515da3d9 Reviewed-on: https://chromium-review.googlesource.com/c/1286142 Commit-Queue: Gauthier Ambard <gambard@chromium.org> Reviewed-by:
Sergio Collazos <sczs@chromium.org> Cr-Commit-Position: refs/heads/master@{#601109}
-
Mohamed Amir Yosef authored
This CL adds the support to convert GCMMessages to/from JSONObject In preparation for later patches that would actually persist GCMMessages in SharedPreferences as JSONObjects. GCMMessages are persisted for lazy FCM subscription that don't require immediate delivery if Chrome is not in the foreground. Bug: 882887 Change-Id: I674eae93262ee339c574b2f18da206785ebbadfb Reviewed-on: https://chromium-review.googlesource.com/c/1283609 Commit-Queue: Mohamed Amir Yosef <mamir@chromium.org> Reviewed-by:
Peter Conn <peconn@chromium.org> Reviewed-by:
Peter Beverloo <peter@chromium.org> Cr-Commit-Position: refs/heads/master@{#601108}
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/67ed0448..ea377862 Please follow these instructions for assigning/CC'ing issues: https://github.com/v8/v8/wiki/Triaging%20issues Please close rolling in case of a roll revert: https://v8-roll.appspot.com/ This only works with a Google account. CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel;luci.chromium.try:android_optional_gpu_tests_rel TBR=hablich@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com Change-Id: Id35ec14911b0a29fa93f9ceb17245618542aa257 Reviewed-on: https://chromium-review.googlesource.com/c/1290779Reviewed-by:
v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Commit-Queue: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#601107}
-
Christian Dullweber authored
This reverts commit 7a77c4e0. Reason for revert: Findit identified that this introduced flakiness and it looks reasonable. Please take a look Original change's description: > [Task Scheduler]: Merge blocking and non-blocking pools. > > This CL creates a feature experiment that removes blocking worker pools > from the task scheduler. Tasks with MayBlock trait are instead posted to > the usual foreground/background pool, giving us better control over scheduling. > > Note: ScopedBlockingCall is used to add extra workers to the pool when a task is > blocking. In this CL, we take advantage of this behavior to make sure enough > workers are running on the CPU. > > Bug: 874080 > Change-Id: I7889a941f82203388c259b0d96073eb5ddf3de69 > Reviewed-on: https://chromium-review.googlesource.com/c/1249836 > Commit-Queue: Etienne Pierre-Doray <etiennep@chromium.org> > Reviewed-by: François Doray <fdoray@chromium.org> > Reviewed-by: Gabriel Charette <gab@chromium.org> > Reviewed-by: Robert Kaplow (sloooow) <rkaplow@chromium.org> > Cr-Commit-Position: refs/heads/master@{#600401} TBR=gab@chromium.org,fdoray@chromium.org,rkaplow@chromium.org,etiennep@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 874080, 897014 Change-Id: I5d125aba916dfb0dfce791b4d0a5b1ca5e6035d9 Reviewed-on: https://chromium-review.googlesource.com/c/1290152Reviewed-by:
Christian Dullweber <dullweber@chromium.org> Commit-Queue: Christian Dullweber <dullweber@chromium.org> Cr-Commit-Position: refs/heads/master@{#601106}
-
Daniel Bratell authored
The target :make_core_generated_css_value_id_mappings was listed twice which made its output be twice in some sources lists. This confused some tools. Seems better to only have it there once. R=fs@opera.com Change-Id: I1da2cfbda7021fa5262d0c0a74b894989fc200de Reviewed-on: https://chromium-review.googlesource.com/c/1290929Reviewed-by:
Fredrik Söderquist <fs@opera.com> Commit-Queue: Daniel Bratell <bratell@opera.com> Cr-Commit-Position: refs/heads/master@{#601105}
-
chromium-autoroll authored
https://chromium.googlesource.com/catapult.git/+log/237fb2a03b4b..2f3bd7e85ec6 git log 237fb2a03b4b..2f3bd7e85ec6 --date=short --no-merges --format='%ad %ae %s' 2018-10-19 perezju@chromium.org [soundwave] Refactor database connection management Created with: gclient setdep -r src/third_party/catapult@2f3bd7e85ec6 The AutoRoll server is located here: https://autoroll.skia.org/r/catapult-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;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=chromium:879526 TBR=sullivan@chromium.org Change-Id: I466a38fe2444294772f1634b0a50d45de102fdde Reviewed-on: https://chromium-review.googlesource.com/c/1290777Reviewed-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@{#601104}
-