commit | 18dc1ec41fa018cfb5ee9b9f823a693dddc44253 | [log] [tgz] |
---|---|---|
author | chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> | Tue Feb 18 17:33:16 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Feb 18 17:33:16 2025 |
tree | 6e6737cb6e1fa190e867adc7e44a6151498bffaa | |
parent | 8460bb39c20431c8170ca4ecbb38dac20d835b7d [diff] |
Roll BoringSSL from 8c6b0c04f19f to 1a42cb8b2702 (1 revision) https://boringssl.googlesource.com/boringssl.git/+log/8c6b0c04f19f..1a42cb8b2702 2025-02-18 davidben@google.com Revert "runner: Switch back to filippo.io/mlkem768 for now" 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: Id9a270edbb031673ef215364f079566b24c8aca5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6277607 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@{#1421446}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone
! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure.
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.