- 21 May, 2018 17 commits
-
-
Koji Ishii authored
Following bot results are included. 5628 5629 5630 5638 5642 5646 5647 5648 5649 5654 5655 5656 5658 5659 116 lines were removed and 18 lines were deflaked by consecutive results since 5630. TBR=eae@chromium.org, mstensho@chromium.org NOTRY=true Bug: 591099 Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_layout_ng Change-Id: I8566e77b2ceeb0db44e704ca127263f3967b699a Reviewed-on: https://chromium-review.googlesource.com/1065476 Commit-Queue: Koji Ishii <kojii@chromium.org> Reviewed-by:
Koji Ishii <kojii@chromium.org> Cr-Commit-Position: refs/heads/master@{#560226}
-
fuchsia-sdk-chromium-autoroll authored
The AutoRoll server is located here: https://fuchsia-sdk-chromium-roll.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=luci.chromium.try:fuchsia_arm64_cast_audio;luci.chromium.try:fuchsia_x64_cast_audio TBR=cr-fuchsia+bot@chromium.org Change-Id: Iffd88ce923f335ee3b3b9979be0a252f9ef240e2 Reviewed-on: https://chromium-review.googlesource.com/1067237Reviewed-by:
Fuchsia SDK Autoroller <fuchsia-sdk-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: Fuchsia SDK Autoroller <fuchsia-sdk-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#560225}
-
Kent Tamura authored
The new behavior matches to name_utilities.py. This CL has no behavior changes because the current users of name_style_converter never pass names with such characters. Bug: 843927 Change-Id: I8eeafb71ec85bb1a0f92eff317fb07eb2dc373ff Reviewed-on: https://chromium-review.googlesource.com/1065959 Commit-Queue: Kent Tamura <tkent@chromium.org> Reviewed-by:
Hitoshi Yoshida <peria@chromium.org> Cr-Commit-Position: refs/heads/master@{#560224}
-
calamity authored
This reverts commit ffd43add. Reason for revert: Suspected of causing https://ci.chromium.org/buildbot/chromium.memory/Linux%20CFI/7978 Original change's description: > Make TouchActionFilter::allowed_touch_action_ optional > > The allowed_touch_action_ bit is set to Auto by default when a touch > action filter is constructed. If we'd want to make a gesture that is > hitting a main thread touch action region non blocking, we need to > make this bit optional and set/reset at the right time. > > In this CL, allowed_touch_action_ is set at touch start, and reset > at GestureScrollEnd, and we also handle the scroll bubbling cases. > > The intention of this CL is to NOT cause any behavior change, which > can be verified by existing tests. > > Bug: 772130 > Change-Id: I6d37fc4d1b99bddc334f28dc342c9b095a5f30c6 > Reviewed-on: https://chromium-review.googlesource.com/1042351 > Commit-Queue: Xida Chen <xidachen@chromium.org> > Reviewed-by: Antoine Labour <piman@chromium.org> > Reviewed-by: Robert Flack <flackr@chromium.org> > Reviewed-by: Philip Rogers <pdr@chromium.org> > Reviewed-by: Dave Tapuska <dtapuska@chromium.org> > Reviewed-by: Navid Zolghadr <nzolghadr@chromium.org> > Cr-Commit-Position: refs/heads/master@{#560146} TBR=flackr@chromium.org,pdr@chromium.org,dtapuska@chromium.org,piman@chromium.org,xidachen@chromium.org,nzolghadr@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 772130 Change-Id: I866b91f13116a085f9956604f16324e373da540b Reviewed-on: https://chromium-review.googlesource.com/1067217Reviewed-by:
calamity <calamity@chromium.org> Commit-Queue: calamity <calamity@chromium.org> Cr-Commit-Position: refs/heads/master@{#560223}
-
Alice Boxhall authored
ARIAProperties.json5 represents the certain rules captured in the ARIA spec. This change also uses it to generate the list of ARIA attribute name constants, and to generate the ARIA autocompletion configuration for devtools. Also adds pyjson5 as a third_party library. Change-Id: I622e590196be667ed97288a73d040856380f3bf9 Reviewed-on: https://chromium-review.googlesource.com/737397 Commit-Queue: Alice Boxhall <aboxhall@chromium.org> Reviewed-by:
Nico Weber <thakis@chromium.org> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Reviewed-by:
Dirk Pranke <dpranke@chromium.org> Reviewed-by:
Dominic Mazzoni <dmazzoni@chromium.org> Reviewed-by:
Joel Einbinder <einbinder@chromium.org> Cr-Commit-Position: refs/heads/master@{#560222}
-
Hayato Ito authored
In Document::UpdateStyleAndLayoutTree(), recalc slot assignments should be done before checking NeedsLayoutTreeUpdate() to detect the need of layout tree update surely. Without that, there is an edge case which causes a crash. Bug: 776656,844301 Change-Id: I1ef7719216649019e07f2799ecd4f1fcb3d961a6 Reviewed-on: https://chromium-review.googlesource.com/1066030 Commit-Queue: Hayato Ito <hayato@chromium.org> Reviewed-by:
Takayoshi Kochi <kochi@chromium.org> Reviewed-by:
Rakina Zata Amni <rakina@chromium.org> Cr-Commit-Position: refs/heads/master@{#560221}
-
Mitsuru Oshima authored
BUG=844325 TEST=covered by unittest Change-Id: I85ba6c727c13e204a0db27f341e3af4ce189b2df Reviewed-on: https://chromium-review.googlesource.com/1065693Reviewed-by:
Ben Wells <benwells@chromium.org> Commit-Queue: Mitsuru Oshima <oshima@chromium.org> Cr-Commit-Position: refs/heads/master@{#560220}
-
Siddhartha authored
The renderer OOM metrics are stored in shared memory buffer so that the browser can read the metrics after renderer crashes (by OOM). BUG=843419 Change-Id: I498256e473785051724efa80864f0292cc24362e Reviewed-on: https://chromium-review.googlesource.com/1062211 Commit-Queue: Siddhartha S <ssid@chromium.org> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Reviewed-by:
-
James Darpinian authored
This reverts commit bdc9b10b. Originally reviewed at: https://chromium-review.googlesource.com/c/chromium/src/+/1062585 Suspected of breaking WebGL conformance tests on FYI waterfall: https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Win7%20FYI%20Release%20(AMD)/1241 https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Win7%20FYI%20Release%20(NVIDIA)/1013 https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Win7%20FYI%20x64%20Release%20(NVIDIA)/1071 https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Mac%20FYI%20Release%20(Intel)/3022 https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Mac%20FYI%20Experimental%20Retina%20Release%20(AMD)/1728 Bug: 844897,843290 No-Try: true Tbr: fsamuel@chromium.org Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel Change-Id: I7994694e057a08f2a27d4aedcfa369fd350f32b2 Reviewed-on: https://chromium-review.googlesource.com/1067142 Commit-Queue: Jamie Madill <jmadill@chromium.org> Reviewed-by:
Jamie Madill <jmadill@chromium.org> Cr-Commit-Position: refs/heads/master@{#560218}
-
Peter Kotwicz authored
This CL fixes the URL formatting in ShortcutHelper#getScopeFromUrl(). Previously getScopeFromUrl() was decoding then re-encoding the path, which does not round-trip correctly as it encodes characters like '='. This bug was causing the WebAPK to think that the start URL was outside of the scope generated by ShortcutHelper#getScopeFromUrl() and to launch a CCT BUG=840271 TEST=ShortcutHelperTest Change-Id: Ibf63a8b13717c33ce6e8f113d58192a964e53d2d Reviewed-on: https://chromium-review.googlesource.com/1053491 Commit-Queue: Peter Kotwicz <pkotwicz@chromium.org> Reviewed-by:
Bernhard Bauer <bauerb@chromium.org> Reviewed-by:
Matt Giuca <mgiuca@chromium.org> Cr-Commit-Position: refs/heads/master@{#560217}
-
csharrison authored
Bug: 689702 Change-Id: I2d42bdc23d384462955a70f53c6462298df30658 Reviewed-on: https://chromium-review.googlesource.com/1067102Reviewed-by:
Kouhei Ueno <kouhei@chromium.org> Commit-Queue: Charlie Harrison <csharrison@chromium.org> Cr-Commit-Position: refs/heads/master@{#560216}
-
csharrison authored
Bug: 689702 Change-Id: I3d536827dc572de1cc315226aefbded5b53aee03 Reviewed-on: https://chromium-review.googlesource.com/1066894Reviewed-by:
-
Kent Tamura authored
tokenize_name() didn't recognize a sequence of lowercase letters as a token, and MATCHING_EXPRESSION didn't contain SPECIAL_TOKENS. So, 'isHTMLDocument' was split to 'isHTML' and 'Document'. In order to avoid such issues, - MATCHING_EXPRESSION should contain SPECIAL_TOKENS - It should also capture lowercase-only tokens, uppercase-only tokens, and digits-only tokens. MATCHING_EXPRESSION is renamed to _TOKEN_RE, and it's now a compiled regular expression. This is a preparation to marge name_style_converter and name_utilities. Bug: 843927 Change-Id: I0630c7dae4a0e01013ce6dc6948f663d04c47d0c Reviewed-on: https://chromium-review.googlesource.com/1065830Reviewed-by:
-
Pawel Osciak authored
An AcceleratedVideoEncoder (AVE) is a video encoder that performs high-level, platform-independent encoding process steps, such as managing codec state, reference frames, etc., but requires support from an external Accelerator (typically a hardware accelerator) to offload the actual image encoding process, using the parameters that AVE prepares beforehand. Clients of AVEs are expected to provide an Accelerator class instance appropriate for current platform and/or scenario. Each video codec-specific AVE specifies its own Accelerator interface (e.g. a H264Encoder AVE defines an H264-specific Accelerator). This CL adds the AVE API, a platform-independent implementation of AVE for H264 - H264Encoder, as well as a VA-API implementation of H264Encoder::Accelerator to provide an accelerator for it. BUG=703988,794608 TEST=veaunittest,apprtc,vdaunittest Cq-Include-Trybots: luci.chromium.try:linux_optional_gpu_tests_rel;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 Change-Id: Iaf50f3a83df4ed51c81bb8a4c0e1152af82515e1 Reviewed-on: https://chromium-review.googlesource.com/918701 Commit-Queue: Pawel Osciak <posciak@chromium.org> Reviewed-by:
Xiaohan Wang <xhwang@chromium.org> Reviewed-by:
Miguel Casas <mcasas@chromium.org> Reviewed-by:
Kuang-che Wu <kcwu@chromium.org> Cr-Commit-Position: refs/heads/master@{#560213}
-
Tetsui Ohkubo authored
UnifiedSystemTray class will replace old SystemTray class. Therefore, we have to remove all the references that rely on old SystemTray implementation. UnifiedSystemTray does not have help button (it will be replaced by one in app launcher), so we remove HelpStep from first run tutorial. Screenshot: http://screen/ZcfkBjBZT0x Design doc: http://go/cros-qs-restyling TEST=manual BUG=837508,837502 Change-Id: I90b8eff7095b9e49cddd31398349b3c5db8728df Reviewed-on: https://chromium-review.googlesource.com/1063529Reviewed-by:
James Cook <jamescook@chromium.org> Commit-Queue: Tetsui Ohkubo <tetsui@chromium.org> Cr-Commit-Position: refs/heads/master@{#560212}
-
Tetsui Ohkubo authored
UnifiedSystemTray class will replace old SystemTray class. Therefore, we have to remove all the references that rely on old SystemTray implementation. Design doc: http://go/cros-qs-restyling TEST=manual BUG=837508 Change-Id: I0ad59343da6b23e400293352ce83355a21d14c07 Reviewed-on: https://chromium-review.googlesource.com/1063528Reviewed-by:
Ahmed Fakhry <afakhry@chromium.org> Commit-Queue: Tetsui Ohkubo <tetsui@chromium.org> Cr-Commit-Position: refs/heads/master@{#560211}
-
skia-chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/5191880cbf3e..32a4910e57b1 $ git log 5191880cb..32a4910e5 --date=short --no-merges --format='%ad %ae %s' 2018-05-20 caryclark Revert "remove toString" Created with: roll-dep src/third_party/skia BUG=chromium:830651 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;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 TBR=allanmac@chromium.org Change-Id: I20bc5ec8ec3c5637612f644bbc33d08cd848511e Reviewed-on: https://chromium-review.googlesource.com/1067004Reviewed-by:
skia-chromium-autoroll <skia-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: skia-chromium-autoroll <skia-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#560210}
-
- 20 May, 2018 23 commits
-
-
Paul Miller authored
This follows the advice of go/power-analysis (internal document). The download frequency is capped at 1/day anyway, so this shouldn't have much effect on seed freshness. BUG=733857 Change-Id: Ifceecf6877542af317ea08128af9bdeb5c6fb991 Reviewed-on: https://chromium-review.googlesource.com/1066801Reviewed-by:
Changwan Ryu <changwan@chromium.org> Commit-Queue: Paul Miller <paulmiller@chromium.org> Cr-Commit-Position: refs/heads/master@{#560209}
-
Morten Stenshorne authored
When there are adjoining floats that need to be separated from a cleared block, clearance is predetermined, and we have to force it on the block. Any large top margin on the child will just be eaten by negative clearance. There's nothing that can be done to prevent clearance in such cases. So make sure that we don't try to determine whether to apply clearance or not based on the clearance offset set in the constraint space. When clearance has been predetermined (which may have triggered a BFC offset resolution and what not), refusing to apply it to the child is a bug. This aligns the implementation with the "alternative" way of calculating clearance in the spec [1]. Everyone but Edge does this. I think what Edge does here is problematic, because it requires us to use a hypothetical position that was calculated before clearance got applied (clearance causes margins that would otherwise collapse to be separated). We'd end up using a hypothetical position not based on the actual layout situation.[2] [1] https://www.w3.org/TR/CSS22/visuren.html#flow-control [2] https://github.com/w3c/csswg-drafts/issues/2608 This fixes one existing test. Added a few new ones as well. Not all of them failed prior to this CL, but they serve as regression tests for things I found to lack coverage while working on this. Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_layout_ng Change-Id: Ia45e9048c75c338477eee4923ff16eea3245bc6a Reviewed-on: https://chromium-review.googlesource.com/1061470 Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Reviewed-by:
Ian Kilpatrick <ikilpatrick@chromium.org> Cr-Commit-Position: refs/heads/master@{#560208}
-
Darren Shen authored
Fixes an issue where CSSNumericValue.parse considers valid strings surrounded by whitespace to be invalid. Bug: 844290 Change-Id: I4c40044631276a611ef9a56aac21ddf09316a550 Reviewed-on: https://chromium-review.googlesource.com/1065532Reviewed-by:
Rune Lillesveen <futhark@chromium.org> Commit-Queue: Darren Shen <shend@chromium.org> Cr-Commit-Position: refs/heads/master@{#560207}
-
Ken Rockot authored
Re-reland of r555117 with process handle leak actually fixed. Totes for reals. Original commit message follows. Mojo passes around base::ProcessHandle values for various reasons. On most systems this is fine, but at least on Windows, a ProcessHandle refers to an owned reference to a system process object, and if not careful it's possible for a base::ProcessHandle value to inadvertently change meaning over time. This CL introduces the concept of a move-only ScopedProcessHandle within Mojo, which on most platforms is just a base::PlatformHandle. On Windows, this represents an owned base::ProcessHandle which closes on destruction and clones correctly using DuplicateHandle rather than merely copying the raw handle value. ScopedProcessHandle is used in a few places where process handle ownership semantics were previously weaker than necessary, or were correct but implemented ad hoc. This also updates ScopedPlatformHandle (and supporting code like Channel::RewriteHandles) such that the |owning_process| field (if not the current process) is always an owned process handle. This ensures that when such handles are closed in unsent messages, they can be safely closed in the target process (from within the source process) without any risk of raciness against target process termination. TBR=jcivelli@chromium.org Bug: 837612 Change-Id: I182e6849fd87fb44e22f6ed21457b17422956613 Reviewed-on: https://chromium-review.googlesource.com/1066999 Commit-Queue: Ken Rockot <rockot@chromium.org> Reviewed-by:
Ken Rockot <rockot@chromium.org> Cr-Commit-Position: refs/heads/master@{#560206}
-
skia-chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/da17f1e7df1d..5191880cbf3e $ git log da17f1e7d..5191880cb --date=short --no-merges --format='%ad %ae %s' 2018-05-18 caryclark remove toString 2018-05-18 brianosman Add drawBitmapLattice to SkDebugCanvas Created with: roll-dep src/third_party/skia BUG=chromium:830651 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;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 TBR=allanmac@chromium.org Change-Id: Ic416a02f00901a15956ee78e8f87dd9ee6d8e3cf Reviewed-on: https://chromium-review.googlesource.com/1067001 Commit-Queue: skia-chromium-autoroll <skia-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Reviewed-by:
-
Rohit Rao authored
When the UIRefresh UI is enabled, bookmarks is presented using a UIPresentationController with a custom presentation. UIAlertController chooses to draw as a popover in Regular horizontal size classes, so we need to provide a sourceView and sourceRect. For now, provide the center of the bottom UIToolbar, as that roughly corresponds to the "More" button. BUG=None Cq-Include-Trybots: luci.chromium.try:ios-simulator-full-configs;master.tryserver.chromium.mac:ios-simulator-cronet Change-Id: I6e732460eb371158ac9e1754d752b923965f5b0b Reviewed-on: https://chromium-review.googlesource.com/1064916Reviewed-by:
Sergio Collazos <sczs@chromium.org> Commit-Queue: Rohit Rao <rohitrao@chromium.org> Cr-Commit-Position: refs/heads/master@{#560204}
-
Takuto Ikuta authored
Stop to use explicit dependency for indirect dependency in the CL broke Mac builder. https://chromium-review.googlesource.com/1041506 This CL uses deps/public_deps in create_bundle target always not to miss the dependency. Bug: 843470 Change-Id: Iae66f2a3aec20f67ea2e880bb5fd33d6c2aa2f91 Reviewed-on: https://chromium-review.googlesource.com/1065591Reviewed-by:
Sylvain Defresne <sdefresne@chromium.org> Reviewed-by:
-
Jialiu Lin authored
1. Skip client side detection if page url matches enterprise whitelist 2. Trigger |OnSecurityInterstitialShown| and |OnSecurityInterstitialProceeded| extension events on SB and SSL interstitial. Bug: 811467, 811454 Change-Id: Ia361763f3102914f8be3896068809ccd599319aa Reviewed-on: https://chromium-review.googlesource.com/1056066 Commit-Queue: Jialiu Lin <jialiul@chromium.org> Reviewed-by:
Emily Stark <estark@chromium.org> Reviewed-by:
Varun Khaneja <vakh@chromium.org> Reviewed-by:
Luke Z <lpz@chromium.org> Cr-Commit-Position: refs/heads/master@{#560202}
-
skia-chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/04d6ced50cd8..da17f1e7df1d $ git log 04d6ced50..da17f1e7d --date=short --no-merges --format='%ad %ae %s' 2018-05-20 rmistry Omit "espn" from key_mobile_sites_smooth in RecreateSKPs bot 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;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 TBR=allanmac@chromium.org Change-Id: I91b10ca53e88ef86823b954562182b7c31dfedca Reviewed-on: https://chromium-review.googlesource.com/1067145 Commit-Queue: skia-chromium-autoroll <skia-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Reviewed-by:
-
Nico Weber authored
TBR=scottmg Bug: 845011 Change-Id: I06891b947b6eb444ab8a6af7b2f9a574e04d40f0 Reviewed-on: https://chromium-review.googlesource.com/1067151Reviewed-by:
-
Robert Sesek authored
This should force LaunchServices`clientIsAllowedToConnect() to always return false. Bug: 844660 Change-Id: Ib6e57b3d567da7efd2590858dff1e19f5e82c5db Reviewed-on: https://chromium-review.googlesource.com/1066482Reviewed-by:
Greg Kerr <kerrnel@chromium.org> Reviewed-by:
Avi Drissman <avi@chromium.org> Commit-Queue: Robert Sesek <rsesek@chromium.org> Cr-Commit-Position: refs/heads/master@{#560199}
-
Ria Jiang authored
Record the number of clients we asked when doing async targeting. 0 means we didn't take async path at all; 1 means we found the target when asking the first client; 2 means we found the target when asking the second client; ... This should give us a better idea of how many clients we usually ask in async path so we can try to optimize and reduce latency in async path. Note that we only report this UMA if Site Isolation is turned on and we actually did explicit hit-testing for that event. Bug: 732417 Change-Id: I164a9f8c853181c4ab6896a5bfcf9c0806a3da7d Reviewed-on: https://chromium-review.googlesource.com/1060286Reviewed-by:
Robert Kaplow <rkaplow@chromium.org> Reviewed-by:
Sadrul Chowdhury <sadrul@chromium.org> Reviewed-by:
Ken Buchanan <kenrb@chromium.org> Commit-Queue: Ria Jiang <riajiang@chromium.org> Cr-Commit-Position: refs/heads/master@{#560198}
-
chromeos-commit-bot@chromium.org authored
BUG=762641 TBR=satorux@chromium.org Change-Id: I2e0380a22ffdbfd29f3db231b7b7adcdfb342804 Reviewed-on: https://chromium-review.googlesource.com/1067126Reviewed-by:
ChromeOS Commit Bot <chromeos-commit-bot@chromium.org> Commit-Queue: ChromeOS Commit Bot <chromeos-commit-bot@chromium.org> Cr-Commit-Position: refs/heads/master@{#560197}
-
v8-autoroll authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/b292e56e..41a6376d 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,machenbach@chromium.org,kozyatinskiy@chromium.org,sergiyb@chromium.org Change-Id: Iab746e59dc5d09c20ec415a6cf2a34ec61c22bda Reviewed-on: https://chromium-review.googlesource.com/1067098Reviewed-by:
v8 autoroll <v8-autoroll@chromium.org> Commit-Queue: v8 autoroll <v8-autoroll@chromium.org> Cr-Commit-Position: refs/heads/master@{#560196}
-
afdo-chromium-autoroll authored
This CL may cause a small binary size increase, roughly proportional to how long it's been since our last AFDO profile roll. For larger increases (around or exceeding 100KB), please file a bug against gbiv@chromium.org. Additional context: https://crbug.com/805539 The AutoRoll server is located here: https://afdo-chromium-roll.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. TBR=gbiv@chromium.org Change-Id: Iaf53bf154f0704151e8d5d2ce25ab1c3448f4b81 Reviewed-on: https://chromium-review.googlesource.com/1067143Reviewed-by:
afdo-chromium-autoroll <afdo-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: afdo-chromium-autoroll <afdo-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#560195}
-
David Grogan authored
ShrinkToAvoidFloats does this already. Possible artifact from a previous draft patchset of https://chromium-review.googlesource.com/c/chromium/src/+/888059 ? Change-Id: Ica9ec0d92403e8d90370ab4758b5504fa8a124f6 Reviewed-on: https://chromium-review.googlesource.com/1066853Reviewed-by:
Morten Stenshorne <mstensho@chromium.org> Commit-Queue: David Grogan <dgrogan@chromium.org> Cr-Commit-Position: refs/heads/master@{#560194}
-
John Budorick authored
Bug: 731985,790706 Change-Id: I3a0e3de9e5fbc883e6a42035b4aa9cf10f9e6814 Reviewed-on: https://chromium-review.googlesource.com/1066180 Commit-Queue: John Budorick <jbudorick@chromium.org> Reviewed-by:
Ben Pastene <bpastene@chromium.org> Cr-Commit-Position: refs/heads/master@{#560193}
-
Pavel Feldman authored
Change-Id: I9bb1a1aadc3f50f8b6e9bed38ae7eb0834e3c66a TBR: dgozman Reviewed-on: https://chromium-review.googlesource.com/1066992Reviewed-by:
Pavel Feldman <pfeldman@chromium.org> Cr-Commit-Position: refs/heads/master@{#560192}
-
chrome-release-bot authored
# This is an automated release commit. # Do not revert without consulting chrome-pmo@google.com. NOAUTOREVERT=true TBR=govind@chromium.org Change-Id: If33411a07b66d701f7ee84d22cd0af5526d31807 Reviewed-on: https://chromium-review.googlesource.com/1067094Reviewed-by:
chrome-release-bot@chromium.org <chrome-release-bot@chromium.org> Cr-Commit-Position: refs/heads/master@{#560191}
-
Pavel Feldman authored
Change-Id: Idbc930f4087158b413bd447698098792ec1b9b04 TBR: dgozman Reviewed-on: https://chromium-review.googlesource.com/1067133 Commit-Queue: Pavel Feldman <pfeldman@chromium.org> Reviewed-by:
-
fuchsia-sdk-chromium-autoroll authored
The AutoRoll server is located here: https://fuchsia-sdk-chromium-roll.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=luci.chromium.try:fuchsia_arm64_cast_audio;luci.chromium.try:fuchsia_x64_cast_audio TBR=cr-fuchsia+bot@chromium.org Change-Id: Idaa308c8de43f9bd0b9d6aaa3a6d31cecad4233b Reviewed-on: https://chromium-review.googlesource.com/1067136 Commit-Queue: Fuchsia SDK Autoroller <fuchsia-sdk-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Reviewed-by:
-
https://chromium.googlesource.com/angle/angle.git/+log/9b1a90845291..42cf958ce8fa $ git log 9b1a90845..42cf958ce --date=short --no-merges --format='%ad %ae %s' 2018-05-17 jmadill Make UNIMPLEMENTED a warning. 2018-05-17 jmadill dEQP: Use overload of CreateWindow. Created with: roll-dep src/third_party/angle The AutoRoll server is located here: https://angle-chromium-roll.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=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 TBR=ynovikov@chromium.org Change-Id: I8615be45d9fed12790e35d0154df6f6d2fb326d0 Reviewed-on: https://chromium-review.googlesource.com/1067130Reviewed-by:
angle-chromium-autoroll <angle-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: angle-chromium-autoroll <angle-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#560188}
-
skia-chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/da816f070842..04d6ced50cd8 $ git log da816f070..04d6ced50 --date=short --no-merges --format='%ad %ae %s' 2018-05-19 angle-skia-autoroll Roll third_party/externals/angle2/ 78b7f3a8e..42cf958ce (3 commits) 2018-05-19 angle-skia-autoroll Roll third_party/externals/angle2/ a9ab0f37c..78b7f3a8e (1 commit) 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;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 TBR=herb@chromium.org Change-Id: I017293cbc3122ee0c068c9869e5e9423b4cdab13 Reviewed-on: https://chromium-review.googlesource.com/1067086Reviewed-by:
-
