Google Git
Sign in
chromium / chromium / src / 923f6c65618ff0b31b5fb136663945186d7036b9
commit923f6c65618ff0b31b5fb136663945186d7036b9[log] [tgz]
authorYusuke Sato <yusukes@chromium.org>Mon Apr 05 00:43:52 2021
committerChromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon Apr 05 00:43:52 2021
treee17595fa0d709c21e11da880f258cb4b4cb9e83b
parent047050bed6248542508e1d9e0879a9b52c4c36a5 [diff]
Reland "arcvm: Test androidboot.arcvm_ureadahead_mode generation"

This reverts commit 0e3d2b854abcb5ca3b296601a26d89e015ad3621.

Reason for revert: a fix is in though speculative:
https://chromium-review.googlesource.com/c/chromium/src/+/2803691

Original change's description:
> Revert "arcvm: Test androidboot.arcvm_ureadahead_mode generation"
>
> This reverts commit 2dc92b6ec4eb02c819210f21e054970442f1e0f7.
>
> Reason for revert: suspect that this change may cause ArcVmClientAdapterTest tests flakiness. If it doesn't help, then this CL should be relanded.
>
> Original change's description:
> > arcvm: Test androidboot.arcvm_ureadahead_mode generation
> >
> > BUG=None
> > TEST=try
> >
> > Change-Id: I6ad4bedfb48b6f6979fccaad872e6db34cf24ec9
> > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2788028
> > Reviewed-by: Yury Khmel <khmel@chromium.org>
> > Commit-Queue: Yusuke Sato <yusukes@chromium.org>
> > Cr-Commit-Position: refs/heads/master@{#866911}
>
> Bug: 1193425
> Change-Id: I18cac91d8fe81eb0a767570c29e2648577a496f4
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2788791
> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
> Commit-Queue: Rushan Suleymanov <rushans@google.com>
> Owners-Override: Rushan Suleymanov <rushans@google.com>
> Cr-Commit-Position: refs/heads/master@{#867152}

Bug: 1193425
Change-Id: I357e5d72e048d0be7d5e056928303335a823639e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2803676
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Reviewed-by: Yury Khmel <khmel@chromium.org>
Commit-Queue: Yusuke Sato <yusukes@chromium.org>
Cr-Commit-Position: refs/heads/master@{#869066}
1 file changed
tree: e17595fa0d709c21e11da880f258cb4b4cb9e83b
  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. cloud_print/
  13. codelabs/
  14. components/
  15. content/
  16. courgette/
  17. crypto/
  18. dbus/
  19. device/
  20. docs/
  21. extensions/
  22. fuchsia/
  23. gin/
  24. google_apis/
  25. google_update/
  26. gpu/
  27. headless/
  28. infra/
  29. ios/
  30. ipc/
  31. jingle/
  32. media/
  33. mojo/
  34. native_client_sdk/
  35. net/
  36. pdf/
  37. ppapi/
  38. printing/
  39. remoting/
  40. rlz/
  41. sandbox/
  42. services/
  43. skia/
  44. sql/
  45. storage/
  46. styleguide/
  47. testing/
  48. third_party/
  49. tools/
  50. ui/
  51. url/
  52. weblayer/
  53. .clang-format
  54. .clang-tidy
  55. .eslintrc.js
  56. .git-blame-ignore-revs
  57. .gitattributes
  58. .gitignore
  59. .gn
  60. .vpython
  61. .vpython3
  62. .yapfignore
  63. AUTHORS
  64. BUILD.gn
  65. CODE_OF_CONDUCT.md
  66. codereview.settings
  67. DEPS
  68. DIR_METADATA
  69. ENG_REVIEW_OWNERS
  70. LICENSE
  71. LICENSE.chromium_os
  72. OWNERS
  73. PRESUBMIT.py
  74. PRESUBMIT_test.py
  75. PRESUBMIT_test_mocks.py
  76. README.md
  77. 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.