- 26 Apr, 2019 40 commits
-
-
chromium-autoroll authored
https://dawn.googlesource.com/dawn.git/+log/15d4c2e63b72..9286adcb0f7e git log 15d4c2e63b72..9286adcb0f7e --date=short --no-merges --format='%ad %ae %s' 2019-04-26 shaobo.yan@intel.com Add end2end test for all vertex formats 2019-04-26 cwallez@chromium.org Metal: Invert CW and CCW because we compile with flip Y Created with: gclient setdep -r src/third_party/dawn@9286adcb0f7e The AutoRoll server is located here: https://autoroll.skia.org/r/dawn-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:dawn-linux-x64-deps-rel;luci.chromium.try:dawn-mac-x64-deps-rel;luci.chromium.try:dawn-win10-x64-deps-rel;luci.chromium.try:dawn-win10-x86-deps-rel TBR=cwallez@chromium.org Change-Id: I29075ea071daef544200f9eb6b6b6fff4c86a8aa Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1584755Reviewed-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@{#654509}
-
Wei Li authored
Since View's metadata already includes 'Visible' information now, we can get rid of direct query about visibility information from View elements. Also updated the tests to reflect these changes. BUG=954675 Change-Id: I82a1bb1459984d54c8a71b53832e45338e295e6d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1585070Reviewed-by:
Leonard Grey <lgrey@chromium.org> Commit-Queue: Wei Li <weili@chromium.org> Cr-Commit-Position: refs/heads/master@{#654508}
-
Francois Doray authored
This is a reland of e9dec932. The change was initially reverted due to a crash encountered when two successive ScopedBlockingCalls were observed. Successive ScopedBlockingCalls led to CallbackMayRunLong being called twice on the same callback, which is not expected by the API. To fix this issue, the observer is cleared after a call to CallbackMayRunLong, ensuring that CallbackMayRunLong is called at most once per callback. Original change's description: > ThreadPool: PlatformNativeWorkerPoolWin should use CallbackMayRunLong for blocking tasks > > The Windows Thread Pool API provides a CallbackMayRunLong method to > indicate that a callback may not return quickly. The thread pool can use > this information to better determine when a new thread should be > created. > > This CL teaches PlatformNativeWorkerPoolWin about ScopedBlockingCall in > order to determine whether a callback will return quickly. A > BlockingObserver is registered before running a task in the work > callback. If the task contains a ScopedBlockingCall, the observer is > notified, and will call CallbackMayRunLong on the appropriate > PTP_CALLBACK_INSTANCE. > > Bug: 756547 > Change-Id: If04d2c5e01b00960dc510e94ff89525036c2ae67 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1574229 > Commit-Queue: François Doray <fdoray@chromium.org> > Reviewed-by: François Doray <fdoray@chromium.org> > Cr-Commit-Position: refs/heads/master@{#653252} Bug: 756547 Change-Id: Ic7c1a93b1429b333fdd4d9a574e232d5c9bdcb2e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1582219Reviewed-by:
François Doray <fdoray@chromium.org> Commit-Queue: Aditya Keerthi <adityakeerthi@google.com> Cr-Commit-Position: refs/heads/master@{#654507}
-
Cammie Smith Barnes authored
For shared workers, we will double-key the network cache by script origin, i.e. |request_initiator|. Here we test that this origin is as expected for shared workers. Bug: 918868 Change-Id: Iceca9b2e8bbaf1717afeea3ee68f5d4bc352cee1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1574263 Commit-Queue: Cammie Smith Barnes <cammie@chromium.org> Reviewed-by:
Shivani Sharma <shivanisha@chromium.org> Reviewed-by:
Matt Falkenhagen <falken@chromium.org> Cr-Commit-Position: refs/heads/master@{#654506}
-
Joshua Pawlicki authored
Bug: 931177 Change-Id: Ie699786336d84ccde017466606d26073f9d1eb8b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1585961 Commit-Queue: Joshua Pawlicki <waffles@chromium.org> Commit-Queue: Tommy Nyquist <nyquist@chromium.org> Auto-Submit: Joshua Pawlicki <waffles@chromium.org> Reviewed-by:
Tommy Nyquist <nyquist@chromium.org> Cr-Commit-Position: refs/heads/master@{#654505}
-
David Benjamin authored
Bug: 820198 Change-Id: Ie9c08c97d217fedda206635c79a9881688aac6b4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1575170 Commit-Queue: David Benjamin <davidben@chromium.org> Reviewed-by:
Eric Roman <eroman@chromium.org> Cr-Commit-Position: refs/heads/master@{#654504}
-
Raymond Toy authored
Set number of outputs to 0 as required by the spec. This requires some small refactoring of AudioBasicInspectorHandler too. One Chrome test is also moved to WPT. Manually tested with Firefox (nightly) which passes all the tests. Spec: https://webaudio.github.io/web-audio-api/#mediastreamaudiodestinationnode Feature: https://www.chromestatus.com/feature/5702493226926080# Bug: 691806 Change-Id: Ic17b4f248b606701dfa3ca54892754d7ebe4e749 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1580202Reviewed-by:
Hongchan Choi <hongchan@chromium.org> Reviewed-by:
Kent Tamura <tkent@chromium.org> Commit-Queue: Raymond Toy <rtoy@chromium.org> Cr-Commit-Position: refs/heads/master@{#654503}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/75c4cbfa717a..38526935062e Created with: gclient setdep -r src-internal@38526935062e 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. CQ_INCLUDE_TRYBOTS=luci.chrome.try:linux-chromeos-chrome TBR=andruud@chromium.org,alexmos@chromium.org,horo@chromium.org,adithyas@chromium.org Change-Id: I2f0de88b33a652071aab4325b3ec02f55504f6aa Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1584750Reviewed-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@{#654502}
-
Carlos Caballero authored
ScopedTaskEnvironment::ExecutionMode is becoming ScopedTaskEnvironment::ThreadPoolExecutionMode This CL was uploaded by git cl split. R=gab@chromium.org Bug: 708584 Change-Id: Ie47875c39164799cb87d1358c22fbc08c45b2c7f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1583886 Auto-Submit: Carlos Caballero <carlscab@google.com> Reviewed-by:
Gabriel Charette <gab@chromium.org> Commit-Queue: Gabriel Charette <gab@chromium.org> Cr-Commit-Position: refs/heads/master@{#654501}
-
sczs authored
This is being done for three reasons mainly: - The delegate shouldn't be responsibly of manipulating the InfobarManager and creating the Infobars its being a delegate of. - This prevents dependency cycles since now InfobarCoordinator can include IOSChromeSavePasswordInfoBarDelegate. - While trying to test IOSChromeSavePasswordInfoBarDelegate having its default constructor private was making everything more complicated since there was more setup needed. Bug: 945478 Change-Id: I223d6ada2b939d9037bf030728a588051e28c115 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1585379 Commit-Queue: Sergio Collazos <sczs@chromium.org> Reviewed-by:
Vasilii Sukhanov <vasilii@chromium.org> Cr-Commit-Position: refs/heads/master@{#654500}
-
Daniel Cheng authored
Bug: 841899 Tbr: rdevlin.cronin@chromium.org Change-Id: Ifa01917f00bab75db998abddf4d487fb1b049990 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1584598 Commit-Queue: Daniel Cheng <dcheng@chromium.org> Auto-Submit: Daniel Cheng <dcheng@chromium.org> Reviewed-by:
danakj <danakj@chromium.org> Cr-Commit-Position: refs/heads/master@{#654499}
-
Daniel Cheng authored
Bug: 841899 Change-Id: If27e6942058fba40ee59ac10a64ce0c97ed5b179 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1584926Reviewed-by:
David Jacobo <djacobo@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Commit-Queue: Daniel Cheng <dcheng@chromium.org> Auto-Submit: Daniel Cheng <dcheng@chromium.org> Cr-Commit-Position: refs/heads/master@{#654498}
-
Xianzhu Wang authored
We chose to skip direct transform/opacity if the property is animating in compositor in crrev.com/c/1565467 (fast-path for simple transform change) to reduce risk of it. We observed that it caused regressions for several benchmarks. Now allow direct transform/opacity on the end of animation in this separate CL. We already have several test cases testing the situation. Bug: 954611 Change-Id: I6a8516dba92f6a3b02efd664bbc12315fe94d63b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1585263Reviewed-by:
Philip Rogers <pdr@chromium.org> Reviewed-by:
vmpstr <vmpstr@chromium.org> Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org> Cr-Commit-Position: refs/heads/master@{#654497}
-
Sergey Ulanov authored
This reverts commit 4a436e48. Reason for revert: The problem was fixed in SDK Original change's description: > [Fuchsia] Disable media_unittests failing in new SDK > > New SDK removed some services that the tests depend on, which broke 2 > tests: FuchsiaVideoDecoderTest.H264 and AudioOutputTest.Play200HzTone. > Disabling these tests temporarily until the problem is resolved. > > TBR=wez@chromium.org,maxmorin@chromium.org > > Bug: 956446 > Change-Id: I16f69249f49df6fc6c874196a17bca9973f154dd > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1582034 > Reviewed-by: Sergey Ulanov <sergeyu@chromium.org> > Commit-Queue: Sergey Ulanov <sergeyu@chromium.org> > Cr-Commit-Position: refs/heads/master@{#653924} TBR=wez@chromium.org,sergeyu@chromium.org,maxmorin@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 956446 Change-Id: Idd9fee71cdb802490fe422f8a1e44dfff8d62b3c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1585395Reviewed-by:
Sergey Ulanov <sergeyu@chromium.org> Reviewed-by:
Wez <wez@chromium.org> Commit-Queue: Sergey Ulanov <sergeyu@chromium.org> Cr-Commit-Position: refs/heads/master@{#654496}
-
Andrew Grieve authored
This reverts commit ce3df784. Reason for reland: Updated resource_sizes.py with renamed .ap_ path Original change's description: > Revert "Android: Compile .proto and .arsc resources at the same time" > > This reverts commit 697c9ab8. > > Reason for revert: Broke resource_sizes.py > > Original change's description: > > Android: Compile .proto and .arsc resources at the same time > > > > Saves a couple of seconds of build time for base bundle modules, > > and simplifies the GN logic for resources. > > > > Also fixes chrome_apk using unoptimized arsc file when lemon is > > enabled (broken by 2e296d82). > > > > Simplifies temp file usage in compile_resources.py by having all > > outputs go to the staging directory. > > > > Removes cruft: > > * Unused --no-compress flag > > * Unnecessary "Touch()" of R.txt > > > > Bug: 950233 > > Change-Id: Ida77380e8038002435ec3d320105d9feaa3c2136 > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1568568 > > Commit-Queue: Andrew Grieve <agrieve@chromium.org> > > Reviewed-by: Tibor Goldschwendt <tiborg@chromium.org> > > Cr-Commit-Position: refs/heads/master@{#653275} > > TBR=agrieve@chromium.org,tiborg@chromium.org > > Change-Id: I76bd9cf76b357156efa2848613ab576486d18476 > No-Presubmit: true > No-Tree-Checks: true > No-Try: true > Bug: 950233, 955959 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1581988 > Reviewed-by: Andrew Grieve <agrieve@chromium.org> > Commit-Queue: Andrew Grieve <agrieve@chromium.org> > Cr-Commit-Position: refs/heads/master@{#653653} TBR=agrieve@chromium.org,tiborg@chromium.org Bug: 950233, 955959 Change-Id: I73367591e5d88fad86ebb24827238ca064a0f55c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1585941Reviewed-by:
Andrew Grieve <agrieve@chromium.org> Commit-Queue: Andrew Grieve <agrieve@chromium.org> Cr-Commit-Position: refs/heads/master@{#654495}
-
Sigurdur Asgeirsson authored
Nodes in the PM graph are now self-indexed rather than by id. A stable opaque id is still provided for serialization purposes. Bug: 910288 Change-Id: I89ff8aef3763ed9f4406498457cb224c5d38ad29 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1585004Reviewed-by:
Will Harris <wfh@chromium.org> Reviewed-by:
Chris Hamilton <chrisha@chromium.org> Reviewed-by:
Brian White <bcwhite@chromium.org> Commit-Queue: Sigurður Ásgeirsson <siggi@chromium.org> Cr-Commit-Position: refs/heads/master@{#654494}
-
jdoerrie authored
TBR=jdoerrie@chromium.org Bug: NONE Change-Id: I1ac9128815d5f59127c6618227ff3ac42d6f7193 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1583737Reviewed-by:
Jan Wilken Dörrie <jdoerrie@chromium.org> Commit-Queue: Jan Wilken Dörrie <jdoerrie@chromium.org> Cr-Commit-Position: refs/heads/master@{#654493}
-
khmel@chromium.org authored
This fixes 2 issues, first that in case of CPU heavy load, one CPU might work for one thread for a long time, in this case if thread was activated before zoomed view time it would be wrongly considered as an idle thread. Second issue is band selection SVG captures event that lead to incorrect detailed view activation in case next clicks is done in bounds of this selection. TEST=Locally BUG=b:122555793 Change-Id: I355eafa8dbc14bb66527522970354876e0d54a6e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1585248Reviewed-by:
Xiyuan Xia <xiyuan@chromium.org> Commit-Queue: Yury Khmel <khmel@chromium.org> Cr-Commit-Position: refs/heads/master@{#654492}
-
Dale Curtis authored
FFmpeg indicates more than this will cause issues, and it certainly causes OOM errors for 8K H264 content. VP9 playback doesn't seem to benefit at all from going from 16 - 32 threads. BUG=893984 R=sandersd Change-Id: Ibaa2dfac94cbdd4f42f728b579c063a960b4f973 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1584567 Auto-Submit: Dale Curtis <dalecurtis@chromium.org> Reviewed-by:
Dan Sanders <sandersd@chromium.org> Commit-Queue: Dale Curtis <dalecurtis@chromium.org> Cr-Commit-Position: refs/heads/master@{#654491}
-
Piotr Bialecki authored
Bump expiry_milestone for flags owned by xr-dev@. Bug: 954532,929789 Change-Id: I1b7cb111c71976fee413033a4eb1d7ea1881232f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1582614Reviewed-by:
Kinuko Yasuda <kinuko@chromium.org> Reviewed-by:
Bill Orr <billorr@chromium.org> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Commit-Queue: Piotr Bialecki <bialpio@chromium.org> Cr-Commit-Position: refs/heads/master@{#654490}
-
kylechar authored
A gpu::Mailbox is needed to do something useful with the texture in GLOutputSurfaceOffscreen. Convert it to use SharedImageInterface to generate a gpu::Mailbox and then GL texture from that. Bug: 601869 Change-Id: Id7da76e06bf119bc0d679132330b75bc1662836a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1585059Reviewed-by:
Jonathan Backer <backer@chromium.org> Commit-Queue: kylechar <kylechar@chromium.org> Cr-Commit-Position: refs/heads/master@{#654489}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/7a2205ca50c8..c62691b671a9 git log 7a2205ca50c8..c62691b671a9 --date=short --no-merges --format='%ad %ae %s' 2019-04-26 tandrii@chromium.org git_cache: print if cache bundle under the same number already exists. Created with: gclient setdep -r src/third_party/depot_tools@c62691b671a9 The AutoRoll server is located here: https://autoroll.skia.org/r/depot-tools-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. BUG=chromium:943696 TBR=agable@chromium.org Change-Id: I8e0b641a23ab537d2152b3fe5c38a1c4cb758345 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1585932Reviewed-by:
-
Francois Doray authored
Change-Id: I958f00fcd81c261515db469aa913c7945862db26 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1582221Reviewed-by:
Yury Khmel <khmel@chromium.org> Commit-Queue: François Doray <fdoray@chromium.org> Cr-Commit-Position: refs/heads/master@{#654487}
-
Aaron Krajeski authored
Tests needed to be rebaselined due to this CL: https://chromium-review.googlesource.com/c/chromium/src/+/1486711 Bug: 909937 Change-Id: If609d4e1420b4923b7e1ce68a5069d41cfb779be Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1585278Reviewed-by:
Antoine Labour <piman@chromium.org> Commit-Queue: Aaron Krajeski <aaronhk@chromium.org> Cr-Commit-Position: refs/heads/master@{#654486}
-
Greg Kerr authored
This deletes calls to InitializeSandbox that are no longer called. These are processes which only use the V2 sandbox. Bug: 917445 Change-Id: I87b96a4f4071438eeaf68e6d07ddc2c9813b3e58 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1582967Reviewed-by:
Robert Sesek <rsesek@chromium.org> Reviewed-by:
Jochen Eisinger <jochen@chromium.org> Auto-Submit: Greg Kerr <kerrnel@chromium.org> Commit-Queue: Jochen Eisinger <jochen@chromium.org> Cr-Commit-Position: refs/heads/master@{#654485}
-
Jan Krcal authored
This reverts commit a75e19c4. Reason for reland: fixed the test flakiness. Original change's description: > Revert "[AF Wallet] Ignore remote metadata deletions in USS sync" > > This reverts commit 948191bb. > > Reason for revert: introduces flakiness in integration tests > > Original change's description: > > [AF Wallet] Ignore remote metadata deletions in USS sync > > > > This CL changes behavior of the wallet_metadata sync bridge to ignore > > remote deletions. This is safe as every deletion should be eventually > > processed locally and for corner cases there is anyway already a GC > > routine. > > > > This is motivated by observed ping-pongs of deletions-creations between > > clients running Directory code and clients running USS code, leading > > to considerably increased number of address conversions on USS. This > > CL breaks these ping-pongs and should get the conversion counts on > > comparable levels. > > > > Bug: 953693 > > Change-Id: I1a30f51d4727a08f84ef33091089d2a7a366b4df > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1583896 > > Commit-Queue: Jan Krcal <jkrcal@chromium.org> > > Reviewed-by: Mikel Astiz <mastiz@chromium.org> > > Cr-Commit-Position: refs/heads/master@{#654413} > > TBR=jkrcal@chromium.org,mastiz@chromium.org > > Change-Id: Ia8afa93aa834101d154e1a1a3db3996f686d1786 > No-Presubmit: true > No-Tree-Checks: true > No-Try: true > Bug: 953693 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1583711 > Reviewed-by: Jan Krcal <jkrcal@chromium.org> > Commit-Queue: Jan Krcal <jkrcal@chromium.org> > Cr-Commit-Position: refs/heads/master@{#654471} TBR=jkrcal@chromium.org,mastiz@chromium.org Change-Id: I737e61569db88219f10db68817b03b5467389df4 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 953693 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1584310Reviewed-by:
Mikel Astiz <mastiz@chromium.org> Reviewed-by:
Mohamed Amir Yosef <mamir@chromium.org> Reviewed-by:
Jan Krcal <jkrcal@chromium.org> Commit-Queue: Jan Krcal <jkrcal@chromium.org> Cr-Commit-Position: refs/heads/master@{#654484}
-
Scott Violet authored
This code was split when we had two nearly identical window types. That is no longer the case, so this template can be nuked. BUG=none TEST=none Change-Id: I876e18d1335c74e2ab34e1ba34d423f60bf6babf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1585160 Commit-Queue: Scott Violet <sky@chromium.org> Reviewed-by:
Michael Wasserman <msw@chromium.org> Cr-Commit-Position: refs/heads/master@{#654483}
-
Raymond Toy authored
Previously we only tested the result of getFreqencyResponse for peaking filters. Add test for all the other filters as well. Bug: 390266 Change-Id: I7cba2a0dbcfaf3e6c0fec0a92eaedf8779f2d361 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1584368 Commit-Queue: Raymond Toy <rtoy@chromium.org> Reviewed-by:
-
Brian Sheedy authored
The VR instrumentation tests have always taken a while to run with a Daydream View paired due to the number of tests. For whatever reason, they take even longer on Android P, causing them to fairly regularly hit the 1 hour timeout on the bots. So, enable sharding for the Daydream View version of the tests. Bug: 953990 Change-Id: Ife442148e4799318f0665a4dfa345fbeff47a361 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1585251Reviewed-by:
Ben Pastene <bpastene@chromium.org> Commit-Queue: Brian Sheedy <bsheedy@chromium.org> Cr-Commit-Position: refs/heads/master@{#654481}
-
Scott Violet authored
I had to do this in a separate step as git doesn't handle moves particularly well. BUG=none TEST=none Change-Id: I6e948957013eb6b7db97c12d4c980ad35a7b1827 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1584842 Commit-Queue: Scott Violet <sky@chromium.org> Reviewed-by:
James Cook <jamescook@chromium.org> Cr-Commit-Position: refs/heads/master@{#654480}
-
chromium-autoroll authored
https://chromium.googlesource.com/external/github.com/KhronosGroup/SPIRV-Tools.git/+log/2de3e3c02f29..dca3ea5e1719 git log 2de3e3c02f29..dca3ea5e1719 --date=short --no-merges --format='%ad %ae %s' 2019-04-26 clouds.flowing@gmail.com fix example.cpp (#2540) Created with: gclient setdep -r src/third_party/SPIRV-Tools/src@dca3ea5e1719 The AutoRoll server is located here: https://autoroll.skia.org/r/spirv-tools-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=dsinclair@chromium.org,geofflang@chromium.org Change-Id: I82fe9d860669eeaef8a15dbe80a791ac9e5b7d3c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1585926Reviewed-by:
-
chromium-autoroll authored
https://chromium.googlesource.com/catapult.git/+log/517f7f858d97..d7f22e29c4a1 git log 517f7f858d97..d7f22e29c4a1 --date=short --no-merges --format='%ad %ae %s' 2019-04-26 simonhatch@chromium.org Dashboard - Calculate comparison_magnitude for custom ranges Created with: gclient setdep -r src/third_party/catapult@d7f22e29c4a1 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:894529 TBR=eyaich@chromium.org Change-Id: I24cacdc410c6ffdb1fcf240584af2ae3b18bcd6f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1585925Reviewed-by:
-
siashah authored
The Save button is enabled based on the error type value. Before: https://screenshot.googleplex.com/xujMptYhWxW After: https://screenshot.googleplex.com/jTj8SnNL82A Bug: 955825 Change-Id: I123c72d23342e5c04f8ce3e4c02610720b6a7231 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1584166Reviewed-by:
Theresa <twellington@chromium.org> Reviewed-by:
Jared Saul <jsaul@google.com> Reviewed-by:
Rouslan Solomakhin <rouslan@chromium.org> Commit-Queue: Theresa <twellington@chromium.org> Auto-Submit: Siddharth Shah <siashah@chromium.org> Cr-Commit-Position: refs/heads/master@{#654477}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/6e345f4e28d3..999374532cec git log 6e345f4e28d3..999374532cec --date=short --no-merges --format='%ad %ae %s' 2019-04-26 eseckler@google.com Merge "processor: Tokenizer support for TrackEvent + InternedData" Created with: gclient setdep -r src/third_party/perfetto@999374532cec 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: I58a49e0cc896f363a75474f680166bc10ebe4a9a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1585923Reviewed-by:
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/d3aeecd01069..d521ce39e99f git log d3aeecd01069..d521ce39e99f --date=short --no-merges --format='%ad %ae %s' 2019-04-26 egdaniel@google.com Test vulkan msaa on test bots. Created with: gclient setdep -r src/third_party/skia@d521ce39e99f 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-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 TBR=mtklein@chromium.org Change-Id: I6e252b23bbd4c58e4b4e3a8fde07b7ca0bc3dff5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1585924Reviewed-by:
-
Nicolas Ouellet-payeur authored
Bug: 957003 Change-Id: I60f2c62d75dfc2a7d1b86f5b9880151d5d11c78d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1585465Reviewed-by:
Owen Min <zmin@chromium.org> Commit-Queue: Nicolas Ouellet-Payeur <nicolaso@chromium.org> Cr-Commit-Position: refs/heads/master@{#654474}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/419c9cd57073..75c4cbfa717a Created with: gclient setdep -r src-internal@75c4cbfa717a 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. CQ_INCLUDE_TRYBOTS=luci.chrome.try:linux-chromeos-chrome TBR=andruud@chromium.org,alexmos@chromium.org,horo@chromium.org,adithyas@chromium.org Change-Id: I10b65df10fdb516c26b0dd3f695e74e1bada10c0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1585921Reviewed-by:
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/eb37b1394300..e670fd97951a git log eb37b1394300..e670fd97951a --date=short --no-merges --format='%ad %ae %s' 2019-04-26 srte@webrtc.org Adds getter for FieldTrialParameter keys. Created with: gclient setdep -r src/third_party/webrtc@e670fd97951a 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. TBR=webrtc-chromium-sheriffs-robots@google.com Change-Id: Ie183d7aaf9756d506940118a1c822303f1b7938b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1585922Reviewed-by:
-
Jan Krcal authored
This reverts commit 948191bb. Reason for revert: introduces flakiness in integration tests Original change's description: > [AF Wallet] Ignore remote metadata deletions in USS sync > > This CL changes behavior of the wallet_metadata sync bridge to ignore > remote deletions. This is safe as every deletion should be eventually > processed locally and for corner cases there is anyway already a GC > routine. > > This is motivated by observed ping-pongs of deletions-creations between > clients running Directory code and clients running USS code, leading > to considerably increased number of address conversions on USS. This > CL breaks these ping-pongs and should get the conversion counts on > comparable levels. > > Bug: 953693 > Change-Id: I1a30f51d4727a08f84ef33091089d2a7a366b4df > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1583896 > Commit-Queue: Jan Krcal <jkrcal@chromium.org> > Reviewed-by: Mikel Astiz <mastiz@chromium.org> > Cr-Commit-Position: refs/heads/master@{#654413} TBR=jkrcal@chromium.org,mastiz@chromium.org Change-Id: Ia8afa93aa834101d154e1a1a3db3996f686d1786 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 953693 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1583711Reviewed-by:
-
Saman Sami authored
We already do this in PixelsMatchReference() but that only applies to references that are stored in a file. Do something similar for the other variation of RunPixelTest where the reference is stored in memory. Bug: 939442 Change-Id: If71be3a9fa1d701711740dc11d341c57f56cbcfe Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1585546Reviewed-by:
-
