commit | 8abef7234935a825ae4aeddf062366e3a182522b | [log] [tgz] |
---|---|---|
author | chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> | Thu Jun 13 19:22:24 2024 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Jun 13 19:22:24 2024 |
tree | e51cc0e152c9078a4370acee7c6daf3abf78a7bb | |
parent | ea7942f5e8e6000065ddbb505ccb8a0022a3eeb2 [diff] |
Roll RE2 from 33eba105f662 to 4a8cee3dd3c3 (1 revision) https://chromium.googlesource.com/external/github.com/google/re2.git/+log/33eba105f662..4a8cee3dd3c3 2024-06-13 junyer@google.com Make the Bazel CI workflow test different Python versions. If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/re2-chromium Please CC junyer@chromium.org,thakis@chromium.org on the revert to ensure that a human is aware of the problem. To file a bug in Chromium: https://bugs.chromium.org/p/chromium/issues/entry 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: junyer@chromium.org,thakis@chromium.org Change-Id: I8ec53df61247f3cc45e86644019fbfd8546a6f30 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5631051 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@{#1314798}
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.