tree 45428923a13e81c8607e31913954ecdda267fb76
parent e544e09ee8bd1fb5630518a4cf854eec0fd8293e
author chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> 1729882416 +0000
committer Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> 1729882416 +0000

Roll BoringSSL from 7628194c2305 to 9588d3c35d43 (1 revision)

https://boringssl.googlesource.com/boringssl.git/+log/7628194c2305..9588d3c35d43

2024-10-25 davidben@google.com Use DTLSRecordNumber in DTLSWriteEpoch

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/boringssl-chromium
Please CC boringssl-cabal@google.com,boringssl@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in BoringSSL: https://crbug.com/boringssl/new
To file a bug in Chromium: https://crbug.com/new

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Tbr: boringssl-cabal@google.com
Change-Id: Ieb90d9996b177b5925fd89b9a32c683a331fa8be
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5966663
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/main@{#1374073}