commit | effc776d15ef0243b58e93dd2eee0a7dc89121e2 | [log] [tgz] |
---|---|---|
author | Skylab tests cros image roller <skylab-test-cros-roller@chops-service-accounts.iam.gserviceaccount.com> | Fri Feb 03 02:45:45 2023 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Feb 03 02:45:45 2023 |
tree | 7644ed5c4c4cc2c640bc6884258ba381e9071bec | |
parent | 45cc80127d70a20508fb29837d7c6a430d9ccf22 [diff] |
[skylab_tests] Update skylab tests cros img version This cl only affect Lacros on-device config builders like lacros-amd64-generic-chrome-skylab. This cl will certainly NOT affect linux-lacros builders(linux-lacros-tester-rel, linux-lacros-rel, etc) or any other platforms. This CL will update cros image version for skylab tests. CROS_BOARD_LKGM is updated according to chromeos/CHROMEOS_LKGM; CROS_BOARD_DEV, CROS_BOARD_BETA and CROS_BOARD_STABLE are updated according to Omaha. If this CL caused regressions, please revert and pause the autoroller at https://luci-scheduler.appspot.com/jobs/chrome/lacros-skylab-tests-cros-img-roller Also please file a bug to OS>LaCrOS>Partner, and CC svenzheng@chromium.org, yjt@google.com. R=rubber-stamper@appspot.gserviceaccount.com Cq-Include-Trybots: luci.chrome.try:lacros-amd64-generic-chrome-skylab Requires-Testing: True Change-Id: I57ef3f187a2239768d1cadc9d63c7f0dca953f11 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4219477 Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Auto-Submit: skylab-test-cros-roller@chops-service-accounts.iam.gserviceaccount.com <skylab-test-cros-roller@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#1100807}
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.