| commit | fec76841faa0737faa60e481e764ff0b51a6650e | [log] [tgz] |
|---|---|---|
| author | chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> | Thu Sep 07 17:18:49 2023 |
| committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Sep 07 17:18:49 2023 |
| tree | 898213f4db4303a3ec20a5dc48e1e12c5e2d95ef | |
| parent | a6df0c8d83a1bfbcdbc6293b688c2cbb89812edf [diff] |
Roll Depot Tools from 29282b581bc6 to c3d210d6052a (2 revisions) https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/29282b581bc6..c3d210d6052a 2023-09-07 philwo@google.com post_build_ninja_summary.py: Gracefully handle empty .ninja_log files 2023-09-07 bentekkie@google.com [reclient] Add hostname to invocation ids If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/depot-tools-chromium-autoroll Please CC ajp@google.com,aravindvasudev@google.com,gavinmak@google.com,sokcevic@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://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 Bug: None Tbr: ajp@google.com,aravindvasudev@google.com,gavinmak@google.com,sokcevic@chromium.org Change-Id: I286484f168e5eeb6b8666efdb469ce7b7251f01d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4849720 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@{#1193654}
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.