- 20 Sep, 2018 40 commits
-
-
Max Morin authored
Make ForwardingAudioStreamFactory hosting the source streams to be aware that it's being captured by a loopback sinks. Notify loopback sinks when the source ForwardingAudioStreamFactory (i.e. WebContents whch owns it) is being destroyed. Bug: 866440,852880,866442 Change-Id: I4a46952cafd378f87ceb7da4a1c1ce27341babd9 Reviewed-on: https://chromium-review.googlesource.com/1221318 Commit-Queue: Max Morin <maxmorin@chromium.org> Reviewed-by:
Max Morin <maxmorin@chromium.org> Cr-Commit-Position: refs/heads/master@{#592800}
-
Etienne Pierre-doray authored
This CL uses ScopedBlockingCall to mark blocking calls in /chrome/browser/media. This CL was created by replacing calls to AssertBlockingAllowed() with instantiations of ScopedBlockingCall(MAY_BLOCK). I kindly ask the reviewer to make sure of the following: - ScopedBlockingCall is instantiated in a scope with minimal CPU usage. If this is not the case, ScopedBlockingCall should be instantiated closer to the blocking call. See scoped_blocking_call.h for more info. Please let me know when/where the blocking call happens if this needs to be changed. - Parameter |blocking_type| matches expectation (MAY_BLOCK/WILL_BLOCK). See BlockingType for more info. While I assumed MAY_BLOCK by default, that might not be the best fit if we know that this callsite is guaranteed to block. - The ScopedBlockingCall's scope covers the entirety of the blocking operation previously asserted against by the AssertBlockingAllowed(). This CL was uploaded by git cl split. R=chcunningham@chromium.org TBR=chcunningham@chromium.org Bug: 874080 Change-Id: If0029c7a63eb0cc35a18dbcec7c21cbdaeeaf156 Reviewed-on: https://chromium-review.googlesource.com/1191193 Commit-Queue: Etienne Pierre-Doray <etiennep@chromium.org> Reviewed-by:Yuchen Liu <yucliu@chromium.org> Cr-Commit-Position: refs/heads/master@{#592799}
-
Nico Weber authored
These two files are unused after https://chromium-review.googlesource.com/c/chromium/src/+/1234473 Bug: 832676 Change-Id: I216ee64cda26ba618a8b89bd8dc216aef6f567f5 Reviewed-on: https://chromium-review.googlesource.com/1236176Reviewed-by:
Elly Fong-Jones <ellyjones@chromium.org> Commit-Queue: Nico Weber <thakis@chromium.org> Cr-Commit-Position: refs/heads/master@{#592798}
-
Max Moroz authored
https://chromium.googlesource.com/external/github.com/google/re2.git/+log/4c916c947ab7..bfe29206c269 $ git log 4c916c947..bfe29206c --date=short --no-merges --format='%ad %ae %s' 2018-09-19 junyer Crudely limit the use of . when fuzzing. Created with: roll-dep src/third_party/re2/src Bug: 884457 Change-Id: Id978d2f46c8c0fdf2017d4c3cba78b75797fd17a Reviewed-on: https://chromium-review.googlesource.com/1235336Reviewed-by:
Nico Weber <thakis@chromium.org> Commit-Queue: Nico Weber <thakis@chromium.org> Cr-Commit-Position: refs/heads/master@{#592797}
-
Eric Seckler authored
Replace the remaining references to BrowserThread::PostTask with the base::PostTaskWithTraits API. These locations weren't covered by the global replacement patch as they were either added recently or ignored by the script. TBR=lazyboy@chromium.org Bug: 878356 Change-Id: Id199777ae6bcb30ebb03b767f9cd8c6f981c6ac4 Reviewed-on: https://chromium-review.googlesource.com/1235727 Commit-Queue: Eric Seckler <eseckler@chromium.org> Reviewed-by:
Jochen Eisinger <jochen@chromium.org> Reviewed-by:
Alex Clarke <alexclarke@chromium.org> Reviewed-by:
Colin Blundell <blundell@chromium.org> Cr-Commit-Position: refs/heads/master@{#592796}
-
Eric Robinson authored
This updates the closures and callbacks to use the "Once" paradigm as per the style guide/presubmission warnings. All of the instances were switched over to "Once". Bug: 884057 Change-Id: I93a63e79c6e142051a80eea433f29239a1f3b28d Reviewed-on: https://chromium-review.googlesource.com/1234217 Commit-Queue: Eric Robinson <ericrobinson@chromium.org> Reviewed-by:
Charlie Harrison <csharrison@chromium.org> Cr-Commit-Position: refs/heads/master@{#592795}
-
Colin Blundell authored
ProfileOAuth2TokenService has a corner case wherein during startup, it can fire token removal notifications for accounts for which it has never previously filed a token available notification. IdentityManager currently swallows such notifications. However, as we streamline IdentityManager to be just a straight pass-through to its backing classes (crbug.com/883722), IdentityManager will no longer be able to detect this case (because it won't be maintaining any cached info from the token available notifications). This CL makes the behavioral change of having IdentityManager always pass on token removal notifications from ProfileOAuth2TokenService. The behavioral impact is that consumers of IdentityManager::Observer::OnRefreshTokenRemovedForAccount() will now see a removal notification in the corner case described above. However, all such consumers were previously consumers of ProfileOAuth2TokenService::Observer::OnRefreshTokenRevoked() before their conversion and hence were previously seeing the removal notification in this corner case. Thus, the behavioral change does not seem to have a concrete impact on consumers one way or the other. Bug: 883722 Change-Id: I131ad8dbe12d73772845fd2eb565cd3477779c36 Reviewed-on: https://chromium-review.googlesource.com/1225878Reviewed-by:
Sylvain Defresne <sdefresne@chromium.org> Commit-Queue: Colin Blundell <blundell@chromium.org> Cr-Commit-Position: refs/heads/master@{#592794}
-
Bo Liu authored
There are a few reports on esoteric android devices where getApplicationRestrictions may throw SecurityException even though it is not documented behavior. Just ignore them. Bug: 886814 Change-Id: Ife0c91f3516ec022912bfb2dc99cfc69ba25f186 Reviewed-on: https://chromium-review.googlesource.com/1235118Reviewed-by:
Bartosz Fabianowski <bartfab@chromium.org> Commit-Queue: Bo <boliu@chromium.org> Cr-Commit-Position: refs/heads/master@{#592793}
-
Mikel Astiz authored
ModelTypeController assumes that the user must be signed in by the time a datatype gets started. This however doesn't hold true for local sync, so we relax the requirement. Some datatypes have similar requirements in their bridge implementations, so we disable those datatypes for local sync. The patch introduces first browser tests for local sync, which would have caught such a basic issue. Bug: 887250 Change-Id: I1bca79478958ac64ee5502e4795f8619ee50e85c Reviewed-on: https://chromium-review.googlesource.com/1235935 Commit-Queue: Mikel Astiz <mastiz@chromium.org> Reviewed-by:
Marc Treib <treib@chromium.org> Reviewed-by:
Julian Pastarmov <pastarmovj@chromium.org> Cr-Commit-Position: refs/heads/master@{#592792}
-
Anders Hartvoll Ruud authored
R=futhark@chromium.org Bug: 641877 Change-Id: I5f12db2690ec02248cb0533b2f18da2613afea98 Reviewed-on: https://chromium-review.googlesource.com/1235723 Commit-Queue: Anders Ruud <andruud@chromium.org> Reviewed-by:
Rune Lillesveen <futhark@chromium.org> Cr-Commit-Position: refs/heads/master@{#592791}
-
chromium-autoroll authored
https://pdfium.googlesource.com/pdfium.git/+log/109aa6d0f673..dd92aa594625 git log 109aa6d0f673..dd92aa594625 --date=short --no-merges --format='%ad %ae %s' 2018-09-20 thestig@chromium.org Fix misc lint errors and other cleanups. Created with: gclient setdep -r src/third_party/pdfium@dd92aa594625 The AutoRoll server is located here: https://autoroll.skia.org/r/pdfium-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=dsinclair@chromium.org Change-Id: I810c9319884a00aea8b64b4ef440ea5e3cd87183 Reviewed-on: https://chromium-review.googlesource.com/1235841Reviewed-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@{#592790}
-
Sean Gilhuly authored
Remember the last call to SetOutputIsSecure, and apply the information when the compositor is configured, or if the gpu process crashes. Bug: 882519 Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel Change-Id: Id212aaae3b2c164575c1d8e92e93e623bd182d69 Reviewed-on: https://chromium-review.googlesource.com/1225290 Commit-Queue: Sean Gilhuly <sgilhuly@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Reviewed-by:
danakj <danakj@chromium.org> Reviewed-by:
kylechar <kylechar@chromium.org> Cr-Commit-Position: refs/heads/master@{#592789}
-
Anders Hartvoll Ruud authored
R=futhark@chromium.org Bug: 641877 Change-Id: I0b4dc43b29f7e30dbc3eab89f22ffa5505e6a333 Reviewed-on: https://chromium-review.googlesource.com/1235999 Commit-Queue: Anders Ruud <andruud@chromium.org> Reviewed-by:
-
Anders Hartvoll Ruud authored
This Options object will soon need to carry information that ValueForCustomProperty needs to act upon. Specifically, it needs to know whether the resolved CSSVariableData should be stored on the ComputedStyle before returning. Also, since the Options object is now available here, let ValueForCustomProperty return nullptr if a variable is disallowed. This avoids an extra PropertyRegistation lookup at one of the callsites. R=futhark@chromium.org Bug: 641877 Change-Id: I85f51ff23d23ab404f6fc133e2017f70dd5aea03 Reviewed-on: https://chromium-review.googlesource.com/1235721 Commit-Queue: Anders Ruud <andruud@chromium.org> Reviewed-by:
-
Etienne Pierre-Doray authored
Original CL intention was: This CL uses ScopedBlockingCall to mark blocking calls in /chromeos/binder. This CL was created by replacing calls to AssertBlockingAllowed() with instantiations of ScopedBlockingCall(MAY_BLOCK). I kindly ask the reviewer to make sure of the following: - ScopedBlockingCall is instantiated in a scope with minimal CPU usage. If this is not the case, ScopedBlockingCall should be instantiated closer to the blocking call. See scoped_blocking_call.h for more info. Please let me know when/where the blocking call happens if this needs to be changed. - Parameter |blocking_type| matches expectation (MAY_BLOCK/WILL_BLOCK). See BlockingType for more info. While I assumed MAY_BLOCK by default, that might not be the best fit if we know that this callsite is guaranteed to block. - The ScopedBlockingCall's scope covers the entirety of the blocking operation previously asserted against by the AssertBlockingAllowed(). This CL was uploaded by git cl split. R=satorux@chromium.org Bug: 874080 Change-Id: Ia8c04385530dbaefee972c8ebffc46c1ec627aa3 Reviewed-on: https://chromium-review.googlesource.com/1191246 Commit-Queue: Etienne Pierre-Doray <etiennep@chromium.org> Reviewed-by:Ryo Hashimoto <hashimoto@chromium.org> Cr-Commit-Position: refs/heads/master@{#592786}
-
Kyoko Muto authored
In this CL, we reuse hashset that control all the assigned slots in the shadowroot for each node, added previous CL. Thanks to the hashset we can find the assigned slot for each node in O(1) order, instead of searching all the slot for each shadow root when we call slot change event. We will improve this implementation in another CL. Result of perftests: https://pinpoint-dot-chromeperf.appspot.com/job/151f9a47640000 Previous implementation CL: crrev.com/c/1179555 See design doc at https://docs.google.com/document/d/1n2iDNkI5bF4B5eefxa0SRSyS_RVchvTNSqezvA4PyF4/edit?usp=sharing Bug: 869308 Change-Id: I96fc4c50d9083eca199c7849db0097e73436983d Reviewed-on: https://chromium-review.googlesource.com/1201513 Commit-Queue: Kyoko Muto <kymuto@google.com> Reviewed-by:
Hayato Ito <hayato@chromium.org> Cr-Commit-Position: refs/heads/master@{#592785}
-
Anders Hartvoll Ruud authored
In the near future, it will be necessary for ValueForCustomProperty to return a CSSVariableData which may not be stored elsewhere. This is because we need to do a "non-destructive" pre-resolve of registered custom properties that are used before high priority properties are applied. R=futhark@chromium.org Bug: 641877 Change-Id: Idb1ab4ba7aae77187a4fd86877a0246e56fc82a4 Reviewed-on: https://chromium-review.googlesource.com/1235936Reviewed-by:
-
Dave Tapuska authored
Using the appropriate type gets rid of a checked cast and a truncation. BUG=879657 Change-Id: I30e6aa1f28ebcd6e245a95a8662a212e72986829 Reviewed-on: https://chromium-review.googlesource.com/1234016 Commit-Queue: Dave Tapuska <dtapuska@chromium.org> Reviewed-by:
-
Justin Cohen authored
Bug: 807330 Cq-Include-Trybots: luci.chromium.try:ios-simulator-cronet;luci.chromium.try:ios-simulator-full-configs Change-Id: I988192d63f2189524b86c5ccd40f64fe42aebf40 Reviewed-on: https://chromium-review.googlesource.com/1228515 Commit-Queue: Justin Cohen <justincohen@chromium.org> Reviewed-by:
Sergio Collazos <sczs@chromium.org> Cr-Commit-Position: refs/heads/master@{#592782}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/ecfe498c1a1a..a6fb5c9cdd1b Created with: gclient setdep -r src-internal@a6fb5c9cdd1b 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: Ic06aaab2918f506b88ea657707e4b4b3cc8c84f9 Reviewed-on: https://chromium-review.googlesource.com/1235840Reviewed-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@{#592781}
-
Stephane Zermatten authored
This change reads the original intent, looks for parameters that are meant for Autofill Assistant and allow scripts to check these in preconditions. Bug: 806868 Change-Id: I8bd6b51cf281d1f21ce2ccf6128b7345290cab0a Reviewed-on: https://chromium-review.googlesource.com/1225696 Commit-Queue: Stephane Zermatten <szermatt@chromium.org> Reviewed-by:
Ganggui Tang <gogerald@chromium.org> Cr-Commit-Position: refs/heads/master@{#592780}
-
Gemene Narcis authored
This CL allows cleaning of blacklisted duplicates for iOS platform. Bug: 862930 Cq-Include-Trybots: luci.chromium.try:ios-simulator-cronet;luci.chromium.try:ios-simulator-full-configs Change-Id: I44e9fb90181781c261760ac0d933f8917b7d2910 Reviewed-on: https://chromium-review.googlesource.com/1233234Reviewed-by:
Vaclav Brozek <vabr@chromium.org> Reviewed-by:
Jan Wilken Dörrie <jdoerrie@chromium.org> Commit-Queue: Narcis Gemene <gemene@google.com> Cr-Commit-Position: refs/heads/master@{#592779}
-
Nico Weber authored
This reverts commit f6a8902e. Reason for revert: relanding with lto for android disabled until things are sorted out. Original change's description: > Revert "Roll clang 340925:342523." > > This reverts commit 34893e97. > > Reason for revert: New failures on Android in computeKnownBits(), looks like an LTO problem. http://crbug.com/887272 > > Original change's description: > > Roll clang 340925:342523. > > > > Ran `tools/clang/scripts/upload_revision.py 342523`. > > > > Bug: 880827 > > Change-Id: I8f747ab4a2de74a0f0b4b5a201d37e111f323077 > > Reviewed-on: https://chromium-review.googlesource.com/1232590 > > Reviewed-by: Reid Kleckner <rnk@chromium.org> > > Commit-Queue: Nico Weber <thakis@chromium.org> > > Cr-Commit-Position: refs/heads/master@{#592531} > > TBR=thakis@chromium.org,hans@chromium.org,rnk@chromium.org > > Change-Id: Idee414178ab15058aa080f670585cee81e0f8ac5 > No-Presubmit: true > No-Tree-Checks: true > No-Try: true > Bug: 880827 > Reviewed-on: https://chromium-review.googlesource.com/1236003 > Reviewed-by: Egor Pasko <pasko@chromium.org> > Commit-Queue: Egor Pasko <pasko@chromium.org> > Cr-Commit-Position: refs/heads/master@{#592765} TBR=pasko@chromium.org,thakis@chromium.org,hans@chromium.org,rnk@chromium.org Change-Id: I26ea97e83cfebcec0670e79683fe0db7f993c1a7 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 880827 Reviewed-on: https://chromium-review.googlesource.com/1236174 Commit-Queue: Nico Weber <thakis@chromium.org> Reviewed-by:
-
Yuki Awano authored
- Touch events come in screen pixel. We need to use in screen pixel conversion here as the comment in the file says. that touch exploration works correctly on the touch controller. Bug: 887222 Test: Enable spoken feedback on touch controller of CfM unit. Confirm Change-Id: Ic7a83eb5d9c4690b41a184ab85d5421e0468934e Reviewed-on: https://chromium-review.googlesource.com/1235489 Commit-Queue: David Tseng <dtseng@chromium.org> Reviewed-by:
David Tseng <dtseng@chromium.org> Cr-Commit-Position: refs/heads/master@{#592777}
-
Charles Zhao authored
Both tests fail because the proto serialization is not deterministic. Change-Id: I3b99faa03c55b3333c1d03e05258985e6f8ddaa5 Bug: 884140 Change-Id: I3b99faa03c55b3333c1d03e05258985e6f8ddaa5 Reviewed-on: https://chromium-review.googlesource.com/1233096 Commit-Queue: Charles . <charleszhao@chromium.org> Reviewed-by:
Xiyuan Xia <xiyuan@chromium.org> Cr-Commit-Position: refs/heads/master@{#592776}
-
Mikel Astiz authored
This is a mitigation to what are believed to be bugs in the bridges, which may forget to appropriately report local deletions to the processor, leading to orphan sync metadata. We have recently instrumented a UMA metric ("Sync.ModelTypeOrphanMetadata") to assess the severity of the issue, and the collected data suggests that the problem is not specific to a single datatype. While we investigate each bridge individually, a reasonable workaround is to let the processor remove the orphaned metadata and untrack the entity. Bugs in the bridges should still be surfaced by the aforementioned UMA metric, although absolute numbers should tend to be smaller after this patch, because issues will get fixed after emitting the metric once. Bug: 875671,871733 Change-Id: Ieb06692f46739d73ce6f04115c25e14198ade1dd Reviewed-on: https://chromium-review.googlesource.com/1233676 Commit-Queue: Mikel Astiz <mastiz@chromium.org> Reviewed-by:Jan Krcal <jkrcal@chromium.org> Cr-Commit-Position: refs/heads/master@{#592775}
-
Mohamed Amir Yosef authored
This CL adds the functionality to store the ids of lazy subscriptions in SharedPeferences. Later CL will consume this information to decide whether the FCM message should be deferred until there are visible activities or not. Bug: 882887 Change-Id: Ic28dbfeb2b77020cd9b5e02b79f055e477d55aed Reviewed-on: https://chromium-review.googlesource.com/1221532Reviewed-by:
Peter Conn <peconn@chromium.org> Reviewed-by:
Kenneth Russell <kbr@chromium.org> Reviewed-by:
Peter Beverloo <peter@chromium.org> Commit-Queue: Mohamed Amir Yosef <mamir@chromium.org> Cr-Commit-Position: refs/heads/master@{#592774}
-
Matthew Cary authored
android_build_tools/art was recently added, and pulls in several binaries that should be ignored by git. TBR: agrieve@chromium.org Change-Id: I2fb97c175707225237acbee80f4c01cdb0cdad44 Reviewed-on: https://chromium-review.googlesource.com/1235726Reviewed-by:
Matthew Cary <mattcary@chromium.org> Commit-Queue: Matthew Cary <mattcary@chromium.org> Cr-Commit-Position: refs/heads/master@{#592773}
-
Mathias Carlen authored
R=gogerald@chromium.org Bug: 806868 Change-Id: I7515c9fb448b9324b81dec958e0c212192741188 Reviewed-on: https://chromium-review.googlesource.com/1228059 Commit-Queue: Mathias Carlen <mcarlen@chromium.org> Reviewed-by:
-
Jan Krcal authored
This CL makes a cleanup in autofill sync unit-test, reducing code duplication and getting rid of custom fakes that can be mocked in one line. It also renames another existing fake to achieve more consistency in naming (w.r.t. gmock). This CL precedes a change in the AutofillWebDataBackend interface, making it easier to implement. Bug: 853688 Change-Id: Iaf9ec6151caa77e9b81297f50c061835443cfadd Reviewed-on: https://chromium-review.googlesource.com/1235716Reviewed-by:
Sebastien Seguin-Gagnon <sebsg@chromium.org> Commit-Queue: Sebastien Seguin-Gagnon <sebsg@chromium.org> Cr-Commit-Position: refs/heads/master@{#592771}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/1b8671f08f41..ecfe498c1a1a Created with: gclient setdep -r src-internal@ecfe498c1a1a 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: I8bb96b3b8e967bfc07accec533508d1478486a7e Reviewed-on: https://chromium-review.googlesource.com/1235839Reviewed-by:
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/ee002e61857b..207cfdfbd889 git log ee002e61857b..207cfdfbd889 --date=short --no-merges --format='%ad %ae %s' 2018-09-20 artit@webrtc.org Added support of getting coverage on mac Created with: gclient setdep -r src/third_party/webrtc@207cfdfbd889 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 BUG=chromium:844647 TBR=webrtc-chromium-sheriffs-robots@google.com Change-Id: I392429d4014348877087de19a4812632cbad9f38 Reviewed-on: https://chromium-review.googlesource.com/1235837Reviewed-by:
-
Thomas Tangl authored
Apparently creating a new image out of a bitmap leads to crashes in |Image::ToImageSkia|. This CL removes the conversion between images inside PrepareAvatarImage() to speculatively fix the issue. See bug report for details. Bug: 882330 Change-Id: Ifd7df91f5933ce0159ce223bf61fd9dcfac9356d Reviewed-on: https://chromium-review.googlesource.com/1228194 Commit-Queue: Thomas Tangl <tangltom@chromium.org> Reviewed-by:
-
chromium-autoroll authored
https://chromium.googlesource.com/catapult.git/+log/8495ffe55979..985f6fe58181 git log 8495ffe55979..985f6fe58181 --date=short --no-merges --format='%ad %ae %s' 2018-09-20 anthonyalridge@google.com Handle inputs with zero range for plots. Created with: gclient setdep -r src/third_party/catapult@985f6fe58181 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:866423 TBR=sullivan@chromium.org Change-Id: I80ec2cd27533b784f212a413532c4a7ee39e820f Reviewed-on: https://chromium-review.googlesource.com/1235838Reviewed-by:
-
Stuart Langley authored
This will always append the "supportsTeamDrives=true" parameters to drive query strings, so lots of mechanical test related changes to update the expected query string. Change-Id: Ic98c558f74195dc27550af5a06aab78fdb413e57 Reviewed-on: https://chromium-review.googlesource.com/1235454Reviewed-by:
Sam McNally <sammc@chromium.org> Commit-Queue: Stuart Langley <slangley@chromium.org> Cr-Commit-Position: refs/heads/master@{#592766}
-
Egor Pasko authored
This reverts commit 34893e97. Reason for revert: New failures on Android in computeKnownBits(), looks like an LTO problem. http://crbug.com/887272 Original change's description: > Roll clang 340925:342523. > > Ran `tools/clang/scripts/upload_revision.py 342523`. > > Bug: 880827 > Change-Id: I8f747ab4a2de74a0f0b4b5a201d37e111f323077 > Reviewed-on: https://chromium-review.googlesource.com/1232590 > Reviewed-by: Reid Kleckner <rnk@chromium.org> > Commit-Queue: Nico Weber <thakis@chromium.org> > Cr-Commit-Position: refs/heads/master@{#592531} TBR=thakis@chromium.org,hans@chromium.org,rnk@chromium.org Change-Id: Idee414178ab15058aa080f670585cee81e0f8ac5 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 880827 Reviewed-on: https://chromium-review.googlesource.com/1236003Reviewed-by:
Egor Pasko <pasko@chromium.org> Commit-Queue: Egor Pasko <pasko@chromium.org> Cr-Commit-Position: refs/heads/master@{#592765}
-
Florian Mayer authored
Change-Id: I764fcf0f349d5c78f8029408530f783ae9301b76 Reviewed-on: https://chromium-review.googlesource.com/1235934 Commit-Queue: Primiano Tucci <primiano@chromium.org> Reviewed-by:
Primiano Tucci <primiano@chromium.org> Cr-Commit-Position: refs/heads/master@{#592764}
-
Balazs Engedy authored
Bug: 885165 Change-Id: I207457e481ef89ffcf0d91ee530cea2d3c33649a Reviewed-on: https://chromium-review.googlesource.com/1230675 Commit-Queue: Balazs Engedy <engedy@chromium.org> Reviewed-by:
-
Gauthier Ambard authored
This CL removes the TabHistory popup code as it was only used pre-UI Refresh. Bug: 800266 Cq-Include-Trybots: luci.chromium.try:ios-simulator-cronet;luci.chromium.try:ios-simulator-full-configs Change-Id: I140bbed84ef69efb81c67130186ec72cca684961 Reviewed-on: https://chromium-review.googlesource.com/1233853 Commit-Queue: Gauthier Ambard <gambard@chromium.org> Reviewed-by:
Mark Cogan <marq@chromium.org> Cr-Commit-Position: refs/heads/master@{#592762}
-
Marc Treib authored
This moves a bunch of helper functions around secondary account support from single_client_secondary_account_sync_test.cc into their own files. This is in preparation for adding more integration tests that will make use of these. Bug: 885211 Change-Id: I1f30b2425951933f6f9251f35c4aafb7e1cdb663 Reviewed-on: https://chromium-review.googlesource.com/1233704Reviewed-by:
-
