Roll Chromite from 033823256b56 to 317edad47272 (10 revisions)

https://chromium.googlesource.com/chromiumos/chromite.git/+log/033823256b56..317edad47272

2024-04-22 jrosenth@chromium.org Ignore flags.no_replace to SdkService/Create
2024-04-20 jrosenth@chromium.org lib: cros_sdk_lib: Improve fetch_remote_tarballs logging
2024-04-20 jrosenth@chromium.org systemd: Add configurations for cros-cron
2024-04-19 srinivashegde@google.com scripts: Use relative names instead of hardcoding it.
2024-04-19 jrosenth@chromium.org lib: path_util: Fix tracks_main property for paygen
2024-04-19 tbain@google.com lib: Pass BAZEL_USE_REMOTE_CACHING into chroot
2024-04-19 jrosenth@chromium.org cli: cros cron: Implement the basics of "cros cron run"
2024-04-19 jrosenth@chromium.org cli: cros ap: Refactor to use CommandGroup
2024-04-19 jrosenth@chromium.org cli: command: Add a CommandGroup helper
2024-04-19 jrosenth@chromium.org lib: cros_sdk_lib: Allow fetch_remote_tarballs to take an argument

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-pi-arc-chrome
Tbr: chrome-os-gardeners-reviews@google.com
Change-Id: I1df2489fe385813ff7401b5a0fab4307db26805f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5472226
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@{#1290758}
2 files changed
tree: 8ad7438552dc917f3908d16d530baee0ca860a43
  1. android_webview/
  2. apps/
  3. ash/
  4. base/
  5. build/
  6. build_overrides/
  7. buildtools/
  8. cc/
  9. chrome/
  10. chromecast/
  11. chromeos/
  12. codelabs/
  13. components/
  14. content/
  15. courgette/
  16. crypto/
  17. dbus/
  18. device/
  19. docs/
  20. extensions/
  21. fuchsia_web/
  22. gin/
  23. google_apis/
  24. google_update/
  25. gpu/
  26. headless/
  27. infra/
  28. ios/
  29. ipc/
  30. media/
  31. mojo/
  32. native_client_sdk/
  33. net/
  34. pdf/
  35. ppapi/
  36. printing/
  37. remoting/
  38. rlz/
  39. sandbox/
  40. services/
  41. skia/
  42. sql/
  43. storage/
  44. styleguide/
  45. testing/
  46. third_party/
  47. tools/
  48. ui/
  49. url/
  50. webkit/
  51. .clang-format
  52. .clang-tidy
  53. .clangd
  54. .eslintrc.js
  55. .git-blame-ignore-revs
  56. .gitallowed
  57. .gitattributes
  58. .gitignore
  59. .gitmodules
  60. .gn
  61. .mailmap
  62. .rustfmt.toml
  63. .vpython3
  64. .yapfignore
  65. ATL_OWNERS
  66. AUTHORS
  67. BUILD.gn
  68. CODE_OF_CONDUCT.md
  69. codereview.settings
  70. CPPLINT.cfg
  71. DEPS
  72. DIR_METADATA
  73. LICENSE
  74. LICENSE.chromium_os
  75. OWNERS
  76. PRESUBMIT.py
  77. PRESUBMIT_test.py
  78. PRESUBMIT_test_mocks.py
  79. README.md
  80. WATCHLISTS
README.md

Logo Chromium

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.