Google Git
Sign in
chromium / chromium / src / 29df86deade3ea9f876d9ed33573303b58623416
commit29df86deade3ea9f876d9ed33573303b58623416[log] [tgz]
authorTsuyoshi Horo <horo@chromium.org>Mon Nov 06 00:56:20 2023
committerChromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon Nov 06 00:56:20 2023
tree4cca7f65e0bfabea7f0eb6de55d318c226698f1f
parent3fcf91b0c49d11b14a452510f2dd8b55d1a41ad1 [diff]
Add experimental web tests for BackgroundResourceFetch in Linux Tests

This CL adds two experimental ci_only test steps
(brfetch_blink_web_tests and brfetch_blink_wpt_tests) in Linux Tests
bots for the BackgroundResourceFetch feature (crbug.com/1379780).

BackgroundResourceFetch introduces a new resource loading logic in
Blink. This feature will impact almost all subresource loading, so we
need to run many tests to ensure that it works as expected. However,
running all tests with and without the feature for every commit in the
commit queue is not ideal.

These two test steps are 100% experimental, so the test failure doesn't
alert a sheriff. They are also ci_only, so they will only run on CQ when
`Include-Ci-Only-Tests: true` is set.

Bug: 1498364
Change-Id: Ieb08c90bf9568dd7b82a5fd58635ee1eeb493c3a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4996932
Reviewed-by: Erik Staab <estaab@chromium.org>
Reviewed-by: Ben Pastene <bpastene@chromium.org>
Commit-Queue: Tsuyoshi Horo <horo@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1220076}
7 files changed
tree: 4cca7f65e0bfabea7f0eb6de55d318c226698f1f
  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. .eslintrc.js
  60. .git-blame-ignore-revs
  61. .gitattributes
  62. .gitignore
  63. .gitmodules
  64. .gn
  65. .mailmap
  66. .rustfmt.toml
  67. .vpython3
  68. .yapfignore
  69. ATL_OWNERS
  70. AUTHORS
  71. BUILD.gn
  72. CODE_OF_CONDUCT.md
  73. codereview.settings
  74. DEPS
  75. DIR_METADATA
  76. LICENSE
  77. LICENSE.chromium_os
  78. OWNERS
  79. PRESUBMIT.py
  80. PRESUBMIT_test.py
  81. PRESUBMIT_test_mocks.py
  82. README.md
  83. 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.