- 14 Apr, 2019 15 commits
-
-
Robert Ogden authored
GetNewPageId() is only called in one place now, GetOrCreateSLPInfo, and this value is used for all restarted navigations, persisted by the Info. Bug: 952523 Change-Id: Id9cdc8aead427c6cfefabd195db10ed251c6f787 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1567101Reviewed-by:
Ryan Sturm <ryansturm@chromium.org> Commit-Queue: Robert Ogden <robertogden@chromium.org> Cr-Commit-Position: refs/heads/master@{#650642}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/2221eb4885ad..4f62e7ac6bde Created with: gclient setdep -r src-internal@4f62e7ac6bde The AutoRoll server is located here: https://autoroll-internal.skia.org/r/src-internal-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.chrome.try:linux-chromeos-chrome TBR=anthonyvd@chromium.org,andypaicu@chromium.org,aboxhall@chromium.org,caseq@chromium.org Change-Id: Ib9f045be36109d0bf752fb1b52400a8683631066 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1566484Reviewed-by:
chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#650641}
-
Adam Langley authored
This change causes the human-readable form of the CBOR errors to be included in log messages and also logs messages from parse errors in GetInfo requests (which are handled differently). This would have been helpful when figuring out why the Solo Key wasn't working as a CTAP2 device. Change-Id: I11f241a740a50a4f0b1edb45e4d535a193561a93 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1565088 Commit-Queue: Adam Langley <agl@chromium.org> Reviewed-by:
Martin Kreichgauer <martinkr@google.com> Cr-Commit-Position: refs/heads/master@{#650640}
-
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: Id6df0fc1f882b0c27b553836538e6856618e8e61 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1566483Reviewed-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@{#650639}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/d3b72ea43c8a..2221eb4885ad Created with: gclient setdep -r src-internal@2221eb4885ad The AutoRoll server is located here: https://autoroll-internal.skia.org/r/src-internal-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.chrome.try:linux-chromeos-chrome TBR=anthonyvd@chromium.org,andypaicu@chromium.org,aboxhall@chromium.org,caseq@chromium.org Change-Id: I83b7065ed311befae1f6ed948bc56d727808c340 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1566979Reviewed-by:
chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#650638}
-
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: I1c2979a8ea0945b9d392fd3d1a3d6512c056f790 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1566814Reviewed-by:
chrome-release-bot@chromium.org <chrome-release-bot@chromium.org> Cr-Commit-Position: refs/heads/master@{#650637}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromiumos/chromite.git/+log/1f05aec37ff8..d7ba750e8dd8 git log 1f05aec37ff8..d7ba750e8dd8 --date=short --no-merges --format='%ad %ae %s' 2019-04-14 dhanyaganesh@chromium.org Migrate from CIDB to Buildbucket for read ops Created with: gclient setdep -r src/third_party/chromite@d7ba750e8dd8 The AutoRoll server is located here: https://autoroll.skia.org/r/chromite-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:chromeos-kevin-rel TBR=chrome-os-gardeners@chromium.org Change-Id: I5447c51a5127334d19b0575eeae2be955d84425c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1567066Reviewed-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@{#650636}
-
Robert Ogden authored
This test is long overdue. There's a couple of early returns which I'll remove as the bugs are fixed. Bug: 952523 Change-Id: I81d945c168e25a12b661191435300436fdcd2154 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1567096Reviewed-by:
Ryan Sturm <ryansturm@chromium.org> Commit-Queue: Robert Ogden <robertogden@chromium.org> Cr-Commit-Position: refs/heads/master@{#650635}
-
Adam Langley authored
In addition to canceling operations at the device level, we also need to ensure that higher-level tasks stop creating new requests once canceled. This change is most evident when a Webauthn request results in an error (for example, because a credential isn't recognised). Previously, U2F authenticators would still flash. Now they'll stop within a few seconds. Also, in the request handlers, ensure that state changes are performed before cancelations in case the act of canceling triggers immediate callbacks. This is a preventative measure. Change-Id: I950ea9e705126d6ef1ea340000fe34090661c951 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1560512 Commit-Queue: Adam Langley <agl@chromium.org> Reviewed-by:
Martin Kreichgauer <martinkr@google.com> Cr-Commit-Position: refs/heads/master@{#650634}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/3fd871d1fa0a..d3b72ea43c8a Created with: gclient setdep -r src-internal@d3b72ea43c8a The AutoRoll server is located here: https://autoroll-internal.skia.org/r/src-internal-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.chrome.try:linux-chromeos-chrome TBR=anthonyvd@chromium.org,andypaicu@chromium.org,aboxhall@chromium.org,caseq@chromium.org Change-Id: I6617de58444e194d81de8b21a17e782bcf320246 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1565785Reviewed-by:
chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#650633}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromiumos/chromite.git/+log/b9d6ee1fce0c..1f05aec37ff8 git log b9d6ee1fce0c..1f05aec37ff8 --date=short --no-merges --format='%ad %ae %s' 2019-04-14 dhanyaganesh@chromium.org BuildStore: Separate the values in StageFailure initialization Created with: gclient setdep -r src/third_party/chromite@1f05aec37ff8 The AutoRoll server is located here: https://autoroll.skia.org/r/chromite-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:chromeos-kevin-rel TBR=chrome-os-gardeners@chromium.org Change-Id: Ib3c438bf1e92a70c67f100c6b8cacab7aa5f858a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1567064Reviewed-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@{#650632}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/33233a09fef8..12cf258193dc git log 33233a09fef8..12cf258193dc --date=short --no-merges --format='%ad %ae %s' 2019-04-14 herb@google.com Revert "Convert the CPU mask case to use prepareForDrawing" Created with: gclient setdep -r src/third_party/skia@12cf258193dc The AutoRoll server is located here: https://autoroll.skia.org/r/skia-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-blink-rel;luci.chromium.try:linux-chromeos-compile-dbg;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel TBR=herb@chromium.org Change-Id: I7fa9f0225d4b4270ff30813e7c1eb10c5e3d9615 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1565786Reviewed-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@{#650631}
-
John Williams authored
Change-Id: I6dd462281b83f0935b8e6af3a9b9a8d2605d5e44 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1554249 Commit-Queue: John Williams <jrw@chromium.org> Reviewed-by:
Takumi Fujimoto <takumif@chromium.org> Cr-Commit-Position: refs/heads/master@{#650630}
-
Adam Langley authored
Change-Id: Ibf22af9d53824ecc1762492543ed505898dc0e28 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1560511 Commit-Queue: Adam Langley <agl@chromium.org> Reviewed-by:
Martin Kreichgauer <martinkr@google.com> Cr-Commit-Position: refs/heads/master@{#650629}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/24fcaccc2247..3fd871d1fa0a Created with: gclient setdep -r src-internal@3fd871d1fa0a The AutoRoll server is located here: https://autoroll-internal.skia.org/r/src-internal-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.chrome.try:linux-chromeos-chrome TBR=anthonyvd@chromium.org,andypaicu@chromium.org,aboxhall@chromium.org,caseq@chromium.org Change-Id: Idde2d1920a22b8b33d1998c9b0e45372b905fbaa Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1565784Reviewed-by:
chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#650628}
-
- 13 Apr, 2019 25 commits
-
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/beea825f7b47..24fcaccc2247 Created with: gclient setdep -r src-internal@24fcaccc2247 The AutoRoll server is located here: https://autoroll-internal.skia.org/r/src-internal-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.chrome.try:linux-chromeos-chrome TBR=anthonyvd@chromium.org,andypaicu@chromium.org,aboxhall@chromium.org,caseq@chromium.org Change-Id: Idc8f3b90754d5d338f9d363f2c51e9e484665ed3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1565640Reviewed-by:
chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#650627}
-
Matthew Mourgos authored
AddPreTargetHandler() is called every time the app list is opened from closed state, but RemovePreTargetHandler() is called in the destructor which is not called when the app list is closed. This change properly calls RemovePreTargetHandler() when the app list is closed. Change-Id: Ic6f2556a3dabab43a7a7d2b63e81814b31058d60 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1566478 Commit-Queue: Matthew Mourgos <mmourgos@chromium.org> Reviewed-by:
Alex Newcomer <newcomer@chromium.org> Cr-Commit-Position: refs/heads/master@{#650626}
-
Adam Langley authored
Add warning message to UI when creating resident credentials as these credentials may have privacy implications. Also fix the oddity (and todo) that the RP ID for a request was passed via the transport observer, and didn't come from |AuthenticatorImpl|. Bug: 941120 Change-Id: Ib1d370d56c70dabdf69a94e4e472ed3addcfa900 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1559769 Commit-Queue: Adam Langley <agl@chromium.org> Reviewed-by:
Avi Drissman <avi@chromium.org> Reviewed-by:
Martin Kreichgauer <martinkr@google.com> Auto-Submit: Adam Langley <agl@chromium.org> Cr-Commit-Position: refs/heads/master@{#650625}
-
Xiaocheng Hu authored
This reverts commit cbdaf211. Reason for revert: Crash data already collected in 3763 and 3764 Original change's description: > Reland "[LayoutNG] Turn AssertLaidOut into a CHECK for LayoutNG" round 3 > > This reverts commit 33b5c673. > > Reason for revert: Adding production CHECKs to collect LayoutNG failures > for the 3rd time. > > Original change's description: > > Revert "Reland "[LayoutNG] Turn AssertLaidOut into a CHECK for LayoutNG"" > > > > This reverts commit 26ca019a. > > > > Reason for revert: Crash data already collected > > > > Original change's description: > > > Reland "[LayoutNG] Turn AssertLaidOut into a CHECK for LayoutNG" > > > > > > This reverts commit ec11fe81. > > > > > > Reason for revert: Try to catch more crashes in the wild after > > > a fix (crrev.com/c/1546713) has been landed. > > > > > > Original change's description: > > > > Revert "[LayoutNG] Turn AssertLaidOut into a CHECK for LayoutNG" > > > > > > > > This reverts commit bade42c5. > > > > > > > > Reason for revert: New crashes already caught. Reverting CHECKs > > > > back into DCHECKs to reduce noises. > > > > > > > > Original change's description: > > > > > [LayoutNG] Turn AssertLaidOut into a CHECK for LayoutNG > > > > > > > > > > Bug: 946004 > > > > > Change-Id: I9e2aa69a32f7a0373196d57e629256dbc7d78d2a > > > > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1540305 > > > > > Reviewed-by: Koji Ishii <kojii@chromium.org> > > > > > Reviewed-by: Emil A Eklund <eae@chromium.org> > > > > > Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org> > > > > > Cr-Commit-Position: refs/heads/master@{#644907} > > > > > > > > TBR=eae@chromium.org,kojii@chromium.org,xiaochengh@chromium.org > > > > > > > > Change-Id: I15fb43370f58757e09e7b7abc7c40d4af4a6101a > > > > No-Presubmit: true > > > > No-Tree-Checks: true > > > > No-Try: true > > > > Bug: 946004 > > > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1544156 > > > > Reviewed-by: Xiaocheng Hu <xiaochengh@chromium.org> > > > > Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org> > > > > Cr-Commit-Position: refs/heads/master@{#645407} > > > > > > TBR=eae@chromium.org,kojii@chromium.org,xiaochengh@chromium.org > > > > > > # Not skipping CQ checks because original CL landed > 1 day ago. > > > > > > Bug: 946004 > > > Change-Id: Iccb8c2b998d28f659381c3f89a1686614600860c > > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1548248 > > > Reviewed-by: Xiaocheng Hu <xiaochengh@chromium.org> > > > Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org> > > > Cr-Commit-Position: refs/heads/master@{#646516} > > > > TBR=eae@chromium.org,kojii@chromium.org,xiaochengh@chromium.org > > > > # Not skipping CQ checks because original CL landed > 1 day ago. > > > > Bug: 946004 > > Change-Id: I9794539b39bc6a0053a7229b03bce7db402ecb5b > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1551440 > > Reviewed-by: Xiaocheng Hu <xiaochengh@chromium.org> > > Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org> > > Cr-Commit-Position: refs/heads/master@{#647418} > > TBR=eae@chromium.org,kojii@chromium.org,xiaochengh@chromium.org > > # Not skipping CQ checks because original CL landed > 1 day ago. > > Bug: 946004 > Change-Id: I973ccf65be78d4632f67b945614f1a4ee091134d > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1562500 > Reviewed-by: Xiaocheng Hu <xiaochengh@chromium.org> > Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org> > Cr-Commit-Position: refs/heads/master@{#649773} TBR=eae@chromium.org,kojii@chromium.org,xiaochengh@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 946004 Change-Id: If61d1cbfaeb6a445b8ceee193dba198978d2719c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1567130Reviewed-by:
Xiaocheng Hu <xiaochengh@chromium.org> Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org> Cr-Commit-Position: refs/heads/master@{#650624}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/869ed03f2b53..beea825f7b47 Created with: gclient setdep -r src-internal@beea825f7b47 The AutoRoll server is located here: https://autoroll-internal.skia.org/r/src-internal-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.chrome.try:linux-chromeos-chrome TBR=anthonyvd@chromium.org,andypaicu@chromium.org,aboxhall@chromium.org,caseq@chromium.org Change-Id: Iaddc44e30d8ccf9da8607eaf98875d806d20d2f6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1566554Reviewed-by:
chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#650623}
-
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: I2dc4b5ffe2d87a9e02fd0171ff73087302f213a5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1565639Reviewed-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@{#650622}
-
Findit authored
This reverts commit d4a2bb57. Reason for revert: Findit (https://goo.gl/kROfz5) identified CL at revision 650550 as the culprit for flakes in the build cycles as shown on: https://analysis.chromium.org/p/chromium/flake-portal/analysis/culprit?key=ag9zfmZpbmRpdC1mb3ItbWVyQwsSDEZsYWtlQ3VscHJpdCIxY2hyb21pdW0vZDRhMmJiNTc1N2YyMTNlNjhiMDFkMDMwYjEwOTM1YjFkNjQ3MzRhMAw Sample Failed Build: https://ci.chromium.org/buildbot/chromium.memory/Linux%20Chromium%20OS%20ASan%20LSan%20Tests%20%281%29/32724 Sample Failed Step: browser_tests Sample Flaky Test: LoginTest.GaiaAuthOffline Original change's description: > Chrome OS: Fix and re-enable LoginTest.GaiaAuthOffline test. > > Bug: 692364 > > Change-Id: Ib42c71c66094088d4c0644ba3b151700e110351f > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1565710 > Commit-Queue: Alexander Alekseev <alemate@chromium.org> > Reviewed-by: Toni Baržić <tbarzic@chromium.org> > Cr-Commit-Position: refs/heads/master@{#650550} Change-Id: I61dc50f4cc301438970d66f41555ed81e0cdf7b0 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 692364 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1567093 Cr-Commit-Position: refs/heads/master@{#650621}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/aad76fe386c5..869ed03f2b53 Created with: gclient setdep -r src-internal@869ed03f2b53 The AutoRoll server is located here: https://autoroll-internal.skia.org/r/src-internal-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.chrome.try:linux-chromeos-chrome TBR=anthonyvd@chromium.org,andypaicu@chromium.org,aboxhall@chromium.org,caseq@chromium.org Change-Id: Iffcc0f4198a7bcd49a2df8b301d703f60b87c0a4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1565638Reviewed-by:
chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#650620}
-
Charlie Reis authored
CL adapted from clamy@'s https://crrev.com/c/1565876. This is a partial revert of r638122 and r642275, plus a new test. This CL fixes a process leak that happens in navigations where the current renderer process is not live (crashed process or NTP). The mechanism is the following: 1) We want to navigate to a page in a FrameTreeNode where the current RFH is not live. This RFH has a SiteInstance with id 1, and a process with id 1. 2) We create a NavigationRequest, which takes as its starting SiteInstance the SiteInstance with id 1. 3) We call into RenderFrameHostManager::GetFrameHostForNavigation. It creates a speculative RFH, with a new SiteInstance with id 2, and a process with id 2. It commits this RFH immediately, since the current one is not live. This has the side effect of deleting process 1, however it does not delete SiteInstance 1 since it is referenced by the NavigationRequest. So SiteInstance 1 ends up associated with no RFH, and has no process either. 4) We create the NavigationHandle and call DidStartNavigation. One of the WebContentsObservers accesses NavigationHandle::GetStartingSiteInstance (which is SiteInstance 1), and asks it for its process (https://cs.chromium.org/chromium/src/chrome/browser/safe_browsing/safe_browsing_navigation_observer.cc?type=cs&q=safe_browsing::SafeBrowsingNavigationObserver::DidStartNavigation&g=0&l=185). Because the SiteInstance no longer has a process, we re-create a process with id 3 due to this call. 5) We finish the navigation and delete the last reference to SiteInstance 1. However, this does not delete process 3, which is not referenced anymore, and we leak the process. To fix the issue, this CL makes sure that the starting SiteInstance is captured just before creating the NavigationHandle, which is after a new RFH has been committed to replace the non-live current RFH. This way, the SiteInstance is properly linked to a RFH and it has a RenderProcessHost. Separately, we can ensure that unused processes will be cleaned up if GetProcess() is called unexpectedly. TBR=clamy@chromium.org TBR=jbudorick@chromium.org Bug: 949977 Change-Id: Ia84e238af0036822dd8c4cd47be5b497d0e7be3d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1566643 Commit-Queue: Charlie Reis <creis@chromium.org> Reviewed-by:
Charlie Reis <creis@chromium.org> Cr-Commit-Position: refs/heads/master@{#650619}
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/3af5c4c3547b..79e9f4b9c128 git log 3af5c4c3547b..79e9f4b9c128 --date=short --no-merges --format='%ad %ae %s' 2019-04-13 yvesg@webrtc.org Replace test::Statistics by webrtc::RunningStatistics. 2019-04-13 benwright@webrtc.org Remove HKDF implementation from WebRTC. 2019-04-13 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision 9ba7465f..8b06d91a (650428:650536) Created with: gclient setdep -r src/third_party/webrtc@79e9f4b9c128 The AutoRoll server is located here: https://autoroll.skia.org/r/webrtc-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. BUG=chromium:None TBR=webrtc-chromium-sheriffs-robots@google.com Change-Id: I2c47a1c8bbc975e1f9ca06aeeccebe81de4f0d1b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1565637Reviewed-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@{#650618}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/a15988358bf1..aad76fe386c5 Created with: gclient setdep -r src-internal@aad76fe386c5 The AutoRoll server is located here: https://autoroll-internal.skia.org/r/src-internal-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.chrome.try:linux-chromeos-chrome TBR=anthonyvd@chromium.org,andypaicu@chromium.org,aboxhall@chromium.org,caseq@chromium.org Change-Id: I0234193c618b4125c66d73898339b086d233cc84 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1566552Reviewed-by:
chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#650617}
-
chromium-autoroll authored
https://swiftshader.googlesource.com/SwiftShader.git/+log/e339d6c04e7b..db4f3dfd1960 git log e339d6c04e7b..db4f3dfd1960 --date=short --no-merges --format='%ad %ae %s' 2019-04-13 bclayton@google.com Revert "SprivShader: Replace hand-rolled bitreverse with LLVM intrinsic" Created with: gclient setdep -r src/third_party/swiftshader@db4f3dfd1960 The AutoRoll server is located here: https://autoroll.skia.org/r/swiftshader-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: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=swiftshader-team+autoroll@chromium.org Change-Id: I805b69425bba45a22e19156b87c30267b0f30c73 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1566553Reviewed-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@{#650616}
-
chromium-autoroll authored
https://swiftshader.googlesource.com/SwiftShader.git/+log/0179e5eb6537..e339d6c04e7b git log 0179e5eb6537..e339d6c04e7b --date=short --no-merges --format='%ad %ae %s' 2019-04-13 bclayton@google.com Revert "SprivShader: Replace hand-rolled bitcount with LLVM intrinsic" Created with: gclient setdep -r src/third_party/swiftshader@e339d6c04e7b The AutoRoll server is located here: https://autoroll.skia.org/r/swiftshader-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: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=swiftshader-team+autoroll@chromium.org Change-Id: I27dc1e26c7b4dfd3ff5d626eb76ac4f751162d07 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1566551Reviewed-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@{#650615}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/9abaded9b292..a15988358bf1 Created with: gclient setdep -r src-internal@a15988358bf1 The AutoRoll server is located here: https://autoroll-internal.skia.org/r/src-internal-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.chrome.try:linux-chromeos-chrome TBR=anthonyvd@chromium.org,andypaicu@chromium.org,aboxhall@chromium.org,caseq@chromium.org Change-Id: Ic713b77c3a62176c1b64dde9bb045c07eae6518a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1566588Reviewed-by:
chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#650614}
-
Darwin Huang authored
Bug: 949453, 950296 Change-Id: I875a580857d8de7557baa40de95e73e0a91689a3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1565682 Auto-Submit: Darwin Huang <huangdarwin@chromium.org> Reviewed-by:
Chris Mumford <cmumford@google.com> Commit-Queue: Darwin Huang <huangdarwin@chromium.org> Cr-Commit-Position: refs/heads/master@{#650613}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/487c1028fabb..9abaded9b292 Created with: gclient setdep -r src-internal@9abaded9b292 The AutoRoll server is located here: https://autoroll-internal.skia.org/r/src-internal-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.chrome.try:linux-chromeos-chrome TBR=anthonyvd@chromium.org,andypaicu@chromium.org,aboxhall@chromium.org,caseq@chromium.org Change-Id: I01c606a77076dcaec09933f28ba2d5103ea555cf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1566586Reviewed-by:
chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#650612}
-
chromium-autoroll authored
https://swiftshader.googlesource.com/SwiftShader.git/+log/73832434f8f3..0179e5eb6537 git log 73832434f8f3..0179e5eb6537 --date=short --no-merges --format='%ad %ae %s' 2019-04-13 bclayton@google.com SprivShader: Replace hand-rolled bitcount with LLVM intrinsic 2019-04-13 bclayton@google.com SprivShader: Replace hand-rolled bitreverse with LLVM intrinsic Created with: gclient setdep -r src/third_party/swiftshader@0179e5eb6537 The AutoRoll server is located here: https://autoroll.skia.org/r/swiftshader-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: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 BUG=chromium:b/126873455,chromium:b/126873455 TBR=swiftshader-team+autoroll@chromium.org Change-Id: I5137d2dbfe4dbf9b7c1ed9bc9ec5795e37ff780c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1566587Reviewed-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@{#650611}
-
Tao Bai authored
Fix a infinite loop caused by removing session in GetFrameContentCaptureData(). The previous test didn't uncover this issue, because it navigated to different domain, it acutally created new rfh, therefore, new ContentCaptureReceiver. Bug: 951567 Change-Id: Ib18806c23a0eb774ceb0adfd2a11eff52d5cc1a2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1565046Reviewed-by:
Changwan Ryu <changwan@chromium.org> Commit-Queue: Tao Bai <michaelbai@chromium.org> Cr-Commit-Position: refs/heads/master@{#650610}
-
chromium-autoroll authored
https://chromium.googlesource.com/catapult.git/+log/c789f4d537ae..b614c567e8b3 git log c789f4d537ae..b614c567e8b3 --date=short --no-merges --format='%ad %ae %s' 2019-04-13 benjhayden@chromium.org Migrate cp-dialog to es6 module. Created with: gclient setdep -r src/third_party/catapult@b614c567e8b3 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 BUG=chromium:950011 TBR=crouleau@chromium.org Change-Id: I4ad6274d050d83f045f261635a9692f211c0dae7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1566585Reviewed-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@{#650609}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/1f504bd31cbf..487c1028fabb Created with: gclient setdep -r src-internal@487c1028fabb The AutoRoll server is located here: https://autoroll-internal.skia.org/r/src-internal-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.chrome.try:linux-chromeos-chrome TBR=anthonyvd@chromium.org,andypaicu@chromium.org,aboxhall@chromium.org,caseq@chromium.org Change-Id: I362a2d41c978ffc2ccb0b3e595929001fd1e5622 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1566584Reviewed-by:
chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#650608}
-
chromium-autoroll authored
https://swiftshader.googlesource.com/SwiftShader.git/+log/17ecf2a67016..73832434f8f3 git log 17ecf2a67016..73832434f8f3 --date=short --no-merges --format='%ad %ae %s' 2019-04-13 sugoi@google.com Dynamic state implementation Created with: gclient setdep -r src/third_party/swiftshader@73832434f8f3 The AutoRoll server is located here: https://autoroll.skia.org/r/swiftshader-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: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=swiftshader-team+autoroll@chromium.org Change-Id: I77db1d52c99bfd9b9adb9b445f6ee50611af198c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1566583Reviewed-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@{#650607}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/69f54f8f0f22..33233a09fef8 git log 69f54f8f0f22..33233a09fef8 --date=short --no-merges --format='%ad %ae %s' 2019-04-13 herb@google.com Reland "Convert the CPU path case to use prepareForDrawing" Created with: gclient setdep -r src/third_party/skia@33233a09fef8 The AutoRoll server is located here: https://autoroll.skia.org/r/skia-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-blink-rel;luci.chromium.try:linux-chromeos-compile-dbg;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=egdaniel@chromium.org Change-Id: Ie5e6f96ae8af08c4ab50976b65f2a4eb45bca064 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1567017Reviewed-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@{#650606}
-
Frank Tang authored
https://chromium.googlesource.com/chromium/deps/icu.git/+log/4ae7482a..35f7e13 It includes 35f7e13 Update ICU to 64-2-rc ccb314e Fix config_data 85768aa Add 32 more locales for Android (OFF by default) Data size impact is small- just a couple K To test, in v8 see the Japanese Era year change from 2019/4/30 to 2019/5/1 d8> d = new Date(Date.UTC(2019,3,30)) Mon Apr 29 2019 17:00:00 GMT-0700 (Pacific Daylight Time) d8> d.toLocaleDateString("ja-u-ca-japanese", {era: "long", timeZone: "Etc/UTC"}) "平成31年4月30日" d8> d = new Date(Date.UTC(2019,4,1)) Tue Apr 30 2019 17:00:00 GMT-0700 (Pacific Daylight Time) d8> d.toLocaleDateString("ja-u-ca-japanese", {era: "long", timeZone: "Etc/UTC"}) "令和1年5月1日" Test: See above Bug: 952501, 952305, 949885, 949962 Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng Change-Id: I7626b48cb8258e3f54690e81d2eb04f1928315d1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1566724 Commit-Queue: Jungshik Shin <jshin@chromium.org> Reviewed-by:
Jungshik Shin <jshin@chromium.org> Cr-Commit-Position: refs/heads/master@{#650605}
-
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: Iaa28980cad6aafaff789931cc497bc2128bc100d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1567016Reviewed-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@{#650604}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/424cd978f64d..1f504bd31cbf Created with: gclient setdep -r src-internal@1f504bd31cbf The AutoRoll server is located here: https://autoroll-internal.skia.org/r/src-internal-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.chrome.try:linux-chromeos-chrome TBR=anthonyvd@chromium.org,andypaicu@chromium.org,aboxhall@chromium.org,caseq@chromium.org Change-Id: If84d914f34c669af0bfb2b09316708162162e9ae Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1566949Reviewed-by:
chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#650603}
-