Google Git
Sign in
chromium / chromium / src / 01dbc5e6f2d36a8eae61dff7161d891c87b5cadc
commit01dbc5e6f2d36a8eae61dff7161d891c87b5cadc[log] [tgz]
authorBen Pastene <bpastene@chromium.org>Thu Apr 11 20:21:48 2024
committerChromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Apr 11 20:21:48 2024
tree76e9edcb1cbdc43ad6e1bbc0c4cf5bd9c1b7b962
parent4ee3c867b219ca693470fb25d0dad60b66ddb5b5 [diff]
infra: Switch cros arm64-generic bot to build with the VM-optimized sdk

http://b/303119905 is tracking an effort to enable tests on CrOS
arm64 VMs. For chrome, that's practically this bot:
https://ci.chromium.org/ui/p/chromium/builders/ci/chromeos-arm64-generic-rel

That bot's currently compile-only. So to enable tests, the bot needs a
couple things.

First, it needs to be told to download an OS image to run the tests
on. This is what the "cros_boards_with_qemu_images" gclient var
change does.

Second, it needs to switch to the VM-optimized arm64-generic board.
(This is what the gn_args change does.) The two boards are mostly
identical, except the VM-optimized one produces test images that are
a bit faster when booted via qemu.

After that, the bot should be able to have VM tests added to it
in follow-ups (provided that the tests are green).

Bug: 303119905
Change-Id: I9679bba6181852ab70925ddd55aabfcda8f09e46
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5444869
Commit-Queue: Ben Pastene <bpastene@chromium.org>
Reviewed-by: Struan Shrimpton <sshrimp@google.com>
Cr-Commit-Position: refs/heads/main@{#1286061}
6 files changed
tree: 76e9edcb1cbdc43ad6e1bbc0c4cf5bd9c1b7b962
  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. clank
  52. internal
  53. ios_internal
  54. native_client
  55. signing_keys
  56. v8
  57. .clang-format
  58. .clang-tidy
  59. .clangd
  60. .eslintrc.js
  61. .git-blame-ignore-revs
  62. .gitallowed
  63. .gitattributes
  64. .gitignore
  65. .gitmodules
  66. .gn
  67. .mailmap
  68. .rustfmt.toml
  69. .vpython3
  70. .yapfignore
  71. ATL_OWNERS
  72. AUTHORS
  73. BUILD.gn
  74. CODE_OF_CONDUCT.md
  75. codereview.settings
  76. DEPS
  77. DIR_METADATA
  78. LICENSE
  79. LICENSE.chromium_os
  80. OWNERS
  81. PRESUBMIT.py
  82. PRESUBMIT_test.py
  83. PRESUBMIT_test_mocks.py
  84. README.md
  85. 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.