- 02 Jun, 2020 40 commits
-
-
Benoit Lize authored
With some configurations, DiskDataAllocator triggers DCHECK()s: - Serializing an empty file is supported by Mojo, but discouraged - Background writes need to be explicitly annotated in blink This also adds a threading restriction exception for reads on the main thread. This wasn't hit because a write always happen before a read, but is required as well. This is expected, and is covered by metrics to ensure this is not an issue in practice. Bug: 1087862, 1029320 Change-Id: I41f5fca2b9b371a6ad7b9988ba3914543bd44d6d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2222580 Commit-Queue: Benoit L <lizeb@chromium.org> Reviewed-by:
Kinuko Yasuda <kinuko@chromium.org> Reviewed-by:
Gabriel Charette <gab@chromium.org> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Cr-Commit-Position: refs/heads/master@{#774278}
-
David Bokan authored
The |is_composited| was added to ScrollNodes in https://crrev.com/6ce0a16d1e0 as a way to tell which ScrollNodes are able to scroll directly on the compositor by changing the transform tree. When the scroll unification flag is turned on, scroll nodes without this bit set avoid mutating the transform tree and instead rely on a commit from the main thread for a scroll to be realized. PropertyTreeBuilder creates property trees for the UI compositor and some tests based on the layer tree. The CL above did not update this method of tree generation to set this bit. Since the nodes are built from layers, all nodes should be considered composited in this case. This change fixes tests when the scroll unification flag is turned on. Bug: 1086625 Change-Id: I3a3552a5c17f1f69e038657c1f267b2a61f7a070 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2222892 Commit-Queue: David Bokan <bokan@chromium.org> Reviewed-by:
Philip Rogers <pdr@chromium.org> Cr-Commit-Position: refs/heads/master@{#774277}
-
Jarryd authored
Change-Id: I2c7df80c038104c8c19e9d70e2b75ca0d8acedfa Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2225837 Auto-Submit: Jarryd Goodman <jarrydg@chromium.org> Commit-Queue: Darwin Huang <huangdarwin@chromium.org> Reviewed-by:
Darwin Huang <huangdarwin@chromium.org> Cr-Commit-Position: refs/heads/master@{#774276}
-
Mark Yacoub authored
Encapsulate {id, mode and origin} into a single struct that is passed through Mojom. The intention is to use a vector of the structs of the multiple displays that will be configured together. BUG=1082882 TEST=no changes in modesetting any device Change-Id: I932b7bae16670a3eff55f2666ce1096c8a4b8a27 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2202876Reviewed-by:Robert Sesek <rsesek@chromium.org> Reviewed-by:
Daniel Nicoara <dnicoara@chromium.org> Commit-Queue: Mark Yacoub <markyacoub@google.com> Cr-Commit-Position: refs/heads/master@{#774275}
-
Mounir Lamouri authored
Don't keep a copy of the player id in the controller. Simplifies the logic. Bug: None Change-Id: Ia9f4be60f8affd4329f788a59597b06a2cb521ad Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2196935Reviewed-by:
Becca Hughes <beccahughes@chromium.org> Commit-Queue: Mounir Lamouri <mlamouri@chromium.org> Cr-Commit-Position: refs/heads/master@{#774274}
-
Ali Juma authored
This adds some integration tests for Safe Browsing, verifying that error pages are displayed when navigating to an unsafe URL, the "Back to safety" and "Details" buttons work as expected, the proceed link dismisses the error page and loads the unsafe site. Change-Id: Ife93280ae78562626d779d28c432c76c3c582bc0 Bug: 1087390 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2222694 Commit-Queue: Ali Juma <ajuma@chromium.org> Reviewed-by:
Kurt Horimoto <kkhorimoto@chromium.org> Reviewed-by:
Eugene But <eugenebut@chromium.org> Cr-Commit-Position: refs/heads/master@{#774273}
-
Jian Li authored
This allows Feed v2 surface UI being rendered in NTP. All the interaction with Feed v2 surface is now wrapped under Stream API, as in FeedStream class. According to android-binary-size trybot, this increases the binary sizes by ~2.6kb. The increase comes from exposing Feed v2 UI and there isn't much we can do to reduce them. Bug: 1044139 Binary-Size: Size increase is unavoidable (see above) Change-Id: I0ec53959867b8842f9f546ad42c22f05d819fa1e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2224154Reviewed-by:
Dan H <harringtond@chromium.org> Reviewed-by:
Cathy Li <chili@chromium.org> Commit-Queue: Jian Li <jianli@chromium.org> Cr-Commit-Position: refs/heads/master@{#774272}
-
Brandon Wylie authored
Bug: 1086345 Change-Id: Ia5ca55590795a9ecd4586787520458d98ac1876f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2225823 Commit-Queue: Brandon Wylie <wylieb@chromium.org> Reviewed-by:
Theresa <twellington@chromium.org> Cr-Commit-Position: refs/heads/master@{#774271}
-
Yao Xiao authored
Bug: 1062736 Change-Id: Ib6dae46fc0fffc06376f2f792daea6de7394ecfc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2219012 Commit-Queue: Yao Xiao <yaoxia@chromium.org> Reviewed-by:
Marc Treib <treib@chromium.org> Cr-Commit-Position: refs/heads/master@{#774270}
-
Tommy C. Li authored
This CL adds the accessibility messages for popup headers. It also moves the logic out of OmniboxResultView into OmniboxPopupModel. We had to do this, since we now have headers that are not encapsulated within OmniboxResultView. Moreover, we've had crashes with one View reaching into other Views. Our new design going forward is to have Views be relatively independent while coordinating shared business logic though the OmniboxPopupModel. One more thing: This CL will also make VoiceOver enunciate the accessibility labels for all focused-button SelectionStates, not just BUTTON_FOCUSED. We need this because we now have a sundry of focused button states. This CL is not a complete solution, we still have a few more things to do, that will have to be in separate CLs: - Don't update the temporary text when tabbing INTO a Header. - Update the temporary text when tabbing OUT of a Header. - Provide the proper 'Selected' accessibility event when focusing the header button. We don't do this yet. Bug: 1078183, 1052522 Change-Id: I94108ca5a527754c0087f9a06f1aeb5d53dc57e9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2220348Reviewed-by:
Justin Donnelly <jdonnelly@chromium.org> Commit-Queue: Tommy Li <tommycli@chromium.org> Cr-Commit-Position: refs/heads/master@{#774269}
-
Andrew Grieve authored
Similar to enable_proguard_obfuscation, provides a global toggle to disable path renaming and resource id coalescing. Useful for APK analysis tools that don't support mapping files. Bug: None Change-Id: I9d6b90a9f452e5c87852ecacdfa0def103ddacd4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2225362 Auto-Submit: Andrew Grieve <agrieve@chromium.org> Reviewed-by:
Mohamed Heikal <mheikal@chromium.org> Commit-Queue: Mohamed Heikal <mheikal@chromium.org> Cr-Commit-Position: refs/heads/master@{#774268}
-
Matthew Wang authored
Network.Shill.WiFi.{Ap80211rSupport, BSSTransitionManagementSupport, SessionLength, RoamComplete, RoamTime} Bug: 1089039,1089042,1089801,1089802,1089803 Change-Id: I12bd488d3fec7c195799287dd7c6db7167385616 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2225391Reviewed-by:Alexei Svitkine <asvitkine@chromium.org> Commit-Queue: Alexei Svitkine <asvitkine@chromium.org> Cr-Commit-Position: refs/heads/master@{#774267}
-
Shengfa Lin authored
document.activeElement could return body when no element has focus. When user first navigate to url or switch frame, we don't want to treat this body as focus. Therefore, we will check document.hasFocus() first. Bug: chromedriver:3502,b/157759309 Change-Id: I87e649423a6fde55a7b8a273c3500787045edac3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2225521Reviewed-by:
John Chen <johnchen@chromium.org> Commit-Queue: Shengfa Lin <shengfa@google.com> Cr-Commit-Position: refs/heads/master@{#774266}
-
Dominic Mazzoni authored
This reverts commit 62ff616d. Reason for revert: Both of these are failing on MSAN: SigninReauthViewControllerBrowserTest.CancelReauthDialog SigninReauthViewControllerBrowserTest.ConfirmReauthDialog Original change's description: > [signin] Add reauth browser tests with a fake Gaia page > > This CL adds a new set of tests for the reauth dialog. These tests > check interactions with a Gaia Reauth endpoint that is imitated through > an EmbeddedTestServer. > > The main "embedded/xreauth/chrome" endpoint operates in two modes: > - In the default mode, the endpoint redirects to the "challenge" URL > whose response can be controlled within the test by a > ControllableHttpResponse. > - If the "?done" query is present, the endpoint returns the > HTTP_NO_CONTENT response that signifies a successful reauth. > > The CL also extracts common test code into test suite functions to > reduce the code duplication and make the tests code more readable. > > Bug: 1045515 > Change-Id: I89d4aac57ef25168def1341fb63b1a7498dcfa0f > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2225396 > Commit-Queue: Alex Ilin <alexilin@chromium.org> > Reviewed-by: David Roger <droger@chromium.org> > Cr-Commit-Position: refs/heads/master@{#774205} TBR=droger@chromium.org,alexilin@chromium.org Change-Id: I9e322b00bb98f9394b81fda2a0e62bf5db5cd9e9 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 1045515, 1090451 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2225852Reviewed-by:
Dominic Mazzoni <dmazzoni@chromium.org> Commit-Queue: Dominic Mazzoni <dmazzoni@chromium.org> Cr-Commit-Position: refs/heads/master@{#774265}
-
Kevin Babbitt authored
At window close, we make an outbound call to UI Automation to signal it that objects associated with that window are no longer valid and can be cleaned up. If that cleanup call happens to be the first call into UIA during the lifetime of the browser process - because UIA has not otherwise been used - it can trigger UIA to initialize itself, which can result in an outbound COM call from the browser main thread, which can trigger pumping of messages back into our window. That can lead to bad behavior since objects are already partially torn down at that point. The fix is for each message handler to keep track of whether it has returned any UIA objects and only make the cleanup call if so. Bug: 1087553 Change-Id: Ibf55df4d2e531fb8c4e404ede80e17833ff61543 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2220473 Commit-Queue: Kevin Babbitt <kbabbitt@microsoft.com> Reviewed-by:
Scott Violet <sky@chromium.org> Reviewed-by:
-
Alex Gough authored
Prelude to removal of WithSandboxType API. See linked bug for rationale. Does not change behavior. Tests: browser_tests PrintBrowserTest.* Bug: 1065087 Change-Id: Idaf185273813b4fc75cad3897f0507569135134d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2202423 Commit-Queue: Alex Gough <ajgo@chromium.org> Reviewed-by:
Mustafa Emre Acer <meacer@chromium.org> Reviewed-by:
Lei Zhang <thestig@chromium.org> Cr-Commit-Position: refs/heads/master@{#774263}
-
Junbo Ke authored
This change is generated by the automated script. Bug: internal b/152051045 Test: None Change-Id: I831e12e625e667424fc1869351297a864cc6ae7d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2225738 Commit-Queue: Junbo Ke <juke@chromium.org> Commit-Queue: Alexei Svitkine <asvitkine@chromium.org> Auto-Submit: Junbo Ke <juke@chromium.org> Reviewed-by:
Brian White <bcwhite@chromium.org> Reviewed-by:
Luke Halliwell (slow) <halliwell@chromium.org> Cr-Commit-Position: refs/heads/master@{#774262}
-
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/perfetto-trace-processor-linux-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: I0afcb72086f3d2deffedb3156b62ebcc2922c8e3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2226915Reviewed-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@{#774261}
-
Moe Ahmadi authored
Change-Id: Iba0d2ad906701e78b8dbd28730c7653178aef55c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2224025Reviewed-by:
-
Roman Sorokin authored
Fixed: 1089620 Change-Id: I49bbf4b016be9a8a82b5d8c5b0bccfe43d0f906a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2226812Reviewed-by:
-
Varun Khaneja authored
BYPASS_POLICY_COMPATIBILITY_CHECK=Removing the 'future' value since the policy launched in M83. Bug: 1090384, 1066371 Change-Id: Id4f62087f5995f3c2c12e86ec44c17c9d093c8ea Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2226911 Commit-Queue: Pavol Marko <pmarko@chromium.org> Reviewed-by:
Pavol Marko <pmarko@chromium.org> Reviewed-by:
Greg Thompson <grt@chromium.org> Auto-Submit: Varun Khaneja <vakh@chromium.org> Cr-Commit-Position: refs/heads/master@{#774258}
-
danakj authored
Re-enable external/wpt/html/user-activation/message-event-activation-api-iframe-cross-origin.sub.tentative.html The test was supposed to fail with site isolation but it is passing now. R=bokan@chromium.org Bug: 895001 Change-Id: Ic2f0dc0f39c75424dfcae74468f1570b54ba9fd6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2220879 Commit-Queue: danakj <danakj@chromium.org> Auto-Submit: danakj <danakj@chromium.org> Reviewed-by:
David Bokan <bokan@chromium.org> Cr-Commit-Position: refs/heads/master@{#774257}
-
Renjie Tang authored
Mark port migration as failed but do not close QUIC connection when STATELESS_RESET is received from the probing path. Bug: b/156662307 Change-Id: I3ff86c67f3c2c1d2b88c8742273767dd2ea58273 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2212460 Commit-Queue: Renjie Tang <renjietang@chromium.org> Reviewed-by:
Zhongyi Shi <zhongyi@chromium.org> Reviewed-by:
Ilya Sherman <isherman@chromium.org> Cr-Commit-Position: refs/heads/master@{#774256}
-
Dominic Mazzoni authored
This reverts commit a8ba3523. Reason for revert: MediaFeedsBrowserTest.ResetMediaFeed_ClearSiteDataHeader_Cache failing here: https://ci.chromium.org/p/chrome/builders/ci/linux-chromeos-chrome Original change's description: > [Media Feeds] Add Clear-Site-Data tests > > Add tests for clear-site-data which should > reset the media feed. > > BUG=1053599 > > Change-Id: If539e178aad9c04c3891930420f9f7b8cbbe7a79 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2225231 > Reviewed-by: Tommy Steimel <steimel@chromium.org> > Commit-Queue: Becca Hughes <beccahughes@chromium.org> > Cr-Commit-Position: refs/heads/master@{#774168} TBR=beccahughes@chromium.org,steimel@chromium.org Change-Id: Ic61ee2bb47bfcc3ae1ac33442864754cd0bd679b No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 1053599, 1090444 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2225851Reviewed-by:
-
Wenzhao Zang authored
Bug: internal: 157928107 Test: on device Merge-With: eureka-internal/406533 Change-Id: I122ee50240328ddf7b070aad5c18fc9698a93292 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2226087Reviewed-by:
Kenneth MacKay <kmackay@chromium.org> Commit-Queue: Wenzhao (Colin) Zang <wzang@chromium.org> Cr-Commit-Position: refs/heads/master@{#774254}
-
Arthur Wang authored
R=bsheedy@chromium.org,harringtond@chromium.org Bug: 1060399 Change-Id: Ifb06c6a94a51a6b1a2815bf94fa8f5a53dec1db8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2219525Reviewed-by:
Haiyang Pan <hypan@google.com> Reviewed-by:
Robbie Iannucci <iannucci@chromium.org> Reviewed-by:
Brian Sheedy <bsheedy@chromium.org> Commit-Queue: Arthur Wang <wuwang@chromium.org> Cr-Commit-Position: refs/heads/master@{#774253}
-
mark a. foltz authored
This removes logging statements from c/b/media/router. Logging statements should be for temporary debugging and not a permanent part of the code base. Change-Id: I677b95e37175ce6cd379c9408af2f3641c4311f2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2222886 Commit-Queue: mark a. foltz <mfoltz@chromium.org> Reviewed-by:
Takumi Fujimoto <takumif@chromium.org> Cr-Commit-Position: refs/heads/master@{#774252}
-
Robert Ogden authored
Bug: 1023482 Change-Id: Ia17371bdc6fd85ab950fb76ef3ce6eb1ab9d5883 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2226314 Commit-Queue: Robert Ogden <robertogden@chromium.org> Commit-Queue: Tarun Bansal <tbansal@chromium.org> Reviewed-by:
Tarun Bansal <tbansal@chromium.org> Auto-Submit: Robert Ogden <robertogden@chromium.org> Cr-Commit-Position: refs/heads/master@{#774251}
-
Jon Mann authored
This saves additional metadata when a wi-fi network has a bad password. Once a network has had a successful connection this will be cleared and further bad-password errors will be ignored unless the saved password is changed. This is accessible from a new public method in order to be used to avoid syncing networks with a bad password. Bug: 966270 Change-Id: I084bc46da7302e93644484bf34cebf39ec8b1de2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2220658Reviewed-by:
Kyle Horimoto <khorimoto@chromium.org> Reviewed-by:
James Vecore <vecore@google.com> Commit-Queue: Jon Mann <jonmann@chromium.org> Cr-Commit-Position: refs/heads/master@{#774250}
-
Nico Weber authored
Ran `./tools/clang/scripts/upload_revision.py a6ae333a0c23fc9b0783ca45e2676abac00c6723`. Bug: 1090418 Cq-Include-Trybots: chromium/try:mac_chromium_asan_rel_ng Cq-Include-Trybots: chromium/try:linux_chromium_cfi_rel_ng Cq-Include-Trybots: chromium/try:linux_chromium_chromeos_asan_rel_ng Cq-Include-Trybots: chromium/try:linux_chromium_msan_rel_ng Cq-Include-Trybots: chromium/try:linux_chromium_chromeos_msan_rel_ng Cq-Include-Trybots: chromium/try:linux-chromeos-dbg,win-asan Cq-Include-Trybots: chromium/try:chromeos-amd64-generic-cfi-thin-lto-rel Cq-Include-Trybots: chromium/try:linux_chromium_compile_dbg_32_ng Cq-Include-Trybots: chromium/try:win7-rel,win-angle-deqp-rel-32 Cq-Include-Trybots: chromium/try:win-angle-deqp-rel-64 Cq-Include-Trybots: chromium/try:dawn-win10-x86-deps-rel Cq-Include-Trybots: chrome/try:ipad-device Cq-Include-Trybots: chrome/try:linux-chromeos-chrome Cq-Include-Trybots: chrome/try:win-chrome,win64-chrome,mac-chrome Change-Id: Ib0230c311c8048633cc67caeaf18c10db81c1e09 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2226277 Commit-Queue: Nico Weber <thakis@chromium.org> Reviewed-by:
Hans Wennborg <hans@chromium.org> Cr-Commit-Position: refs/heads/master@{#774249}
-
Andy Paicu authored
Bug: 1016730 Change-Id: Ic376f168d5538366026224d7bc3514d84795261c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2218778Reviewed-by:
Dominick Ng <dominickn@chromium.org> Commit-Queue: Andy Paicu <andypaicu@chromium.org> Cr-Commit-Position: refs/heads/master@{#774248}
-
Dominic Battre authored
This CL extends, resurrects and ends the life-time of some Autofill histograms. I have also made sure via ``` for p in mathp sebsg rogerm wuandy parastoog ftirelo gogerald \ seblalancette vincb tmartino estade mahmadi; do xmllint --xpath "//histogram[not(./obsolete) and contains(@name, 'Autofill')][./owner[contains(text(), '$p')]]" histograms.xml | grep "<histogram"; done ``` that no previous owners remain as histogram owners so that we get expiration events in the future. Bug: 1088598,1088603e,1088604,1088607,1088608,1088609,1088610,1088611,1088612,1088624,1088625,1088626,1088627,1088637,1088638,1089241,1089683,1089684,1089685,1089891,1089892,1089893 Change-Id: I25468642d019de448b8a5b027805db2882c20ac7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2224865Reviewed-by:Matthias Körber <koerber@google.com> Reviewed-by:
-
Michael Ludwig authored
Bug: 1087413 Change-Id: If59a27697f3e2b3aa0049c56f9e7f28bad6e9437 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2220877 Auto-Submit: Michael Ludwig <michaelludwig@google.com> Reviewed-by:
Jonathan Ross <jonross@chromium.org> Commit-Queue: Jonathan Ross <jonross@chromium.org> Cr-Commit-Position: refs/heads/master@{#774246}
-
danakj authored
It used to fail with site isolation but it no longer does. R=foolip@chromium.org Bug: 1007228 Change-Id: I69ba7539d8b08cad2185aecdb22df000df97bec4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2223080Reviewed-by:
Philip Jägenstedt <foolip@chromium.org> Commit-Queue: danakj <danakj@chromium.org> Cr-Commit-Position: refs/heads/master@{#774245}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/dad4850e5d7a..fc0efae149cb 2020-06-02 primiano@google.com Merge "ui/tp: fix race in trace-processor --httpd and improve performance" If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/perfetto-chromium-autoroll 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 Cq-Include-Trybots: luci.chromium.try:linux-perfetto-rel Bug: None Tbr: perfetto-bugs@google.com Change-Id: I122a71b5a4374971fd99f7a0d7fb338d543d8927 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2226886Reviewed-by:
-
Domenic Denicola authored
Bug: 1042415 Change-Id: I2acd2fea79a12e1f60eb9a0114abcf61630e269a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2202512 Commit-Queue: Domenic Denicola <domenic@chromium.org> Reviewed-by:
James MacLean <wjmaclean@chromium.org> Cr-Commit-Position: refs/heads/master@{#774243}
-
Xida Chen authored
Right now we report throughput to UKM system at: 1. 5 seconds after a sequence starts. 2. Every 500 seconds after that as long as the sequence lasts. The problem is that in many cases users stay on a page less than 500 seconds, and thus we would only get the report for the first 5 seconds, which can be heavily dominated by the page loading period. This CL changes it such that we record the throughput every 5 seconds, and then report the median throughput to the UKM when the page shuts down. At this moment, this applies to the kUniversal tracker only, which tracks all kinds of frame productions. For other types of trackers, such as the trackers tracks animation/scroll, etc, this change will be applied later. Bug: 1040634 Change-Id: I452e16c45187393f29abf1bdf3650a4e5ffb45fc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2112953Reviewed-by:
Dmitry Gozman <dgozman@chromium.org> Reviewed-by:
Ken Buchanan <kenrb@chromium.org> Reviewed-by:
Bryan McQuade <bmcquade@chromium.org> Reviewed-by:
Stephen Chenney <schenney@chromium.org> Reviewed-by:
danakj <danakj@chromium.org> Commit-Queue: Xida Chen <xidachen@chromium.org> Cr-Commit-Position: refs/heads/master@{#774242}
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/113bf7f2..f0122481 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: Ib6d01b70017846e6ab09ce2ef3c080d1d3c8c33a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2225048Reviewed-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@{#774241}
-
Sean Kau authored
The printer filters which were provided through component download have been moved into the rootfs. As such, remove the code responsible for downloading them from Chrome. Bug: 1056364 Change-Id: Ia9bd06b0321326880bace28da7e61554eb877c94 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2146052Reviewed-by:
Piotr Pawliczek <pawliczek@chromium.org> Commit-Queue: Piotr Pawliczek <pawliczek@chromium.org> Auto-Submit: Sean Kau <skau@chromium.org> Cr-Commit-Position: refs/heads/master@{#774240}
-
Sven Zheng authored
With this feature, test can post link to Milo UI. The work for getting gtest supports links is in this design doc: go/gtest-supports-artifacts Bug: 1028400 Change-Id: I5be1699932c5f5304c1ec3a44abbf70829ae394b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1940553 Commit-Queue: Sven Zheng <svenzheng@chromium.org> Reviewed-by:
-
