- 11 Dec, 2017 15 commits
-
-
Hiroki Nakagawa authored
This CL doesn't add a test because this case depends on timing and it's difficult to reproduce it artificially. Bug: 792364 Change-Id: I00f1e7fe24860e3652ee98371e40b0e798e2e0aa Reviewed-on: https://chromium-review.googlesource.com/813141 Commit-Queue: Hiroki Nakagawa <nhiroki@chromium.org> Reviewed-by:
Kinuko Yasuda <kinuko@chromium.org> Reviewed-by:
Matt Falkenhagen <falken@chromium.org> Cr-Commit-Position: refs/heads/master@{#523046}
-
Yingbing Wu authored
When first party IME is terminated unexpectedly, IME api will receive extension unload event and unregister all IMEs' components of the extension. Then the IMEs' menu on shelf will disappear. Although OS restart the first party IME extension at once, however, the IME menus can't be recovered. First party IME has more complicated initlization process other than the normal extension. Should not remove its states when it is crashed. Adds a condition in OnExtensionUnload to gurad not to unregister the first party IMEs. And records the extension id, then re-activate the extension when it reloads. Bug: 775507,788247,786273,761714 Change-Id: I08731d2da82278483b843907aacb8256e0325e88 Reviewed-on: https://chromium-review.googlesource.com/803415 Commit-Queue: Shu Chen <shuchen@chromium.org> Commit-Queue: Yingbing Wu <wuyingbing@chromium.org> Reviewed-by:
Shu Chen <shuchen@chromium.org> Reviewed-by:
Yuichiro Hanada <yhanada@chromium.org> Cr-Commit-Position: refs/heads/master@{#523045}
-
chrome-release-bot authored
TBR=govind@chromium.org Change-Id: If48ff8bce682fb21660672ca57fe5d88ddf3dfaa Reviewed-on: https://chromium-review.googlesource.com/817497Reviewed-by:
chrome-release-bot@chromium.org <chrome-release-bot@chromium.org> Cr-Commit-Position: refs/heads/master@{#523044}
-
Hajime Hoshi authored
This is part of efforts to replace base::ThreadTaskRunnerHandle::Get() with other appropriate task runners in the renderer. Bug: 786332 Change-Id: I3e7a8b88dbb85c1af56554507ec71f87e64a3d89 Reviewed-on: https://chromium-review.googlesource.com/807762Reviewed-by:
Alexander Timin <altimin@chromium.org> Reviewed-by:
Pavel Feldman <pfeldman@chromium.org> Commit-Queue: Hajime Hoshi <hajimehoshi@chromium.org> Cr-Commit-Position: refs/heads/master@{#523043}
-
Artur Khachatryan authored
This change is a speculative fix for the linux 64 buildbots due to a GPU failure. Bug: Change-Id: I09360fab81128f8109503f6d3afe67d4ecc43eaf Reviewed-on: https://chromium-review.googlesource.com/818740Reviewed-by:
John Chen <johnchen@chromium.org> Commit-Queue: John Chen <johnchen@chromium.org> Cr-Commit-Position: refs/heads/master@{#523042}
-
Sam McNally authored
Bug: 779444 Change-Id: I7bb353e31a10cd43a910de1cd4282e23309caf5e Reviewed-on: https://chromium-review.googlesource.com/788640Reviewed-by:
Peter Beverloo <peter@chromium.org> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Commit-Queue: Sam McNally <sammc@chromium.org> Cr-Commit-Position: refs/heads/master@{#523041}
-
v8-autoroll authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/14f3b83e..917ba969 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;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel TBR=hablich@chromium.org,machenbach@chromium.org,kozyatinskiy@chromium.org,sergiyb@chromium.org Change-Id: Ic05af7974cbd534be3ae5e70d4de41eac3befc5b Reviewed-on: https://chromium-review.googlesource.com/817964Reviewed-by:
v8 autoroll <v8-autoroll@chromium.org> Commit-Queue: v8 autoroll <v8-autoroll@chromium.org> Cr-Commit-Position: refs/heads/master@{#523040}
-
Peter Kotwicz authored
This CL changes the message displayed by the lightweight first run dialog from "By continuing, you agree to Chrome’s Terms of Service and Privacy Notice." to "{{app_name}} will open in Chrome. By continuing, you agree to Chrome’s Terms of Service and Privacy Notice." Currently, the lightweight FRE is only displayed for WebAPKs. The {{app_name}} is the WebAPK's short_name BUG=787939 Change-Id: Ib7359b8facc5992f0d74fea357f1c1320e3e4b6e Reviewed-on: https://chromium-review.googlesource.com/796936 Commit-Queue: Peter Kotwicz <pkotwicz@chromium.org> Reviewed-by:
Yaron Friedman <yfriedman@chromium.org> Reviewed-by:
Yusuf Ozuysal <yusufo@chromium.org> Cr-Commit-Position: refs/heads/master@{#523039}
-
Miguel Casas-Sanchez authored
TBR=marcheu@chromium.org Change-Id: Ia318d67edc7417c687aeaf8da0f6979aa47ddcff Reviewed-on: https://chromium-review.googlesource.com/818785 Commit-Queue: Miguel Casas <mcasas@chromium.org> Reviewed-by:
Miguel Casas <mcasas@chromium.org> Cr-Commit-Position: refs/heads/master@{#523038}
-
Sandra Sun authored
Use overscroll-behavior css property on viewport defining element to control overscroll action. This patch enables control over rubber-banding. Details can be found at https://wicg.github.io/overscroll-behavior/ This is implemented by recording the overscroll_behavior value at the first overscrolled GestureScrollUpdate inside InputScrollElasticityScroller, because main thread reports overscroll_behavior only when overscroll happens. For all the events in that gesture afterwards, we don't allow overscrolling if that axis has OverscrollBehaviorTypeNone. Bug: 785963 Change-Id: Ib9caae38c89e3993d3618e9b8273e3d799afccc6 Reviewed-on: https://chromium-review.googlesource.com/795450Reviewed-by:
ccameron <ccameron@chromium.org> Reviewed-by:
Charlie Reis <creis@chromium.org> Reviewed-by:
Majid Valipour <majidvp@chromium.org> Commit-Queue: Sandra Sun <sunyunjia@chromium.org> Cr-Commit-Position: refs/heads/master@{#523037}
-
Sam McNally authored
Clone() and Equals() for blink variant mojo structs containing arrays or maps do not currently compile. While custom clone and equals traits exist for WTF::Vector and WTF::HashMap, they aren't included by the appropriate headers and also don't compile. Fix compilation for the mojo::CloneTraits and mojo::EqualsTraits specializations for WTF::Vector and WTF::HashMap. Add an include of wtf_clone_equals_util.h to generated .mojom-blink.h files. Add a regression test. Change-Id: I06ecf7ccaf0207f29be34465e7a778b63767f4a4 Reviewed-on: https://chromium-review.googlesource.com/816640Reviewed-by:
Ken Rockot <rockot@chromium.org> Commit-Queue: Sam McNally <sammc@chromium.org> Cr-Commit-Position: refs/heads/master@{#523036}
-
Dominic Mazzoni authored
Adds support for AXEventGenerator in AutomationAXTreeWrapper, but to be very conservative and safe, only uses it to fire "load complete" events for now. Those events are really important and have both very broad test coverage already, and are also easy to verify in manual tests. In subsequent changes we'll switch over more and more events to come from AXEventGenerator. Bug: 699438 Change-Id: I30486c96689cc83dc24d8443b32dc4ee9069702b Reviewed-on: https://chromium-review.googlesource.com/797214 Commit-Queue: Dominic Mazzoni <dmazzoni@chromium.org> Reviewed-by:
David Tseng <dtseng@chromium.org> Cr-Commit-Position: refs/heads/master@{#523035}
-
Charles Harrison authored
Bug: None Change-Id: I824dccf02a07a56d5f26f365e562d56d6640d05c Reviewed-on: https://chromium-review.googlesource.com/816654Reviewed-by:
Bryan McQuade <bmcquade@chromium.org> Commit-Queue: Charlie Harrison <csharrison@chromium.org> Cr-Commit-Position: refs/heads/master@{#523034}
-
Sam McNally authored
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_site_isolation Change-Id: I392aa805b7d62816624cd944113c2132832dcf09 Bug: 779444 Reviewed-on: https://chromium-review.googlesource.com/706883 Commit-Queue: Sam McNally <sammc@chromium.org> Reviewed-by:
Avi Drissman <avi@chromium.org> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Cr-Commit-Position: refs/heads/master@{#523033}
-
zhuoyu.qian authored
From discussion on chromium-dev, it was decided to remove 'chrome' namespace. BUG=289619 R=pkasting@chromium.org Signed-off-by:
zhuoyu.qian <zhuoyu.qian@samsung.com> Change-Id: Ib61db08cbd4bd14886bd1cd895dbb490e3fb0086 Reviewed-on: https://chromium-review.googlesource.com/778720Reviewed-by:
Peter Kasting <pkasting@chromium.org> Cr-Commit-Position: refs/heads/master@{#523032}
-
- 10 Dec, 2017 16 commits
-
-
Kenneth Russell authored
The following changes were made: - On "Android VR Tests": - Alphabetize step names by name, when test was identical. - Add a missing "merge" script from one step. - On a few bots, remove useless swarming parameters when "can_use_on_swarming_builders" was false. - Made telemetry_unittests run serially, as on other waterfalls. - Alphabetized step names on "Site Isolation Android". With these changes, this waterfall's JSON can be autogenerated with 100% fidelity. BUG=662541 TBR=dpranke@chromium.org, bpastene@chromium.org, jbudorick@chromium.org Change-Id: I9df67955cfe1ac61338c5cfef290e7231fc6dd0f Reviewed-on: https://chromium-review.googlesource.com/818741Reviewed-by:
Kenneth Russell <kbr@chromium.org> Commit-Queue: Kenneth Russell <kbr@chromium.org> Cr-Commit-Position: refs/heads/master@{#523031}
-
Hiroshige Hayashizaki authored
Bug: 788828 Change-Id: I5874bb6e4a283a3049a94c0f66292101dfa5cec7 Reviewed-on: https://chromium-review.googlesource.com/794514 Commit-Queue: Hiroshige Hayashizaki <hiroshige@chromium.org> Reviewed-by:
Kouhei Ueno <kouhei@chromium.org> Reviewed-by:
Jeremy Roman <jbroman@chromium.org> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Cr-Commit-Position: refs/heads/master@{#523030}
-
v8-autoroll authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/f33ef156..14f3b83e 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;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel TBR=hablich@chromium.org,machenbach@chromium.org,kozyatinskiy@chromium.org,sergiyb@chromium.org Change-Id: I85d589c9243124f01f81ac01a947be2d3a7694c9 Reviewed-on: https://chromium-review.googlesource.com/817387Reviewed-by:
v8 autoroll <v8-autoroll@chromium.org> Commit-Queue: v8 autoroll <v8-autoroll@chromium.org> Cr-Commit-Position: refs/heads/master@{#523029}
-
David Tseng authored
Test: alt+shift+s, search right/left to battery status. Verify no 'labeltext' in output. Bug: Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation Change-Id: I24734e58a4835e60c26de2966e4133ce4c84b3b3 Reviewed-on: https://chromium-review.googlesource.com/815389Reviewed-by:
Dominic Mazzoni <dmazzoni@chromium.org> Commit-Queue: David Tseng <dtseng@chromium.org> Cr-Commit-Position: refs/heads/master@{#523028}
-
Alexei Svitkine authored
This way, we make the client behavior match the setup we have now, so that we can stop relying on server-side configs for UKM behavior going forward. BUG=793441 Change-Id: I14322821c69b30f8a8148d262f7e11f0c518a0f4 Reviewed-on: https://chromium-review.googlesource.com/817579Reviewed-by:
Bryan McQuade <bmcquade@chromium.org> Commit-Queue: Alexei Svitkine <asvitkine@chromium.org> Cr-Commit-Position: refs/heads/master@{#523027}
-
Reilly Grant authored
The "device:sensors" interfaces have been removed from the device service and replaced by the "device:generic_sensor" interface. Bug: 721427 Change-Id: I23164b54e09897c7bef3c6c57d37ac99b68acf06 Reviewed-on: https://chromium-review.googlesource.com/818488Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Commit-Queue: Reilly Grant <reillyg@chromium.org> Cr-Commit-Position: refs/heads/master@{#523026}
-
Dirk Pranke authored
R=kbr@chromium.org, jbudorick@chromium.org BUG=662541 Change-Id: I4c308056fcb7a411edf6d6b5e50ac29f49fdc5a8 Reviewed-on: https://chromium-review.googlesource.com/818725 Commit-Queue: Kenneth Russell <kbr@chromium.org> Reviewed-by:
Kenneth Russell <kbr@chromium.org> Cr-Commit-Position: refs/heads/master@{#523025}
-
Gaofeng Huang authored
~StreamMixer could be called before Start(). Bug: internal b/69562112 Test: on device Change-Id: I6376f6aebdc1c0f8ac8ad469e433be079b10ff98 Reviewed-on: https://chromium-review.googlesource.com/818735 Commit-Queue: Gaofeng Huang <gfhuang@chromium.org> Reviewed-by:
Kenneth MacKay <kmackay@chromium.org> Cr-Commit-Position: refs/heads/master@{#523024}
-
Jungshik Shin authored
The run-time top domain list will not have test domains any more. Bug: 791254 Test: components_unittests --gtest_filter=*IDNToUni* Change-Id: I4636438301954c97a6479726e5af70d3a0b00ac8 Reviewed-on: https://chromium-review.googlesource.com/804693 Commit-Queue: Jungshik Shin <jshin@chromium.org> Reviewed-by:
Peter Kasting <pkasting@chromium.org> Cr-Commit-Position: refs/heads/master@{#523023}
-
v8-autoroll authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/65cf9fda..f33ef156 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;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel TBR=hablich@chromium.org,machenbach@chromium.org,kozyatinskiy@chromium.org,sergiyb@chromium.org Change-Id: I8676771b7ccb60b00293de7e83ba57936c3fa9e3 Reviewed-on: https://chromium-review.googlesource.com/818748Reviewed-by:
v8 autoroll <v8-autoroll@chromium.org> Commit-Queue: v8 autoroll <v8-autoroll@chromium.org> Cr-Commit-Position: refs/heads/master@{#523022}
-
skia-deps-roller@chromium.org authored
https://skia.googlesource.com/skia.git/+log/c63ec5ca6407..c34676349da6 $ git log c63ec5ca6..c34676349 --date=short --no-merges --format='%ad %ae %s' 2017-12-10 update-skps Update SKP version Created with: roll-dep src/third_party/skia The AutoRoll server is located here: https://autoroll.skia.org 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=master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel TBR=liyuqian@chromium.org Change-Id: Iacf439dfcc3524a2662c744d47f8695f6541259e Reviewed-on: https://chromium-review.googlesource.com/818734Reviewed-by:
Skia Deps Roller <skia-deps-roller@chromium.org> Commit-Queue: Skia Deps Roller <skia-deps-roller@chromium.org> Cr-Commit-Position: refs/heads/master@{#523021}
-
Xianzhu Wang authored
Code change in RarePaintData::ContentsProperties() and PaintLayerPainter:: NeedsToClip() also fix bugs of SPv1 by the way: - crbug.com/793272 (incorrect property hierarchy about InnerBordorRadiusClip) - a bug causing the revert CL: https://chromium-review.googlesource.com/c/chromium/src/+/817372 (not landed because this CL will fix the bug). Added a test case (compositing/overflow/border-radius-above-composited-subframe.html) for the bug. Bug: 790548,793272 Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2 Change-Id: I514d9b1ae20fe7ebfe0c1712c67a9dae8b4a11d8 Reviewed-on: https://chromium-review.googlesource.com/798511 Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org> Reviewed-by:
Tien-Ren Chen <trchen@chromium.org> Cr-Commit-Position: refs/heads/master@{#523020}
-
Dominik Laskowski authored
Sub-surfaces can be positioned to the top/left of the root surface. However, the cc::RenderSurfaceImpl for a window's layer tree expects layers to be positioned in the window's local coordinate space, and clips content outside the layers' bounding box. If the host window layer has non-negative coordinates, the top/left edges of the bounding box correspond to those of the window frame, so content at negative coordinates is clipped. When the root surface is not the topmost/leftmost surface in the tree, this CL translates quads to non-negative coordinates, and translates the host window to negative coordinates. Bug: b:67384524 Test: No clipping for ARC clients using relative surface hierarchy. Change-Id: I0889387370f5fdb4e3c30849a40a6ff2b5e56c02 Reviewed-on: https://chromium-review.googlesource.com/816434 Commit-Queue: Dominik Laskowski <domlaskowski@chromium.org> Reviewed-by:
David Reveman <reveman@chromium.org> Cr-Commit-Position: refs/heads/master@{#523019}
-
chrome-release-bot authored
TBR=anantha@chromium.org Change-Id: Ib647b78cb278e1aa890174615a22dd3ed1385103 Reviewed-on: https://chromium-review.googlesource.com/817337Reviewed-by:
chrome-release-bot@chromium.org <chrome-release-bot@chromium.org> Cr-Commit-Position: refs/heads/master@{#523018}
-
Chong Zhang authored
This CL: 1.Adds reconnect logic to |StoragePartitionImpl::GetURLLoaderFactoryForBrowserProcess()| and |SystemNetworkContextManager::GetURLLoaderFactory()| to makes sure they return valid interface after crash. 2.Moved two common test APIs into "browser_test_utils.h". 3.Updated browser tests to run against restarted NetworkContext/URLLoaderFactory. Note: * More tests will be added for other NetworkContext providers (e.g. IOThread), |URLLoaderFactoryGetter|, as well as Renderer related stuff. Bug: 780956 Change-Id: I78cd400263e79f2ba2b6088e108a499ee87ae1c3 Reviewed-on: https://chromium-review.googlesource.com/769855 Commit-Queue: Chong Zhang <chongz@chromium.org> Reviewed-by:
John Abd-El-Malek <jam@chromium.org> Reviewed-by:
Matt Menke <mmenke@chromium.org> Cr-Commit-Position: refs/heads/master@{#523017}
-
John Chen authored
Disable testSendTextToAlert for Chromium on Android. It is failing and blocking ChromeDriver 2.34 release. TBR=stgao@chromium.org Bug: chromedriver:2164 Change-Id: I64705dba6547c9ec66a52a60270b131d14df0e8d Reviewed-on: https://chromium-review.googlesource.com/818728Reviewed-by:
John Chen <johnchen@chromium.org> Commit-Queue: John Chen <johnchen@chromium.org> Cr-Commit-Position: refs/heads/master@{#523016}
-
- 09 Dec, 2017 9 commits
-
-
Ryan Sturm authored
Bug: 615565 Change-Id: I6dc6e12d59ef94d50e05c772527d88e145de885b Reviewed-on: https://chromium-review.googlesource.com/792111 Commit-Queue: Ryan Sturm <ryansturm@chromium.org> Reviewed-by:
Jian Li <jianli@chromium.org> Reviewed-by:
Tarun Bansal <tbansal@chromium.org> Cr-Commit-Position: refs/heads/master@{#523015}
-
Michael Giuffrida authored
UKMs are not timestamped and are not guaranteed to arrive in the same order they were logged. This CL adds a SequenceId field to the TabMetrics event to provide a simple ordering -- the SequenceId field is just a counter that is incremented each time it is logged. Session Restore UKMs use a similar field for the same purpose. Bug: 793147 Change-Id: I06c486d44cc5e19583d3f7469c2ae68ec728cef6 Reviewed-on: https://chromium-review.googlesource.com/815539 Commit-Queue: Michael Giuffrida <michaelpg@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Reviewed-by:
Steven Holte <holte@chromium.org> Cr-Commit-Position: refs/heads/master@{#523014}
-
Nektarios Paisios authored
Fixed use-after-free bug. > Bug: 792820 R=dmazzoni@chromium.org, ananta@chromium.org Tested: using syzyASAN Change-Id: I0bc1dd2ed9f8bbe788b5ce89e7290467698a6c58 Reviewed-on: https://chromium-review.googlesource.com/818034Reviewed-by:
Dominic Mazzoni <dmazzoni@chromium.org> Reviewed-by:
Nektarios Paisios <nektar@chromium.org> Commit-Queue: Nektarios Paisios <nektar@chromium.org> Cr-Commit-Position: refs/heads/master@{#523013}
-
Klaus Weidner authored
Adds a mojo transport for GpuFenceHandle objects as an alternative to the previously implemented traditional IPC params_traits_macros support. An example use case is passing a GpuFenceHandle to a Renderer process to synchronize its command buffer GL operations with an external GL context. BUG=761432 Change-Id: I178cf670da0b0052df32f5fcaf9cac2240979deb Reviewed-on: https://chromium-review.googlesource.com/784126 Commit-Queue: Klaus Weidner <klausw@chromium.org> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Reviewed-by:
David Reveman <reveman@chromium.org> Cr-Commit-Position: refs/heads/master@{#523012}
-
v8-autoroll authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/0e3d6c55..65cf9fda 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;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel TBR=hablich@chromium.org,machenbach@chromium.org,kozyatinskiy@chromium.org,sergiyb@chromium.org Change-Id: I50149f745804105abf0afeda364b4157fe703181 Reviewed-on: https://chromium-review.googlesource.com/818705Reviewed-by:
v8 autoroll <v8-autoroll@chromium.org> Commit-Queue: v8 autoroll <v8-autoroll@chromium.org> Cr-Commit-Position: refs/heads/master@{#523011}
-
Dirk Pranke authored
R=kbr@chromium.org, jbudorick@chromium.org BUG=662541 Change-Id: I152e12b9b8d92a7fef53557b44cae22ac8b092e6 Reviewed-on: https://chromium-review.googlesource.com/818399 Commit-Queue: Dirk Pranke <dpranke@chromium.org> Reviewed-by:
Kenneth Russell <kbr@chromium.org> Cr-Commit-Position: refs/heads/master@{#523010}
-
Dirk Pranke authored
This converts the chromium.angle, chromium.webrtc, chromium.webrtc.fyi, and client.v8.branches JSON files to be generated by generate_buildbot_json.py R=kbr@chromium.org, jbudorick@chromium.org BUG=662541 Change-Id: I4c1f9f0938b6461264d979625bdd7b69cb8641e8 Reviewed-on: https://chromium-review.googlesource.com/818625 Commit-Queue: Dirk Pranke <dpranke@chromium.org> Reviewed-by:
Kenneth Russell <kbr@chromium.org> Cr-Commit-Position: refs/heads/master@{#523009}
-
Dirk Pranke authored
R=kbr@chromium.org, jbudorick@chromium.org BUG=662541 Change-Id: I7b73a552f6f3d308341cfca8a6ae5c88b8114065 Reviewed-on: https://chromium-review.googlesource.com/818473 Commit-Queue: Dirk Pranke <dpranke@chromium.org> Reviewed-by:
John Budorick <jbudorick@chromium.org> Reviewed-by:
Kenneth Russell <kbr@chromium.org> Cr-Commit-Position: refs/heads/master@{#523008}
-
Klaus Weidner authored
Split out from the GpuFence implementation due to the large size of the autogenerated mock bindings. BUG=761432 Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel Change-Id: I2cc63b360f9eee7380f0e8c4f1fd13d58c9b5b2a Reviewed-on: https://chromium-review.googlesource.com/772810 Commit-Queue: Klaus Weidner <klausw@chromium.org> Reviewed-by:
David Reveman <reveman@chromium.org> Reviewed-by:
Kenneth Russell <kbr@chromium.org> Cr-Commit-Position: refs/heads/master@{#523007}
-