Roll Chromite from 4aa1b4433713 to 0ba8ad7c5415 (4 revisions) https://chromium.googlesource.com/chromiumos/chromite.git/+log/4aa1b4433713..0ba8ad7c5415 2025-03-18 vapier@chromium.org shell: enter_chroot: stop passing in CHROOT_CWD 2025-03-17 vapier@chromium.org lib: sysroot_lib: stop setting PORTAGE_USERNAME 2025-03-17 vapier@chromium.org lib: cros_sdk: rip `cd $CHROOT_CWD` out of existing ~/.bash_profile 2025-03-17 vapier@chromium.org lib: cros_sdk_lib: stop putting PORTAGE_USERNAME in SDK shell env If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/chromite-chromium-autoroll Please CC chrome-os-gardeners-reviews@google.com,chrome-os-gardeners@google.com,chromeos-velocity@google.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://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 Cq-Include-Trybots: luci.chrome.try:chromeos-betty-chrome Tbr: chrome-os-gardeners-reviews@google.com Change-Id: Ibe13bd4b6f40400a0ac8b23ee623a7649090e4b1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6365682 Bot-Commit: 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/main@{#1434237}
ChromiumChromium 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.