- 03 Dec, 2020 31 commits
-
-
chromium-autoroll authored
https://pdfium.googlesource.com/pdfium.git/+log/8e0ff2457021..46df5d14ee80 2020-12-02 tsepez@chromium.org Remove one form of CFXJSE_ScoeUtil_IsolateHandleContext constructor. 2020-12-02 tsepez@chromium.org Split up CFXJSE_ScopeUtil_IsolateHandleContext If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/pdfium-autoroll Please CC pdfium-deps-rolls@chromium.org on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Bug: None Tbr: pdfium-deps-rolls@chromium.org Change-Id: I7b924521b4d1461139ff600d690b964f0fa3f748 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2570166Reviewed-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@{#833078}
-
James Cook authored
This is a small step toward decoupling //chromeos/constants from //chromeos/dbus. Decoupling should make future code migrations slightly easier, e.g. code moves for lacros. Bug: none Change-Id: Icc27df24c9cfb8ed340da9c489be834ed56d83bb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2570104Reviewed-by:
Steven Bennetts <stevenjb@chromium.org> Reviewed-by:
Dominick Ng <dominickn@chromium.org> Commit-Queue: Dominick Ng <dominickn@chromium.org> Auto-Submit: James Cook <jamescook@chromium.org> Cr-Commit-Position: refs/heads/master@{#833077}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/d1655710f7a7..70828422634e 2020-12-02 recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com Roll recipe dependencies (trivial). If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/depot-tools-chromium-autoroll Please CC ajp@google.com,apolito@google.com,ehmaldonado@google.com,sokcevic@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Bug: None Tbr: ajp@google.com,apolito@google.com,ehmaldonado@google.com,sokcevic@google.com Change-Id: If3c30f3f27a57f04d0e28c847f7401dcba27b322 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2570223Reviewed-by:
-
Makoto Shimazu authored
This reverts commit a954ef5f. Reason for revert: https://crrev.com/c/2569026 has been reverted Original change's description: > Temporarily disable webaudio/DynamicsCompressor/compressor.html > > New test, fails on Mac. > > TBR: rtoy > Bug: 1154883 > Change-Id: I64534e6aa5ee39f928ff7a8c4df21b64a5e70901 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2570019 > Reviewed-by: Dmitry Titov <dimich@chromium.org> > Reviewed-by: Raymond Toy <rtoy@chromium.org> > Commit-Queue: Dmitry Titov <dimich@chromium.org> > Cr-Commit-Position: refs/heads/master@{#833057} TBR=dimich@chromium.org,rtoy@chromium.org,chromium-scoped@luci-project-accounts.iam.gserviceaccount.com Change-Id: Id448bf98326e5dec2d917d2c90e18a7f286fe955 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 1154883 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2568998Reviewed-by:
Makoto Shimazu <shimazu@chromium.org> Commit-Queue: Makoto Shimazu <shimazu@chromium.org> Cr-Commit-Position: refs/heads/master@{#833075}
-
Makoto Shimazu authored
This reverts commit bb8326f6. Reason for revert: The test doesn't seem to pass on Mac and flaky on Linux too. sample build: https://ci.chromium.org/ui/p/chromium/builders/ci/Mac10.14%20Tests/11116/overview Original change's description: > Add test for DynamicsCompressor > > Add a simple test of the DynamicsCompressor using two oscillators and > a gain node to control the amplitude. We compare the output with a > reference file and also compare the reduction values with a known set. > > The reference output and reduction value files were created by saving > the output from the test. > > There's too much variation between browsers to make this a web > platform test. > > Bug: 1013248 > Test: webaudio/DynamicsCompressor/compressor.html > Change-Id: Ib7c68b5b8ffa79b0a78b5b842fef4b121e1bcf52 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2364744 > Commit-Queue: Raymond Toy <rtoy@chromium.org> > Reviewed-by: Hongchan Choi <hongchan@chromium.org> > Cr-Commit-Position: refs/heads/master@{#832890} TBR=rtoy@chromium.org,hongchan@chromium.org,chromium-scoped@luci-project-accounts.iam.gserviceaccount.com Change-Id: I05d4fdbc0c90b57e354d3bc0537f962c6e437fa9 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 1013248 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2569026Reviewed-by:
-
dpapad authored
This script: - Is basically unmaintained. - It's unclear if it still works - Has not been very helpful and does not justify the cost of maintaining it. - Is unlikely to be ported to work with Polymer3 JS imports in third_party/polymer/v3_0/ folder. Moreover, we have way less Polymer UI elemens dependencies than when this script was originally authored, and manually identifying unused elements has not been a problem. Fixed: 997850 Change-Id: Ic062bf1bc1cccf4bd2c98bb37a83b9103270dbb2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2569372 Commit-Queue: Rebekah Potter <rbpotter@chromium.org> Auto-Submit: dpapad <dpapad@chromium.org> Reviewed-by:
Rebekah Potter <rbpotter@chromium.org> Cr-Commit-Position: refs/heads/master@{#833073}
-
chromium-autoroll authored
If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/fuchsia-sdk-chromium-autoroll Please CC chrome-fuchsia-gardener@grotations.appspotmail.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:fuchsia-arm64-cast;luci.chromium.try:fuchsia-deterministic-dbg;luci.chromium.try:fuchsia-x64-cast Tbr: chrome-fuchsia-gardener@grotations.appspotmail.com Change-Id: I5f007ff9188166b6f4eff40a7c13cc3fb9314c8d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2570037Reviewed-by:
-
Jiewei Qian authored
SettingsWindowObserver is used to check if the number of OS Settings browser instances are correct. This can be performed in other ways without relying on SettingsWindowManager. SettingsWindowManager predates the SWA platform, which implements many features wanted by OS Settings, but were otherwise unavailable. After SWA platform launch, we have implemented these features in SWA platform, so it's no longer necessary for OS Settings to duplicate these logics. This is a preparation for implementing a new LaunchSystemWebApp API, which no longer returns the Browser object running the launched App. Bug: 1154540 Change-Id: I2c3322d30fbf2c288e03aa3cc139f9f3bbf74920 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2569191 Commit-Queue: Jiewei Qian <qjw@chromium.org> Reviewed-by:
James Cook <jamescook@chromium.org> Cr-Commit-Position: refs/heads/master@{#833071}
-
Charlie Hu authored
The fix to missing document policy in XSLT documents involves initialize document policy from previous security context, which results |DocumentLoader::document_policy_| not having correct policy content before document policy initialization in |SecurityContextInit|. This CL moves the check for ForceLoadAtTop feature after document policy initialization, so that its behaviour is consistent in XSLT documents. Bug: 1151954 Change-Id: I0a4061975a26cbf922b322c908ce8c2c88897715 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2568439Reviewed-by:
Dmitry Gozman <dgozman@chromium.org> Reviewed-by:
Ian Clelland <iclelland@chromium.org> Commit-Queue: Charlie Hu <chenleihu@google.com> Cr-Commit-Position: refs/heads/master@{#833070}
-
David Trainor authored
TBR=changwan@chromium.org Bug: 1153705 Change-Id: I94974a23a913f51046d0d092f0fb3b827a88cbcf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2570208Reviewed-by:
David Trainor <dtrainor@chromium.org> Reviewed-by:
Changwan Ryu <changwan@chromium.org> Commit-Queue: David Trainor <dtrainor@chromium.org> Commit-Queue: Changwan Ryu <changwan@chromium.org> Auto-Submit: David Trainor <dtrainor@chromium.org> Cr-Commit-Position: refs/heads/master@{#833069}
-
Daniel Hosseinian authored
PDFium's FPDFText_GetTextRenderMode() is technically an experimental API, but it guarantees to return enum values within a certain range. By statically asserting the bounds of FPDF_TEXT_RENDERMODE, we can simply DCHECK the returned value of FPDFText_GetTextRenderMode() against those bounds instead of handling an out-of-bounds value in runtime. Change-Id: I89d377eeaaab5186712e6b85683bf658590eab53 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2567452 Commit-Queue: Daniel Hosseinian <dhoss@chromium.org> Reviewed-by:
Tom Sepez <tsepez@chromium.org> Cr-Commit-Position: refs/heads/master@{#833068}
-
danakj authored
Step 4 for bug 1125106. This is a subset of the mega-patch in https://chromium-review.googlesource.com/c/chromium/src/+/2462248. A same-document navigation is a request to navigate the currently loaded document to the specified anchor tag from the URL. Renderer-initiated navigations simply perform the scroll operation and update history. Browser-initiated ones are treated as a navigation. However there are many things that could cause the given URL to want to load in a different SiteInstance than what was used for the previous load. But using a different SiteInstance would also mean reloading the document - which means it is no longer a same-document navigation. Previous patches in this series have prevented us from trying to load a same-document navigation when there would be valid reasons to want to do a cross-document navigation. Follow-up patches will introduce CHECK()s in the renderer to show that we are in fact never trying to perform a same-document navigation anymore when we would have required a cross-document navigation (with the exception of navigating a frameset which must fallback to cross- document). R=nasko@chromium.org Bug: 1125106 Change-Id: I3603cb0a3698d9e6241aca4eb8895db4fcdfd139 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2558760 Commit-Queue: danakj <danakj@chromium.org> Reviewed-by:
Nasko Oskov <nasko@chromium.org> Cr-Commit-Position: refs/heads/master@{#833067}
-
Frédéric Wang authored
Per [1], only about:blank and about:srcdoc URLs should be treated as potentially trustworthy, but Chromium currently accepts all about: URLs. This CL aligns with the current spec, with the additional assumption that query and fragment components are accepted too [2]. This change is not web-visible. [1] https://w3c.github.io/webappsec-secure-contexts/#potentially-trustworthy-url [2] https://github.com/w3c/webappsec-secure-contexts/issues/81 Bug: 1153335, 1153336 Change-Id: I907d90596b4895a3d3b6efbfd535b2efe9e9cc8b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2563492 Commit-Queue: Frédéric Wang <fwang@igalia.com> Reviewed-by:
Matt Falkenhagen <falken@chromium.org> Reviewed-by:
Mike West <mkwst@chromium.org> Cr-Commit-Position: refs/heads/master@{#833066}
-
Daniel Hosseinian authored
When the plugin sends a message to the renderer, bounds checking is performed on all IPC enum traits. Messages containing bad data are dropped. Consequently, text runs containing no text need to have their style initialized to an unknown mode instead of leaving the field uninitialized. The uninitialized field was trying to pass garbage values through IPC, causing the entire message to be dropped. This issue was discovered after crrev.com/830918 was reverted, because the change depended on accessibility info to be sent sequentially for every page. A single dropped message would prevent the accessibility tree from ever finishing. Bug: 1150665 Change-Id: I0857b79da817e01a9c570d5a9172086ad9f39d67 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2567353 Reviewed-by: Ankit Kumar
🌪 ️ <ankk@microsoft.com> Reviewed-by:Bill Budge <bbudge@chromium.org> Commit-Queue: Daniel Hosseinian <dhoss@chromium.org> Cr-Commit-Position: refs/heads/master@{#833065}
-
chromium-autoroll authored
Roll Chrome Win64 PGO profile from chrome-win64-master-1606910266-ef600127b93b5e1e3330f538f7207fdf2db6ba60.profdata to chrome-win64-master-1606920808-0540fdc6e596cc19c39443c176b663ce2ec75493.profdata If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/pgo-win64-chromium Please CC pgo-profile-sheriffs@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chrome.try:win64-chrome Tbr: pgo-profile-sheriffs@google.com Change-Id: I3e60dc6ec27571eafc6f4cc599a7a76f8ba1d66e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2570035Reviewed-by:
-
Azeem Arshad authored
This CL adds eid property to network_state and exposes it in cros_network_config api. Hermes fake clients are also updated to set EID property on fake eSIM network state. Bug: 1093185 Change-Id: Ied18d96902d0563b96f9617e77d9afc967a40c45 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2541562 Commit-Queue: Azeem Arshad <azeemarshad@chromium.org> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Cr-Commit-Position: refs/heads/master@{#833063}
-
Brandon Wylie authored
This reverts commit a3349311. Reason for revert: Broke clank testers, see crbug.com/1154838. Original change's description: > [WebLayer] Fix FragmentActivityReplacer with SupportLifecycleFragmentImpl > > This fixes a comilation error due to FragmentActivityReplacer's > interaction with SupportLifecycleFragmentImpl. > > Bug: 1152898, 1123216 > Change-Id: I81de8100f7ddd08310f8a36c8f1c9c62e82c0469 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2566455 > Reviewed-by: Andrew Grieve <agrieve@chromium.org> > Reviewed-by: Sam Maier <smaier@chromium.org> > Commit-Queue: Robbie McElrath <rmcelrath@chromium.org> > Cr-Commit-Position: refs/heads/master@{#832426} TBR=agrieve@chromium.org,rmcelrath@chromium.org,smaier@chromium.org,chromium-scoped@luci-project-accounts.iam.gserviceaccount.com # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 1152898 Bug: 1123216 Change-Id: I4932f374ea69c87005cf2ff8ba3ea56d883d879e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2567180Reviewed-by:
Brandon Wylie <wylieb@chromium.org> Reviewed-by:
Robbie McElrath <rmcelrath@chromium.org> Commit-Queue: Haiyang Pan <hypan@google.com> Cr-Commit-Position: refs/heads/master@{#833062}
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/04ee79c749be..b6e840c0368f 2020-12-02 alessiob@webrtc.org RNN VAD: SSE2 optimization for `VectorMath::DotProduct` If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/webrtc-chromium-autoroll Please CC webrtc-chromium-sheriffs-robots@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Bug: None Tbr: webrtc-chromium-sheriffs-robots@google.com Change-Id: Ib1b571671327ff1a276bfe8178be307e56ba7a54 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2570043Reviewed-by:
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/1366dd01174e..ae504d46b4c4 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/perfetto-trace-processor-mac-chromium Please CC perfetto-bugs@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Tbr: perfetto-bugs@google.com Change-Id: I4f40a8a5bb223fdc45e1f986123ee6394f2b3529 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2569380Reviewed-by:
-
Zach Trudo authored
The endpoint for EncryptedReportingJobConfiguration doesn't utilize the profile message provided by context. Additionally the endpoint expects uint64 to be encoded as strings (JSON can't handle 64 bit integers). Bug: chromium:1078512 Change-Id: I5306f940b62e49ad763bfbad31a92f16dc06e7fa Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2558006 Commit-Queue: Zach Trudo <zatrudo@google.com> Auto-Submit: Zach Trudo <zatrudo@google.com> Reviewed-by:
Sergey Poromov <poromov@chromium.org> Cr-Commit-Position: refs/heads/master@{#833059}
-
Austin Eng authored
Adds variants of the following WebGL perf tests with --enable-unsafe-js-fast-calls - Animometer - Animometer Indexed - Aquarium 20k - Skelebuddies wasm - Tiny Racing wasm - Microgame FPS - Lost Crypt Bug: 1101475 Change-Id: I7280d00980af32e96aef7e35a53139e93d4e2b7e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2519363Reviewed-by:
Brian Sheedy <bsheedy@chromium.org> Reviewed-by:
Kenneth Russell <kbr@chromium.org> Commit-Queue: Austin Eng <enga@chromium.org> Cr-Commit-Position: refs/heads/master@{#833058}
-
Dmitry Titov authored
New test, fails on Mac. TBR: rtoy Bug: 1154883 Change-Id: I64534e6aa5ee39f928ff7a8c4df21b64a5e70901 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2570019Reviewed-by:
Dmitry Titov <dimich@chromium.org> Reviewed-by:
Raymond Toy <rtoy@chromium.org> Commit-Queue: Dmitry Titov <dimich@chromium.org> Cr-Commit-Position: refs/heads/master@{#833057}
-
Xinghui Lu authored
Bug: 1097310 Change-Id: Icac2b18a2a289bef1315e60bff51d77f14d40a85 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2568585 Commit-Queue: Xinghui Lu <xinghuilu@chromium.org> Commit-Queue: Varun Khaneja <vakh@chromium.org> Auto-Submit: Xinghui Lu <xinghuilu@chromium.org> Reviewed-by:
Varun Khaneja <vakh@chromium.org> Cr-Commit-Position: refs/heads/master@{#833056}
-
Michael Lippautz authored
Bug: 1154667 Change-Id: I16e5f4d099ce9a3bbabe7c6e7888fd541038d151 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2569667 Auto-Submit: Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Kentaro Hara <haraken@chromium.org> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Cr-Commit-Position: refs/heads/master@{#833055}
-
chromium-autoroll authored
https://chromium.googlesource.com/openscreen.git/+log/6270c082b9aa..48b4a74d6b80 2020-12-02 jophba@chromium.org Fix local build If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/openscreen-chromium Please CC jophba@chromium.org on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Bug: None Tbr: jophba@chromium.org Change-Id: I3261caf2bbaaec091a317a1145e41517a4026e95 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2569959Reviewed-by:
-
Norman Rosas authored
//components/send_tab_to_self and removed duplicated metadata from OWNERS files Bug: 1113033 Change-Id: I58dcbd2fadba57e2f7dec1cabde5df6557321632 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2570243 Auto-Submit: Norman Rosas <normando@google.com> Commit-Queue: Nico Weber <thakis@chromium.org> Reviewed-by:
Nico Weber <thakis@chromium.org> Cr-Commit-Position: refs/heads/master@{#833053}
-
Anna Malova authored
Bug: 1085115 Change-Id: Ib417fea14f0096a9769f106a332697153c8be34b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2566962Reviewed-by:
Richard Coles <torne@chromium.org> Commit-Queue: Anna Malova <amalova@chromium.org> Cr-Commit-Position: refs/heads/master@{#833052}
-
Noel Gordon authored
Use the this.renderOrientation_ feature for better cache keying of RAW image thumbnails from piexwasm. The client's this.request_.orientation forms part of the image loader cache key: we should leave it alone and using this.renderOrientation_ allows us to do that. To be clear, further testing of RAW images that have EXIF orientation, has shown that they are _not_ affected by issue 1152084. Bug: 1152084 Change-Id: I7665985df51ddecdb4bb5bebf2437f910d82330b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2569317 Commit-Queue: Alex Danilo <adanilo@chromium.org> Auto-Submit: Noel Gordon <noel@chromium.org> Reviewed-by:
Alex Danilo <adanilo@chromium.org> Cr-Commit-Position: refs/heads/master@{#833051}
-
Nancy Wang authored
Add the components/full_restore directory to provide some general functions, interfaces, so that the wm component from ash, the app service and the components/exo component can easily access the interfaces in components/full_restore to implement the restoration function. Implement the ShouldRestore interface for the wm component to query whether we should restore virtual desks, split screen, etc, based on go/chrome-os-full-restore-interfaces. Mock: go/cros-full-restore PRD: go/cros-full-restore-prd Design doc: go/chrome-os-full-restore-dd BUG=1146900 Change-Id: I40a8a625f50f979355e113d2dcc6db6b2201cc02 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2563427 Commit-Queue: Nancy Wang <nancylingwang@chromium.org> Reviewed-by:
Cait Phillips <caitkp@chromium.org> Reviewed-by:
Xiyuan Xia <xiyuan@chromium.org> Cr-Commit-Position: refs/heads/master@{#833050}
-
Ben Pastene authored
Until crbug.com/1141234 is complete, the current public kevin pool is quite overloaded. eg: https://ci.chromium.org/p/chromium/builders/try/chromeos-kevin-rel/3153? https://ci.chromium.org/p/chromium/builders/try/chromeos-kevin-rel/3158? This should help reduce load while we wait for more DUT capacity. Bug: None Change-Id: I468eca706b709121e4267f411a1ab57b5c9cb4dd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2570072Reviewed-by:
-
Alex Danilo authored
CL:2568919 removed the progress center group code that isn't used. Remove the TODO comment which isn't needed any more. No-try: true Bug: 1027012 Change-Id: I4e3e9f50175886479cd3956b1e5f950fdf7f3fd6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2567244Reviewed-by:
Luciano Pacheco <lucmult@chromium.org> Commit-Queue: Luciano Pacheco <lucmult@chromium.org> Cr-Commit-Position: refs/heads/master@{#833048}
-
- 02 Dec, 2020 9 commits
-
-
Ryan Hansberry authored
Nearby Connections needs to specify that its registered RFCOMM service should not bond to the remote device on the other side of the connection; CreateRfcommService() is adjusted to CreateRfcommServiceInsecurely() to accommodate this need. Sidenote: this further necessitates an allowlist on service UUIDs and service names: that is tracked at b/162975217. Fixed: 1151116 Change-Id: I8db8e9864ce22122b7af6c8554161f987f6114d0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2553188Reviewed-by:
Reilly Grant <reillyg@chromium.org> Reviewed-by:
James Vecore <vecore@google.com> Commit-Queue: Ryan Hansberry <hansberry@chromium.org> Cr-Commit-Position: refs/heads/master@{#833047}
-
Rachel Wong authored
This CL removes a few launcher metrics that are no longer used, including some that are expiring. Bug: 1142490, 1152023 Change-Id: Id10ad35ee9ee6e6ed3933d811bd4bf721bdc258c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2567236Reviewed-by:
Tony Yeoman <tby@chromium.org> Commit-Queue: Rachel Wong <wrong@chromium.org> Cr-Commit-Position: refs/heads/master@{#833046}
-
spdonghao authored
Demos: Before this CL: https://drive.google.com/file/d/1rGxWGyHhN1Nft2UQACOu6iH045dXhf7D/view?usp=sharing&resourcekey=0-iUuO4moaXQ1z4cqhbbzTdg After this CL: https://drive.google.com/file/d/1yjB2IVO0v7Kf2D---L3PVMhd_J4zbP9W/view?usp=sharing&resourcekey=0-Fyz_1WPerkvgv_2aBCVgVg Bug: 1136245 Change-Id: Ia39231b975a12ec7f7739f428ba344d8005d5fcc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2564010Reviewed-by:
Xi Han <hanxi@chromium.org> Reviewed-by:
Matthew Jones <mdjones@chromium.org> Reviewed-by:
Wei-Yin Chen (陳威尹) <wychen@chromium.org> Commit-Queue: Hao Dong <spdonghao@chromium.org> Cr-Commit-Position: refs/heads/master@{#833045}
-
chromium-autoroll authored
https://swiftshader.googlesource.com/SwiftShader.git/+log/bfb211914759..95ffe036632c 2020-12-02 natsu@google.com Guard VK_GOOGLE_SAMPLER_FILTERING_PRECISION 2020-12-02 amaiorano@google.com LLVM: add option to emit asm file to aid debugging 2020-12-02 amaiorano@google.com Coroutine: allow a name to be passed in for routine generation 2020-12-02 amaiorano@google.com ReactorUnitTests: use test name as Routine names 2020-12-02 amaiorano@google.com LLVM: store input name in JITRoutine 2020-12-02 amaiorano@google.com Fix FunctionT not forwarding its varargs If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/swiftshader-chromium-autoroll Please CC swiftshader-team+autoroll@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_chromium_msan_rel_ng;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:linux-swangle-try-x64;luci.chromium.try:win-swangle-try-x86 Bug: None Tbr: swiftshader-team+autoroll@google.com Change-Id: I4346e8c51d43762371c344ba91886393d0396ba6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2569970Reviewed-by:
-
Lin XInan authored
BUG=chromium:1153349 TEST=./main.star Change-Id: Ibfdbf9379d5b31b6031371043a7273a838aa6718 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2569689 Commit-Queue: Xinan Lin <linxinan@chromium.org> Reviewed-by:
Ben Pastene <bpastene@chromium.org> Reviewed-by:
Haiyang Pan <hypan@google.com> Cr-Commit-Position: refs/heads/master@{#833043}
-
Marijn Kruisselbrink authored
This isn't directly using net::IsSafePortablePathComponent since what is safe for the File System Access API is not the same as what is safe for Downloads. As such currently this duplicates a lot of the implementation of this method, but in a followup we should attempt to unify these two implementations as much as possible. Bug: 1150810, 1154757 Change-Id: Iba4c92ef5f1cd924aa22b9dd201762d48b4bbc3b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2568383 Commit-Queue: Marijn Kruisselbrink <mek@chromium.org> Reviewed-by:
Victor Costan <pwnall@chromium.org> Cr-Commit-Position: refs/heads/master@{#833042}
-
Dmitry Titov authored
TBR: jdoerrie Bug: 1154856 Change-Id: Ib95f47f67c3646c4ff3f1fbca843aacc99bddeee Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2567181Reviewed-by:
-
Zach Trudo authored
Bug: chromium:1078512 Change-Id: I696ad733b399edbb13251c12fac8736b37a34598 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2568779 Auto-Submit: Zach Trudo <zatrudo@google.com> Reviewed-by:
-
Oystein Eftevaag authored
Adds support to the field-trial system for layers: * A field-trial can declare itself a member of a layer * A layer will pick only one member to be activate at a time. This reduces issues with metrics cross-talk between experiments, and enables a number of advanced use-cases for more fine grained control over holdbacks and launches. BUG=1146226 R=isherman,holte Change-Id: I5ada1eda97588e42af2dd061bc0ba8bd49a0fa17 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2340392 Commit-Queue: oysteine <oysteine@chromium.org> Reviewed-by:
Alexei Svitkine <asvitkine@chromium.org> Reviewed-by:
Steven Holte <holte@chromium.org> Cr-Commit-Position: refs/heads/master@{#833039}
-
