commit | cdc1d1a09fb17e829bf0fa2a128b8be658fad4bc | [log] [tgz] |
---|---|---|
author | Lacros QA qualified tracking roller <lacros-tracking-roller@chops-service-accounts.iam.gserviceaccount.com> | Sat Jun 04 01:12:05 2022 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Sat Jun 04 01:12:05 2022 |
tree | c5d0a3cf53b4a19a51b1d14b25244ad8e77d853b | |
parent | 587d23ed9562406162b8e7c877621cf330eda4f8 [diff] |
[lacros] Update lacros QA qualified version This CL will update lacros version in //chrome/LACROS_QA_QUALIFIED_VERSION. This file will be used in Upreving the RootFS-Lacros in the CROS image. If this CL caused regressions, please revert and pause the autoroller at https://luci-scheduler.appspot.com/jobs/chrome/lacros-qa-qualified-tracking-roller Also please file a bug to OS>LaCrOS>Partner, and CC svenzheng@chromium.org, yjt@google.com. R=rubber-stamper@appspot.gserviceaccount.com Change-Id: I5fe100b580b4b9eb51d128118b6d14b1e748c6e6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3690312 Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Auto-Submit: lacros-tracking-roller@chops-service-accounts.iam.gserviceaccount.com <lacros-tracking-roller@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/5060@{#534} Cr-Branched-From: b83393d0f4038aeaf67f970a024d8101df7348d1-refs/heads/main@{#1002911}
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.