commit | 304200f05bdaa026274d7c9532bf1366d69652a5 | [log] [tgz] |
---|---|---|
author | chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> | Sat Jun 25 10:50:58 2022 |
committer | Copybara-Service <copybara-worker@google.com> | Sat Jun 25 11:09:46 2022 |
tree | 9e8501b751db57ee88cd7914d28f626ab5990d4c | |
parent | 21685e0c72e27c74816fb9679c43d4324a587da9 [diff] |
Roll Fuchsia Internal Images from 8.20220624.3.1 to 8.20220625.1.1 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://skia-autoroll.corp.goog/r/fuchsia-internal-images-chromium Please CC chrome-fuchsia-gardener@grotations.appspotmail.com 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md Cq-Include-Trybots: luci.chrome.try:fuchsia-fyi-astro Tbr: chrome-fuchsia-gardener@grotations.appspotmail.com Disable-Retries: true Change-Id: Ib5e1240084cf6ed7f04bc4c62c931803a510f7c2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3724586 Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Bot-Commit: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#1017949} NOKEYCHECK=True GitOrigin-RevId: 1fe61c2bb1305aaf79ec9c63543e188d4b851c2e
//build
contains:
Since this directory is DEPS'ed in by some other repositories (webrtc, pdfium, v8, etc), it should be kept as self-contained as possible by not referring to files outside of it. Some exceptions exist (//testing
, select //third_party
subdirectories), but new dependencies tend to break these other projects, and so should be avoided.
Changes to //build
should be landed in the Chromium repo. They will then be replicated to the stand-alone build repo by the gsubtreed tool. Note: You can find all directories already available through gsubtreed in the list of all chromium repos.
//build/config
- Common templates via .gni
files.//build/toolchain
- GN toolchain definitions.Other .py files
- Some are used by GN/Ninja. Some by gclient hooks, some are just random utilities.Files referenced by //.gn
:
//build/BUILDCONFIG.gn
- Included by all BUILD.gn
files.//build/secondary
- An overlay for BUILD.gn
files. Enables adding BUILD.gn
to directories that live in sub-repositories.//build_overrides
- Refer to //build_overrides/README.md.