- 04 Dec, 2020 40 commits
-
-
chromium-autoroll authored
https://chromium.googlesource.com/openscreen.git/+log/12b95e78a4d5..b9d9529da93a 2020-12-04 jophba@chromium.org Add RBE-CAS instance names to buildbucket 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: I150c2969c5d97535c39bccf97907b9c55def5ffc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2575217Reviewed-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@{#833806}
-
Wez authored
Bug: 1071393 Bug: b/154204041 Test: web_engine_unittests Change-Id: I3ba86964279ef7f467506d0781bee1e75b169a0e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2571699 Commit-Queue: Wez <wez@chromium.org> Reviewed-by:
David Dorwin <ddorwin@chromium.org> Cr-Commit-Position: refs/heads/master@{#833805}
-
Jimmy Gong authored
CanRequestNewDndState indicates whether or not the DoNotDisturb feature should be enabled for the Phone Hub UI. Bug: 1155244 Test: chromeos_components_unittest Change-Id: Ief42e2f3cefdcb2aa4a74b5e41a5f7329ae330c3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2572958 Commit-Queue: Jimmy Gong <jimmyxgong@chromium.org> Reviewed-by:
Kyle Horimoto <khorimoto@chromium.org> Cr-Commit-Position: refs/heads/master@{#833804}
-
Yifan Luo authored
Bug: 1116418 Change-Id: Icecc7124ce0f8e448a5ae95037eb3a3adfe7af2c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2575296Reviewed-by:
Yifan Luo <lyf@chromium.org> Reviewed-by:
Daniel Vogelheim <vogelheim@chromium.org> Commit-Queue: Yifan Luo <lyf@chromium.org> Cr-Commit-Position: refs/heads/master@{#833803}
-
Phu Le authored
Currently today OpenXR event pump does not have a callback to the render loop and instead setting a state for session end and relies on the next frame to check that state. This is not reliable as most of the time, the frame pump stops after sessions ends and the state logic has race condition inside that changes as the code churns. This change add an explicit callback to notify the end of a XR session so that the render loop can reliably trigger the blink callback on session's end. Bug: 1148648 Change-Id: I5447b0d053bbc1d575c9b509edc0ca5d6f76bca8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2535852 Commit-Queue: Phu Le <phle@microsoft.com> Reviewed-by:
Alexander Cooper <alcooper@chromium.org> Cr-Commit-Position: refs/heads/master@{#833802}
-
Erik Chen authored
This reverts commit 8d4df26b. Reason for revert: Reverting for now -- this enables Finch configs for Lacros -- which in turn will turn on Vulkan backend for Skia, which can (sometimes) crash Lacros on launch. Original change's description: > Set "dev" channel for all lacros builds. > > Linux-chrome (of which lacros is a variant) has its channel set as a > runtime environment variable by the launcher script. For Lacros, we must > set the environment variable from ash. For now, we always set "dev" for > all builds of Lacros. > > Change-Id: I840286b6fd5772701c3f6d927986405697b82097 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2570448 > Commit-Queue: Erik Chen <erikchen@chromium.org> > Reviewed-by: James Cook <jamescook@chromium.org> > Cr-Commit-Position: refs/heads/master@{#833460} TBR=jamescook@chromium.org,erikchen@chromium.org,chromium-scoped@luci-project-accounts.iam.gserviceaccount.com Change-Id: I25d3d72d27571645ef9b1723e624e75859579d8b No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2574803Reviewed-by:
Erik Chen <erikchen@chromium.org> Commit-Queue: Erik Chen <erikchen@chromium.org> Cr-Commit-Position: refs/heads/master@{#833801}
-
Alan Screen authored
TestPrintBackend was reworked to include a more consistent behavior across its interfaces. With this in place we can now update the testing for print backend service to use AddValidPrinter() that ensures valid printer definitions. This allows the GetDefaultPrinterName test to be re-enabled and prepares for further updates related to printer capabilities. Bug: 809738 Change-Id: Iedf2d219da40cb508b6778f70889e86cccfb0052 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2538365Reviewed-by:
Rebekah Potter <rbpotter@chromium.org> Commit-Queue: Alan Screen <awscreen@chromium.org> Cr-Commit-Position: refs/heads/master@{#833800}
-
Stepan Khapugin authored
Exposes necessary tail suggest fields of an autocomplete match, wrapped in Foundation types. Bug: none Change-Id: Ia8a8a1e69befc3a8e510dfa196deda1544b9290e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2571876 Commit-Queue: edchin <edchin@chromium.org> Reviewed-by:
edchin <edchin@chromium.org> Reviewed-by:
Robbie Gibson <rkgibson@google.com> Auto-Submit: Stepan Khapugin <stkhapugin@chromium.org> Cr-Commit-Position: refs/heads/master@{#833799}
-
Gang Wu authored
Bug: 1155430 Change-Id: I5e323b8ecfdcdfbbbd9c98f575c864e17ff62d81 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2574078Reviewed-by:
Finnur Thorarinsson <finnur@chromium.org> Reviewed-by:
Theresa <twellington@chromium.org> Commit-Queue: Gang Wu <gangwu@chromium.org> Cr-Commit-Position: refs/heads/master@{#833798}
-
Tommy Li authored
Previously, we were using "key1", "key2", etc. as the GUIDs for our test engines. This was confusing, because "key1", etc. was also used for the keywords to our test engines. For clarity, we've changed all GUIDs of the form "key1" to "guid1", and added a DCHECK to warn developers not to do it again. No functional changes here, just a simple rename of constants in our test files. Bug: 1022775 Change-Id: I776feb17190942fc23e4c5a5d669bc0dbfec537b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2573339 Commit-Queue: Tommy Li <tommycli@chromium.org> Reviewed-by:
Mikel Astiz <mastiz@chromium.org> Cr-Commit-Position: refs/heads/master@{#833797}
-
Sergey Ulanov authored
This reverts commit 4c19ca70. Reason for revert: Broke NTP tests on MSan bots, see https://ci.chromium.org/ui/p/chromium/builders/ci/Linux%20MSan%20Tests/26482/test-results?expected=false&exonerated=true&flaky=true Original change's description: > [NTP][RQ] Adds field trial testing config for repeatable queries > > This is in preparation to promote the canary experiment which > originally landed in cl/339288320 to Beta. > > Fixed: 1155314 > Change-Id: I4b87b89736e4cb461d416aacef98ed888596568c > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2573130 > Commit-Queue: Moe Ahmadi <mahmadi@chromium.org> > Reviewed-by: Weilun Shi <sweilun@chromium.org> > Cr-Commit-Position: refs/heads/master@{#833576} TBR=mahmadi@chromium.org,sweilun@chromium.org,chromium-scoped@luci-project-accounts.iam.gserviceaccount.com Change-Id: I2f53745425e4df57bae943cbd3a4ab3c23de8cda No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2575340Reviewed-by:
Sergey Ulanov <sergeyu@chromium.org> Commit-Queue: Sergey Ulanov <sergeyu@chromium.org> Cr-Commit-Position: refs/heads/master@{#833796}
-
Muhammad Hasan Khan authored
There are multiple reasons for which we show same message in case of sign-in and check-in failure so we're adding an error code on the UI to help distinguish the underlying reasons. BUG=b:166322619 TEST=deploy to DUT, force the sign-in failure, verify message is shown Change-Id: If8e758d02777c3aaa5ced74ac44eaa54dee8a59e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2569988 Commit-Queue: Muhammad Hasan Khan <mhasank@chromium.org> Reviewed-by:
Hidehiko Abe <hidehiko@chromium.org> Cr-Commit-Position: refs/heads/master@{#833795}
-
David Maunder authored
Apply batching to CriticalPersistedTabData tests so that they run faster. Bug: 1152295 Change-Id: I655e4ffe2f79a8549311b32a1f7ff760f3dda34e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2556453Reviewed-by:
Yusuf Ozuysal <yusufo@chromium.org> Reviewed-by:
Wei-Yin Chen (陳威尹) <wychen@chromium.org> Commit-Queue: David Maunder <davidjm@chromium.org> Cr-Commit-Position: refs/heads/master@{#833794}
-
Egor Pasko authored
The test creates a fake RELRO region in private memory and checks that it is spawned into a sealed read-only shared memory region. Since the normal way of using the ModernLinker involves a separate DSO (=shared library), this would add more moving parts to base_unittests. We prefer less advanced ways with GN, so another approach is chosen: all the necessary code is linked with base_unittests. Testing the way ModernLinker loads libraries would be difficult without extra libraries pushed to the device, but RELRO region creation, sharing and consumption can be tested using this approach. Bug: 1154224 Change-Id: Ia78cce98f566084f6f799a7a35ab3cc45beb9346 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2571758Reviewed-by:
Benoit L <lizeb@chromium.org> Commit-Queue: Egor Pasko <pasko@chromium.org> Cr-Commit-Position: refs/heads/master@{#833793}
-
Ben Wagner authored
This is a followup to https://chromium-review.googlesource.com/c/chromium/src/+/2566935/5#message-8b391d170d115a9b89c0a985ab0a8a42a208695b Change-Id: I3c63a4792d26206a9cb91136ce9da72edcb1b70e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2573038 Commit-Queue: John Chen <johnchen@chromium.org> Auto-Submit: Ben Wagner aka dogben <benjaminwagner@google.com> Reviewed-by:
Mirko Bonadei <mbonadei@chromium.org> Reviewed-by:
John Chen <johnchen@chromium.org> Cr-Commit-Position: refs/heads/master@{#833792}
-
chromium-autoroll authored
Roll Chrome Win64 PGO profile from chrome-win64-master-1607061555-9d7880873554417bd44ed300f865acac635c5256.profdata to chrome-win64-master-1607070900-a3f370d99263588b261e824540349b020ef94941.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: Ie8b00905ee134164d074ad60ecb6988916cb5c5d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2574422Reviewed-by:
-
Shu-yu Guo authored
When top-level await is enabled, all module script evaluation is expected to return a Promise. This CL changes ValueWrapperSyntheticModuleScripts (CSS and JSON) to return a Promise that's resolved to undefined. Bug: v8:1154497 Change-Id: I92114d42f0080918e9e61bf1b62d5eda4cffdabc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2568823 Commit-Queue: Shu-yu Guo <syg@chromium.org> Reviewed-by:
Hiroshige Hayashizaki <hiroshige@chromium.org> Reviewed-by:
Yuki Shiino <yukishiino@chromium.org> Cr-Commit-Position: refs/heads/master@{#833790}
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/1ad5791d97be..51a0e95d78eb 2020-12-04 ianelliott@google.com Revert "Suppress memory leaks detected by LSAN" 2020-12-04 angle-autoroll@skia-public.iam.gserviceaccount.com Roll VK-GL-CTS from 524e5bcfba33 to 41331850eb21 (39 revisions) 2020-12-04 angle-autoroll@skia-public.iam.gserviceaccount.com Roll Chromium from d76e39a7 to 78187c02 (806 revisions) 2020-12-04 sugoi@google.com Suppress memory leaks detected by LSAN If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/angle-chromium-autoroll Please CC ianelliott@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_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win-asan;luci.chromium.try:win_optional_gpu_tests_rel;luci.chromium.try:linux-swangle-try-x64;luci.chromium.try:win-swangle-try-x86 Bug: chromium:972686 Tbr: ianelliott@google.com Change-Id: I512c7d239bc2eb8860eea0bcd8421c205342193b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2574721Reviewed-by:
-
Charlie Hu authored
This CL renames 'feature policy' to 'permissions policy' in console messages. Bug: 1123116 Change-Id: Ia7a526e44ccc1d0eb3109f2fb86b12ad7ba2daec Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2513824Reviewed-by:
Nico Weber <thakis@chromium.org> Reviewed-by:
Ian Clelland <iclelland@chromium.org> Reviewed-by:
Dmitry Gozman <dgozman@chromium.org> Commit-Queue: Charlie Hu <chenleihu@google.com> Cr-Commit-Position: refs/heads/master@{#833788}
-
Toni Barzic authored
This is a reland of 2a07cc57 Original change's description: > Shutdown holding space delegates while device is suspended > > Some file systems are unmounted during device suspend (for example drive > FS), which was causing the holding space file system delegate's file > path removal detection to remove them from the holding space on device > suspend. To avoid this issue, holding space keyed service now observes > device suspend status and shuts down holding space delegates when the > device suspends. The delegates are re-initialized when suspend ends, > restoring the model from persistence again. > > BUG=1152924 > > Change-Id: Iffe4586bcb87f47d687ceeff0fc76e60a443c0d5 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2568355 > Commit-Queue: Toni Baržić <tbarzic@chromium.org> > Reviewed-by: David Black <dmblack@google.com> > Cr-Commit-Position: refs/heads/master@{#833515} Bug: 1152924 Change-Id: I4ef1fa83d684260e4ebf66fe4c01e9627e5c46af Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2573893Reviewed-by:
David Black <dmblack@google.com> Commit-Queue: Toni Baržić <tbarzic@chromium.org> Cr-Commit-Position: refs/heads/master@{#833787}
-
Findit authored
This reverts commit 5326cda9. Reason for revert: Findit (https://goo.gl/kROfz5) identified CL at revision 833751 as the culprit for failures in the build cycles as shown on: https://analysis.chromium.org/waterfall/culprit?key=ag9zfmZpbmRpdC1mb3ItbWVyRAsSDVdmU3VzcGVjdGVkQ0wiMWNocm9taXVtLzUzMjZjZGE5NmNhOTdlN2ZiMDdlYTBhMzNkODUyN2RmYmRkZmJiNWYM Sample Failed Build: https://ci.chromium.org/b/8861821025876153104 Sample Failed Step: compile Original change's description: > Patch in Fix For Protobuf Deserialization Bug > > This CL picks up a bugfix integrated into protobuf as part of commit: > http://cl/342360226 > > This fix is responsible for fixing a bug in the serialization code > when trying serialize/deserialize protobuf messages at the end of an > iostream > > Change-Id: I7608174a083b6b63c152c1250d3ccd1fd53914c6 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2535667 > Reviewed-by: Leonard Grey <lgrey@chromium.org> > Commit-Queue: Ryan Keane <rwkeane@google.com> > Cr-Commit-Position: refs/heads/master@{#833751} Change-Id: If9e7cb5da756a985bfc53fe03be0632e3cdbdef1 No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2575436 Cr-Commit-Position: refs/heads/master@{#833786}
-
Ana Salazar authored
In the Holding Space's Screen Capture section, we display screenshots and screen recordings. At the moment, both previews display as still images. In order to differentiate between screenshots and screen recordings, we add a play icon over the screen recordings. Screenshot: https://screenshot.googleplex.com/9YVVkvvyAk7Duds Bug: 1144927 Change-Id: Id1614a867caa73676d24c9ab59289337fea88c63 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2566051 Commit-Queue: Ana Salazar <anasalazar@chromium.org> Reviewed-by:
Toni Baržić <tbarzic@chromium.org> Cr-Commit-Position: refs/heads/master@{#833785}
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/ad70609509a9..6c80aebd0036 2020-12-04 henrik.lundin@webrtc.org Remove kwiberg@webrtc.org from OWNERS files 2020-12-04 hta@webrtc.org Relax check for unknown STUN attribute lengths 2020-12-04 mbonadei@webrtc.org Use RTC_HAS_MSAN to check for MSan builds. 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: chromium:1155459 Tbr: webrtc-chromium-sheriffs-robots@google.com Change-Id: I71ccb08b12368aa4c81d113f911ace63db0a12cf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2574724Reviewed-by:
-
Ryan Heise authored
Bug: chromium:1138593 Change-Id: Ie821d672487612933865610bfba722faf1bc6e6e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2573679Reviewed-by:
-
Abigail Klein authored
in SODAInstallerImplChromeOS. This fixes an overlooked nit whereby the SODAInstallerImpl was overriding a non-virtual destructor in its parent class, and the SODAInstallerImplChromeOS was not. Bug: 1055150 Change-Id: If039f7e046201bcc776f493338c0bffcea365a04 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2572942Reviewed-by:
Dominic Mazzoni <dmazzoni@chromium.org> Commit-Queue: Abigail Klein <abigailbklein@google.com> Cr-Commit-Position: refs/heads/master@{#833782}
-
Patrick Noland authored
This change moves the implementation of revertChanges to LocationBarMediator. It also passes the call to selectAll directly to the UrlBarCoordinator, and implements the OnKeyListener interface in LocationBarCoordinator instead of LocationBarLayout. The latter change is because this listener needs to be able to call revertChanges, which LocationBarLayout can no longer do. Bug: 1147581 Change-Id: I5df4ec31997ed072f0d6040b7d96e595471ec741 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2552758 Commit-Queue: Patrick Noland <pnoland@chromium.org> Reviewed-by:
Filip Gorski <fgorski@chromium.org> Cr-Commit-Position: refs/heads/master@{#833781}
-
Michael Lippautz authored
Bug: 1056170 Change-Id: I0c3420dfb6d0fd978a25aee28c95b412d91a3bd3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2572844 Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Kentaro Hara <haraken@chromium.org> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Auto-Submit: Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/master@{#833780}
-
chromium-autoroll authored
https://dawn.googlesource.com/dawn.git/+log/ab5821d0166f..f31b78e90e1e 2020-12-04 senorblanco@chromium.org Enable all remaining end2end tests on OpenGL ES backend. 2020-12-04 bclayton@google.com Remove legacy tint::transform API codepaths If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/dawn-chromium-autoroll Please CC dsinclair@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:dawn-linux-x64-deps-rel;luci.chromium.try:dawn-mac-x64-deps-rel;luci.chromium.try:dawn-win10-x64-deps-rel;luci.chromium.try:dawn-win10-x86-deps-rel Bug: None Tbr: dsinclair@google.com Change-Id: I8463b72d5670ffca8e141fd385c26f233b5b7760 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2574719Reviewed-by:
-
Robert Sesek authored
Bug: 1153883 Change-Id: Ieb2ee69ba93e0469cbe307dfb1f12687a0a1a702 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2572379 Commit-Queue: Robert Sesek <rsesek@chromium.org> Commit-Queue: Nico Weber <thakis@chromium.org> Reviewed-by:
-
chromium-autoroll authored
https://chromium.googlesource.com/catapult.git/+log/d1cf5db4152d..88efddc6a162 2020-12-04 ulan@chromium.org Implement the unified V8 and CppGC metric computation If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/catapult-autoroll Please CC wenbinzhang@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:chromeos-kevin-rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel Bug: chromium:1154636 Tbr: wenbinzhang@google.com Change-Id: I08a55a2e486c3898a9f9dacd3ec377f3fc020df6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2574425 Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Reviewed-by:
-
chromium-autoroll authored
Roll ChromeOS Atom AFDO profile from 89-4324.9-1606733211-benchmark-89.0.4342.0-r1 to 89-4324.9-1606733211-benchmark-89.0.4343.0-r1 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/cros-afdo-atom-chromium Please CC c-compiler-chrome@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: c-compiler-chrome@google.com Change-Id: I1aa38e3eb726be18675f14cb1f6a3409118a993d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2574726Reviewed-by:
-
Andrew Grieve authored
Plus minor tweaks: * --build-build-config -> --build * Fix --inner name mangling not removing __test_apk Bug: None Change-Id: I3cb77e9f12306d80cb1e4e2d3b2466c489f5a155 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2574656 Commit-Queue: Andrew Grieve <agrieve@chromium.org> Reviewed-by:
Sam Maier <smaier@chromium.org> Cr-Commit-Position: refs/heads/master@{#833775}
-
Chris Buquicchio authored
CFMs currently rely on this behavior. It was removed in https://chromium-review.googlesource.com/c/chromium/src/+/2306918. BUG=b:167805373 TEST='Locally checked order of video capture devices on CFM devices.' Change-Id: I2dc348a88b6821e7cac257ecf9710ec1c5247942 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2573196Reviewed-by:
Guido Urdaneta <guidou@chromium.org> Reviewed-by:
-
Andre Le authored
Add MultiDevice.SecureChannel.Nearby.MessageAction Bug: 1106937, 1150634 Change-Id: I91bc2801c9e35b8b041b4d4c39780ed4d9f32e53 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2569117 Commit-Queue: Andre Le <leandre@chromium.org> Reviewed-by:
Robert Kaplow <rkaplow@chromium.org> Reviewed-by:
-
Chris Hamilton authored
Catan team still uses these, and will be monitoring them in some upcoming experiments. Change-Id: Id6cda68e5b47cd36b2249bea8cb04bce3dcc2116 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2573461Reviewed-by:
Jesse Doherty <jwd@chromium.org> Reviewed-by:
François Doray <fdoray@chromium.org> Reviewed-by:
Alexander Timin <altimin@chromium.org> Commit-Queue: Chris Hamilton <chrisha@chromium.org> Cr-Commit-Position: refs/heads/master@{#833772}
-
Benoit Lize authored
Bug: 998048 Change-Id: Ie18db70f78188e4541aa4d5a0f44da2ce166524e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2569664 Commit-Queue: Benoit L <lizeb@chromium.org> Reviewed-by:
Bartek Nowierski <bartekn@chromium.org> Cr-Commit-Position: refs/heads/master@{#833771}
-
chromium-autoroll authored
Roll ChromeOS Bigcore AFDO profile from 89-4324.9-1606737320-benchmark-89.0.4342.0-r1 to 89-4324.9-1606737320-benchmark-89.0.4343.0-r1 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/cros-afdo-bigcore-chromium Please CC c-compiler-chrome@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: c-compiler-chrome@google.com Change-Id: I2d1150fa7ab69793c68be4ef174795c86527d7e5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2574727Reviewed-by:
-
Keren Zhu authored
A comment-friendly doc version is available at http://doc/1jBT-aqlwb4I7_OH6xC4yX5sn8zlZTOXbfYiU4coG0yQ Bug: None Change-Id: I135f0ba144c437af6bd366625e8cc989c246d7a6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2571803Reviewed-by:
Robert Liao <robliao@chromium.org> Commit-Queue: Robert Liao <robliao@chromium.org> Cr-Commit-Position: refs/heads/master@{#833769}
-
Brandon Wylie authored
Bug: 1123209 Change-Id: Id5d25db3cb60c2bac266ea84a6892475c467fedc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2573135Reviewed-by:
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/ab473c14..61f3e614 Please follow these instructions for assigning/CC'ing issues: https://v8.dev/docs/triage-issues Please close rolling in case of a roll revert: https://v8-roll.appspot.com/ This only works with a Google account. CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux-blink-rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:mac_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:win_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel TBR=hablich@chromium.org,vahl@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com Change-Id: Iaa861c5fc9f32cc910b0f628cd7439754c7cde8c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2572910Reviewed-by:
v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Commit-Queue: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#833767}
-
