- 22 Nov, 2018 40 commits
-
-
Shao-Chuan Lee authored
Bug: 904282 Change-Id: I5dfaed91060891069f317cf9eb3140f58c4d5c2f Reviewed-on: https://chromium-review.googlesource.com/c/1331095 Commit-Queue: Shao-Chuan Lee <shaochuan@chromium.org> Reviewed-by:
Jesse Doherty <jwd@chromium.org> Reviewed-by:
Dominic Battré <battre@chromium.org> Reviewed-by:
Hidehiko Abe <hidehiko@chromium.org> Reviewed-by:
Maajid <maajid@chromium.org> Reviewed-by:
Kinuko Yasuda <kinuko@chromium.org> Cr-Commit-Position: refs/heads/master@{#610332}
-
Hans Wennborg authored
The classes may not actually be copyable, copy-assignable, etc. Previously the compiler would not complain until trying to *use* the defaulted ctor/operator, but the new -Wdefaulted-function-deleted warning warns about this up front. (As a concrete example, ExtensionMsg_TabConnectionInfo isn't copy-assignable because of base::DictionaryValue member, which is a base::Value, which can't be copied.) To ensure these structs are still movable, remove the user-declared destructor. This is also a simplification in that it removes all the code that was necessary to define that destructor out-of-line. Bug: 890307 Change-Id: I27ec3a0639bdeb94776acdd78b173791d0b8162d Reviewed-on: https://chromium-review.googlesource.com/c/1261082Reviewed-by:
John Abd-El-Malek <jam@chromium.org> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Reviewed-by:
Daniele Castagna <dcastagna@chromium.org> Reviewed-by:
Ken Rockot <rockot@google.com> Reviewed-by:
Antoine Labour <piman@chromium.org> Reviewed-by:
Nico Weber <thakis@chromium.org> Commit-Queue: Hans Wennborg <hans@chromium.org> Cr-Commit-Position: refs/heads/master@{#610331}
-
rbpotter authored
Error messages currently appear cut off for large fonts and languages that cause the messages to wrap onto more than 2 lines. Size error messages to the full height of the text content and update styling so that the labels stay aligned with the input when error messages appear. Bug: 898802, 887992 Change-Id: I07036adc127cd9fa95ddede51c44790c867e31ba Reviewed-on: https://chromium-review.googlesource.com/c/1345544Reviewed-by:
Demetrios Papadopoulos <dpapad@chromium.org> Commit-Queue: Rebekah Potter <rbpotter@chromium.org> Cr-Commit-Position: refs/heads/master@{#610330}
-
Zhenyao Mo authored
Currently we initialize it too soon, so on multi-GPU system, the workaround |disable_direct_composition| may not be correctly applied. BUG=907684 TEST=manual R=piman@chromium.org,sunnyps@chromium.org Change-Id: Id30e09f2229b4229b82ee9330523426b470b7c5d Reviewed-on: https://chromium-review.googlesource.com/c/1346998 Commit-Queue: Zhenyao Mo <zmo@chromium.org> Reviewed-by:
-
Alex Danilo authored
Selecting a file, then tabbing to the selection menu button should hide the tooltip if the menu is activated from the keyboard. This change explicitly hides the tooltip on menu activation. behaviour is correct on desktop and real device. Bug: 752035 Test: Ran all FilesApp browser tests. Manually verified Change-Id: I8c13364748773da2521129e95d7edb29c4032edd Reviewed-on: https://chromium-review.googlesource.com/c/1347958Reviewed-by:Joel Hockey <joelhockey@chromium.org> Commit-Queue: Alex Danilo <adanilo@chromium.org> Cr-Commit-Position: refs/heads/master@{#610328}
-
Dale Curtis authored
We should be able to avoid this with careful use of a trampoline through the media thread after PipelineImpl::Stop() completes. BUG=905506 TEST=passes cq. Change-Id: I6a9c1a0e578c48a66af85588879346d26009d2ab Reviewed-on: https://chromium-review.googlesource.com/c/1336659Reviewed-by:
Fredrik Hubinette <hubbe@chromium.org> Reviewed-by:
Dan Sanders <sandersd@chromium.org> Commit-Queue: Dale Curtis <dalecurtis@chromium.org> Cr-Commit-Position: refs/heads/master@{#610327}
-
Joel Hockey authored
* Added quickview integration test pressEnterOnInfoBoxToOpenClose. * Updated test.util.sync.deepQueryAllElements to accept targetQuery as either string or !Array<string>. * Changed RemoteCall waitForElement* functions to call deepQueryAllElements to allow for usage with nested elements. * Updated javadoc on RemoteCall functions to show which already support query as string|!Array<string>. Bug: 893093 Change-Id: I7c542e7a2bc914e16fa8142fb696f5b3fe370752 Reviewed-on: https://chromium-review.googlesource.com/c/1345693Reviewed-by:
Luciano Pacheco <lucmult@chromium.org> Commit-Queue: Joel Hockey <joelhockey@chromium.org> Cr-Commit-Position: refs/heads/master@{#610326}
-
Jinsuk Kim authored
Initial implementation of ephemeral tab based on overlay panel. See go/ephemeral for the design. Final design may be subject to change. and there are many TODO's still left. non-trivial amount of time trying to reduce its number of methods. Bug: 894619 Change-Id: I2833c6aaf820d9cf40be4d465ef135f5d5f8a9f6 Binary-Size: Increase needed to implement a feature, and I've already spent a Reviewed-on: https://chromium-review.googlesource.com/c/1282043 Commit-Queue: Jinsuk Kim <jinsukkim@chromium.org> Reviewed-by:Ted Choc <tedchoc@chromium.org> Reviewed-by:
Matthew Jones <mdjones@chromium.org> Reviewed-by:
Donn Denman <donnd@chromium.org> Cr-Commit-Position: refs/heads/master@{#610325}
-
Joel Hockey authored
Remove the 'toolbar-menu' class when menu closing animation is complete to avoid flicker. Bug: 862926 Change-Id: I8b52b86297a5f629d00b8cf43bce3c537a6ef323 Reviewed-on: https://chromium-review.googlesource.com/c/1347957Reviewed-by:
Stuart Langley <slangley@chromium.org> Commit-Queue: Joel Hockey <joelhockey@chromium.org> Cr-Commit-Position: refs/heads/master@{#610324}
-
Matt Giuca authored
Instead of two separate code paths for when the Desktop PWAs flag is enabled/disabled, it's now a single code path that makes a few behavioural changes depending on the status of that flag. Bug: 907298 Change-Id: I6b449fd65390d631098b2bc58e6c1ea668d5fd41 Reviewed-on: https://chromium-review.googlesource.com/c/1345753Reviewed-by:
Avi Drissman <avi@chromium.org> Commit-Queue: Matt Giuca <mgiuca@chromium.org> Cr-Commit-Position: refs/heads/master@{#610323}
-
Rakina Zata Amni authored
We previously used ComputedStyle::Create when creating ComputedStyle for invisible elements, but the ComputedStyle made with that lacks some setup needed for it to actually be usable correctly. Example case is the style's font fallback list is not set, leading to some crashes. Bug: 904791 Change-Id: I512082af6dcf7a5076eb033a2f9a78b83020e47e Reviewed-on: https://chromium-review.googlesource.com/c/1345952 Commit-Queue: Rakina Zata Amni <rakina@chromium.org> Reviewed-by:
Rune Lillesveen <futhark@chromium.org> Cr-Commit-Position: refs/heads/master@{#610322}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/d66dad7fc2c3..25c4fce2cebb git log d66dad7fc2c3..25c4fce2cebb --date=short --no-merges --format='%ad %ae %s' 2018-11-22 recipe-roller@chromium.org Roll recipe dependencies (trivial). 2018-11-21 recipe-roller@chromium.org Roll recipe dependencies (trivial). Created with: gclient setdep -r src/third_party/depot_tools@25c4fce2cebb 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. TBR=agable@chromium.org Change-Id: I9b719f59b87f305ed9cc5cdf422e9f0b3e811e72 Reviewed-on: https://chromium-review.googlesource.com/c/1347911Reviewed-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@{#610321}
-
Mike Frysinger authored
This makes `grit build --help` work too. Bug: 747171 Change-Id: I5297019a34446196e625635318f2373620ffd87f Reviewed-on: https://chromium-review.googlesource.com/c/1339341 Commit-Queue: Mike Frysinger <vapier@chromium.org> Reviewed-by:
-
Xi Cheng authored
Change-Id: Ia542a4fdc9ee86b06b23a20a8d01ea0ae562224f Reviewed-on: https://chromium-review.googlesource.com/c/1347041Reviewed-by:
Mike Wittman <wittman@chromium.org> Commit-Queue: Xi Cheng <chengx@chromium.org> Cr-Commit-Position: refs/heads/master@{#610319}
-
Kunihiko Sakamoto authored
This updates the expectation for css/css-font-loading/idlharness.https.html and removes the Failure expectation from TestExpectation file. The expected.txt file contains some FAIL lines because - variationSettings attribute does not exist in FontFace (crbug.com/907723) - FontFaceSet constructor is not exposed (crbug.com/651795) Bug: 824955,907723,651795 Change-Id: I527badfeea8d21ac16a9bfd20d1f0f255ff553ce Reviewed-on: https://chromium-review.googlesource.com/c/1347951 Commit-Queue: Kunihiko Sakamoto <ksakamoto@chromium.org> Reviewed-by:
Takashi Toyoshima <toyoshim@chromium.org> Cr-Commit-Position: refs/heads/master@{#610318}
-
Stuart Langley authored
This CL removes the last remaining traces of GA from files app. It does not replace the remaining metrics that were being recorded with UMAs, we're removing them as well as either: a) There's coverage via an existing UMA, or b) We don't care to record that metric anymore. Bug: 847729 Change-Id: I602de642bac43df64f1ecd9035314d5019268aa8 Reviewed-on: https://chromium-review.googlesource.com/c/1347648Reviewed-by:
Naoki Fukino <fukino@chromium.org> Commit-Queue: Stuart Langley <slangley@chromium.org> Cr-Commit-Position: refs/heads/master@{#610317}
-
chromium-autoroll authored
https://chromium.googlesource.com/catapult.git/+log/aa21a922d4a8..4176781039b6 git log aa21a922d4a8..4176781039b6 --date=short --no-merges --format='%ad %ae %s' 2018-11-21 lwsong@google.com Added new pipeline metrics Created with: gclient setdep -r src/third_party/catapult@4176781039b6 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 TBR=sullivan@chromium.org Change-Id: I0efadf017d22d539a2cb05eddf798cebf43a0589 Reviewed-on: https://chromium-review.googlesource.com/c/1347079Reviewed-by:
-
Caroline Tice authored
ThinLTO caching currently has a bug the shows up in Chrome OS and causes bad images to be generated with LLD. This CL disables ThinLTO caching with LLD for Chrome OS, until we can get the ThinLTO caching bug fixed. BUG=chromium:889967 TEST=Tested this patch, build Chrome with LLD in Chrome OS with ThinLTO enabled, and the resulting images were good. Change-Id: I549ee133f0a40f9296ab4d57e8054bcb84e801a8 Reviewed-on: https://chromium-review.googlesource.com/c/1345537Reviewed-by:
Dirk Pranke <dpranke@chromium.org> Reviewed-by:
Peter Collingbourne <pcc@chromium.org> Commit-Queue: Caroline Tice <cmtice@chromium.org> Cr-Commit-Position: refs/heads/master@{#610315}
-
Liquan(Max) Gu authored
In the original comparison logic of performance entries, entries are identified based on entryType, name, detail (if listed) and startTime (if listed). An entry is set to be found only when all of the attributes match. If any of the attribute is not found, the test would just said the entry is not found. But the developer wouldn't know which attribute cause the comparison to fail. In a new logic, we use the name as the identifier for entries. Once the entry is found, we then compare their attributes. In this way, developers would know which attribute caused the failure by the error message. Another benefit of the refactoring is that it factors out the logic of single entry comparison. The logic will be useful for test cases in later patches. Bug: 758385 Change-Id: Ib5721367228f32567efa74cd14a75688fbb34af7 Reviewed-on: https://chromium-review.googlesource.com/c/1346913 Commit-Queue: Liquan (Max) Gǔ <maxlg@chromium.org> Reviewed-by:
Nicolás Peña Moreno <npm@chromium.org> Cr-Commit-Position: refs/heads/master@{#610314}
-
Takashi Toyoshima authored
Chrome internally uses X-Client-Data header, and this should not triggers CORS preflight request. TBR=jochen@chromium.org Bug: 870173, 907018 Change-Id: I67f1711b9065223f9e174e207980940e175031e9 Reviewed-on: https://chromium-review.googlesource.com/c/1335076 Commit-Queue: Takashi Toyoshima <toyoshim@chromium.org> Reviewed-by:
-
Stuart Langley authored
Bug: 731021 Change-Id: I3a894b0c8e225ed031537a908cdc5a914293b4b7 Reviewed-on: https://chromium-review.googlesource.com/c/1345679 Commit-Queue: Stuart Langley <slangley@chromium.org> Reviewed-by:
Noel Gordon <noel@chromium.org> Cr-Commit-Position: refs/heads/master@{#610312}
-
Hiroshi Ichikawa authored
Change-Id: I6187c15d04b5c1df5d3fc520a2647b2499d2720c Reviewed-on: https://chromium-review.googlesource.com/c/1345711 Commit-Queue: Hiroshi Ichikawa <ichikawa@chromium.org> Reviewed-by:
John Wu <jzw@chromium.org> Reviewed-by:
Sylvain Defresne <sdefresne@chromium.org> Cr-Commit-Position: refs/heads/master@{#610311}
-
Kristi Park authored
Expand the toast notification container to fit large font sizes Custom link toast: https://screenshot.googleplex.com/PUqoJ5kQzbt.png https://screenshot.googleplex.com/E6u8dCk4YLM.png Error toast: https://screenshot.googleplex.com/Ky0XtvxYehd.png https://screenshot.googleplex.com/any2UUBJR04.png https://screenshot.googleplex.com/a4BLiXdUdre.png Bug: 899607 Change-Id: Iee80b037e5494a15b2e0a261f1185b435fd1bbc8 Reviewed-on: https://chromium-review.googlesource.com/c/1337439Reviewed-by:
Ramya Nagarajan <ramyan@chromium.org> Commit-Queue: Kristi Park <kristipark@chromium.org> Cr-Commit-Position: refs/heads/master@{#610310}
-
Daniel Cheng authored
ResourceFetcher::ClearContext() can actually queue microtasks; for example, pending FontFace loads will be cancelled and reject the associated promise. Bug: 907270 Change-Id: I83b18924d494052dad021fb3d8bd427de1b9c40c Reviewed-on: https://chromium-review.googlesource.com/c/1347095Reviewed-by:
Kentaro Hara <haraken@chromium.org> Commit-Queue: Daniel Cheng <dcheng@chromium.org> Cr-Commit-Position: refs/heads/master@{#610309}
-
Jeremy Roman authored
Bug: 783060 Change-Id: I02ab0eb7aa0f540a68be1ddfc34c1b4fc16de8e2 Reviewed-on: https://chromium-review.googlesource.com/c/1347060 Commit-Queue: Yuta Kitamura <yutak@chromium.org> Reviewed-by:
Yuta Kitamura <yutak@chromium.org> Cr-Commit-Position: refs/heads/master@{#610308}
-
Kyle Horimoto authored
This callback allows Bluetooth clients on Chrome OS to listen for connection state changes (i.e., when a device goes from connected to disconnected or vice versa). A follow-up CL will add handling for this event in the SecureChannel service to prevent us from accidentally attempting to connect to a disconnecting device (see https://crbug.com/898334). Bug: 898334 Change-Id: Icc18f44106d12a881518f0ece3f0a6e9dd715c0b Reviewed-on: https://chromium-review.googlesource.com/c/1347204Reviewed-by:
Giovanni Ortuño Urquidi <ortuno@chromium.org> Commit-Queue: Kyle Horimoto <khorimoto@chromium.org> Cr-Commit-Position: refs/heads/master@{#610307}
-
Chromium WPT Sync authored
Using wpt-import in Chromium cb59771b. Note to sheriffs: This CL imports external tests and adds expectations for those tests; if this CL is large and causes a few new failures, please fix the failures by adding new lines to TestExpectations rather than reverting. See: https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md Directory owners for changes in this CL: foolip@chromium.org, robertma@chromium.org, smcgruer@chromium.org: external/wpt/infrastructure jsbell@chromium.org: external/wpt/resources NOAUTOREVERT=true TBR=robertma No-Export: true Change-Id: I9f69112f9257f086bc9c4b41945c4e483c6e27bf Reviewed-on: https://chromium-review.googlesource.com/c/1347793 Commit-Queue: WPT Autoroller <wpt-autoroller@chops-service-accounts.iam.gserviceaccount.com> Reviewed-by:
WPT Autoroller <wpt-autoroller@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#610306}
-
Chris Harrelson authored
descendants. This was added in revision 548120 because at the time paint offset baked in sticky position. This was since fixed in revision 590578 that factored sticky position into a transform paint property node rather than paint offset. All that is required is to re-compute paint properties for the scroller and all sticky descendants, in order to update the scroll offset and sticky transform offset. The latter is accomplished by a call to PLSA::InvalidatePaintForStickyDescendants() in PLSA::InvalidatePaintForScrollOffsetChange(). Bug: 895109 Change-Id: Ied7ef8fd15db4f5c3d546f0f06f1adf3cf1e26c8 Reviewed-on: https://chromium-review.googlesource.com/c/1345031Reviewed-by:
Xianzhu Wang <wangxianzhu@chromium.org> Commit-Queue: Chris Harrelson <chrishtr@chromium.org> Cr-Commit-Position: refs/heads/master@{#610305}
-
John Abd-El-Malek authored
This adds support to change the URL of a redirect by a URLLoaderThrottle. Similar to changing the URL at the start of a request, the new URL is restricted to the same origin. This new functionality is only supported when the network service is enabled. This is because the only way to change the URL that is followed after a redirect is through NetworkDelegate::OnBeforeURLRequest. When NS is disabled the NetworkDelegate (ChromeNetworkDelegate) and the URLLoader implementation (MojoAsyncResourceHandler) are in different layers (chrome and content). I didn't want this functionality that is in content/ to depend on chrome/ to make it function correctly. Since the old path is already fixed by r608599 and that code will be deleted once network service ships, I've left it as is. A lot of files change because two core interfaces are changing: 1) URLLoaderThrottle::WillRedirectRequest gets a non-const net::RedirectInfo 2) URLLoader::FollowRedirect gains a "url.mojom.Url? new_url" The interesting parts in this cl are url_loader.mojom, url_loader_throttle.h, throttling_url_loader.*, loader_browsertest.cc, network_context.cc, url_loader.* and google_url_loader_throttle.cc. Bug: 899268 Change-Id: I512de64600500f7e7851aaa0b57f6e46f6cb8001 Reviewed-on: https://chromium-review.googlesource.com/c/1341002 Commit-Queue: John Abd-El-Malek <jam@chromium.org> Reviewed-by:
-
Joel Hockey authored
shortcut handling to work with RU keyboard. Added tests to verify expected behavior for US, DV, RU keyboards. Bug: 725869 Change-Id: I9b81f0bca5fed786fa5b152e25b646cd188ca2a4 Reviewed-on: https://chromium-review.googlesource.com/c/1341444Reviewed-by:
-
Sam McNally authored
Bug: 523292 Change-Id: I24c947f4d33e779ff5b278d855c262cdea87dc3e Reviewed-on: https://chromium-review.googlesource.com/c/1347639Reviewed-by:
-
Sam McNally authored
Test: manual Bug: 889848 Change-Id: I4f7c510e28541bc596c46b8ccd16623dea27fd2b Reviewed-on: https://chromium-review.googlesource.com/c/1347645Reviewed-by:
-
Wei Lee authored
This CL fix the issue that Camera App don't launch when Play Store ToS dialog is shown. Now GCA will only be launched when it is ready. Otherwise, just fallback to launch CCA. BUG=b/119152926 TEST=Tested by enabling/disabling Google Play Store in Settings App and it works as expectation. Change-Id: I51c0a80a3eb6160429b98d40adaf5c56e28d6b61 Reviewed-on: https://chromium-review.googlesource.com/c/1339089Reviewed-by:
Yury Khmel <khmel@chromium.org> Reviewed-by:
Tao Wu <wutao@chromium.org> Commit-Queue: Wei Lee <wtlee@chromium.org> Cr-Commit-Position: refs/heads/master@{#610300}
-
Hayato Ito authored
Chromium sheriff. TBR=wez@chromium.org Bug: 907717 Change-Id: Id0a5bb81ed623572e87f19b9229048febdd3ff2c Reviewed-on: https://chromium-review.googlesource.com/c/1347642Reviewed-by:
Hayato Ito <hayato@chromium.org> Commit-Queue: Hayato Ito <hayato@chromium.org> Cr-Commit-Position: refs/heads/master@{#610299}
-
chrome-release-bot authored
# This is an automated release commit. # Do not revert without consulting chrome-pmo@google.com. NOAUTOREVERT=true TBR=cmasso@chromium.org Change-Id: I1967c870d9f1f81f7629295a9481da8a2aedc359 Reviewed-on: https://chromium-review.googlesource.com/c/1347314Reviewed-by:
chrome-release-bot@chromium.org <chrome-release-bot@chromium.org> Cr-Commit-Position: refs/heads/master@{#610298}
-
Eric Roman authored
Bug: 907673 Change-Id: I71a9bf1433ca7afce1d7482791e008ed809dc04e Reviewed-on: https://chromium-review.googlesource.com/c/1347771Reviewed-by:
Matt Menke <mmenke@chromium.org> Commit-Queue: Matt Menke <mmenke@chromium.org> Cr-Commit-Position: refs/heads/master@{#610297}
-
Shu Chen authored
Bug: 907403 Change-Id: Id300fd5dda6024fcb28d488a32dc13d44924b371 Reviewed-on: https://chromium-review.googlesource.com/c/1347637Reviewed-by:
Leo Zhang <googleo@chromium.org> Commit-Queue: Shu Chen <shuchen@chromium.org> Cr-Commit-Position: refs/heads/master@{#610296}
-
Takashi Toyoshima authored
Currently ServiceWorkerBrowserTest.CrossOriginFetchWithSaveData checks if CORS-preflight requests have "Save-Data" header. This is existing behavior, but new CORS stack does not add the "Save-Data" header for the CORS-preflight. In terms of the fetch spec, it will be better not to have the header in the preflight request. Bug: 907389 Change-Id: Ic6906f5a9ce270a403b7be6f48274f78d2fce546 Reviewed-on: https://chromium-review.googlesource.com/c/1345685Reviewed-by:
Tarun Bansal <tbansal@chromium.org> Reviewed-by:
Matt Falkenhagen <falken@chromium.org> Commit-Queue: Takashi Toyoshima <toyoshim@chromium.org> Cr-Commit-Position: refs/heads/master@{#610295}
-
Jia authored
1. MetricsReporter records daily count of user screen brightness adjustments. It uses local state prefs. 2. This CL also changes the histograms we record: - Previously we record total number of user adjustments, split into those with and without prior model adjustments. - In this CL, we change the reporting so that we record daily counts only. Also, we only record three types of histograms. - Note, we are reusing the enum class, but for different histograms, and the old histograms and its associated enum entry (in enums.xml) are removed. Bug: 881215 Change-Id: I5d5b37af18b1a365f64bd33b61f9f29bbb411962 Reviewed-on: https://chromium-review.googlesource.com/c/1338592 Commit-Queue: Jia Meng <jiameng@chromium.org> Reviewed-by:
Dan Erat <derat@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Reviewed-by:
Steven Holte <holte@chromium.org> Cr-Commit-Position: refs/heads/master@{#610294}
-
chromium-autoroll authored
The AutoRoll server is located here: https://autoroll.skia.org/r/fuchsia-sdk-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:fuchsia-arm64-cast;luci.chromium.try:fuchsia-x64-cast TBR=cr-fuchsia+bot@chromium.org Change-Id: Ifab9496a837c590c6ca525402d0c24eed4aa0f9c Reviewed-on: https://chromium-review.googlesource.com/c/1347081Reviewed-by:
-
