[COIL] Change chromium code search type links to use main rather than master for docs
See this doc: go/chromium-coil-change for more info
BUG=1210385
Change-Id: I6cd8548301e360bae8e71384dbd8ef11aa6c985f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2902904
Reviewed-by: My Nguyen <myy@chromium.org>
Commit-Queue: My Nguyen <myy@chromium.org>
Auto-Submit: John Palmer <jopalmer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#885851}
This commit is contained in:
John Palmer
committed by
Chromium LUCI CQ
Chromium LUCI CQ
parent
a13109cfaa
commit
046f987e02
docs
DIR_METADATAREADME.md
accessibility
ad_tagging.mdandroid_build_instructions.mdandroid_debugging_instructions.mdautofill
chrome_os_logging.mdchrome_untrusted.mdchromeos_build_instructions.mdchromeos_glossary.mdcipd_and_3pp.mdclang_sheriffing.mdclang_tool_refactoring.mdcode_reviews.mdcommit_checklist.mdcontributing.mddbus_mojo_connection_service.mddesign
disassemble_code.mddocumentation_guidelines.mdenterprise
gpu
debugging_gpu_related_code.mdgpu_testing.mdgpu_testing_bot_details.mdpixel_wrangling.mdswiftshader.mdvaapi.md
graphical_debugging_aid_chromium_views.mdhow_cc_works.mdhow_to_add_your_feature_flag.mdimages
infra
inlined_stack_traces.mdios
lacros.mdlinux
login
mac_build_instructions.mdmedia
DIR_METADATA
gpu
memory-infra
memory
navigation.mdnew_port_policy.mdparsing_test_results.mdprivacy
privacy_budget
process
qtcreator.mdsecurity
DIR_METADATA
shutdown.mdlookalikes
permissions-for-powerful-web-platform-features.mdpost-spectre-webdev.mdside-channel-threat-model.mdspeed
DIR_METADATAaddressing_performance_regressions.mdapk_size_regressions.md
benchmark
binary_size
bot_health_sheriffing
help_improve_performance.mdimages
metrics_changelog
perf_waterfall.mdspeed_domains.mdspeed_metrics
sync
testing
DIR_METADATAbatching_instrumentation_tests.mdcode_coverage.mdcode_coverage_in_gerrit.mdtest_descriptions.mdtest_executable_api.mdtesting_in_chromium.mdweb_platform_tests.mdweb_platform_tests_wptrunner.mdweb_tests_linux.md
trusted_types_on_webui.mdui
updater
updating_clang_format_binaries.mdvscode.mdwebui_in_chrome.mdwebui_in_components.mdwindows_native_window_occlusion_tracking.mdwindows_pwa_integration.mdwindows_shortcut_and_taskbar_handling.mdwindows_virtual_desktop_handling.mdworking_remotely_with_android.md@ -1,10 +1,10 @@
|
||||
# Metadata information for this directory.
|
||||
#
|
||||
# For more information on DIR_METADATA files, see:
|
||||
# https://source.chromium.org/chromium/infra/infra/+/master:go/src/infra/tools/dirmd/README.md
|
||||
# https://source.chromium.org/chromium/infra/infra/+/main:go/src/infra/tools/dirmd/README.md
|
||||
#
|
||||
# For the schema of this file, see Metadata message:
|
||||
# https://source.chromium.org/chromium/infra/infra/+/master:go/src/infra/tools/dirmd/proto/dir_metadata.proto
|
||||
# https://source.chromium.org/chromium/infra/infra/+/main:go/src/infra/tools/dirmd/proto/dir_metadata.proto
|
||||
|
||||
# build@ isn't really the right component for this, but it'll
|
||||
# do until we create a component for documentation.
|
||||
|
||||
@ -4,7 +4,7 @@ This directory contains chromium project documentation in
|
||||
[Gitiles-flavored Markdown]. It is automatically [rendered by Gitiles].
|
||||
|
||||
[Gitiles-flavored Markdown]: https://gerrit.googlesource.com/gitiles/+/master/Documentation/markdown.md
|
||||
[rendered by Gitiles]: https://chromium.googlesource.com/chromium/src/+/master/docs/
|
||||
[rendered by Gitiles]: https://chromium.googlesource.com/chromium/src/+/main/docs/
|
||||
|
||||
If you add new documents, please also add a link to them in the Document Index
|
||||
below.
|
||||
|
||||
@ -1,10 +1,10 @@
|
||||
# Metadata information for this directory.
|
||||
#
|
||||
# For more information on DIR_METADATA files, see:
|
||||
# https://source.chromium.org/chromium/infra/infra/+/master:go/src/infra/tools/dirmd/README.md
|
||||
# https://source.chromium.org/chromium/infra/infra/+/main:go/src/infra/tools/dirmd/README.md
|
||||
#
|
||||
# For the schema of this file, see Metadata message:
|
||||
# https://source.chromium.org/chromium/infra/infra/+/master:go/src/infra/tools/dirmd/proto/dir_metadata.proto
|
||||
# https://source.chromium.org/chromium/infra/infra/+/main:go/src/infra/tools/dirmd/proto/dir_metadata.proto
|
||||
|
||||
monorail {
|
||||
component: "Internals>Accessibility"
|
||||
|
||||
@ -92,7 +92,7 @@ The next steps require that you have the full Chrome OS source code
|
||||
checked out and you're in your chroot. See the Chromium OS Developer Guide
|
||||
for instructions:
|
||||
|
||||
https://chromium.googlesource.com/chromiumos/docs/+/master/developer_guide.md
|
||||
https://chromium.googlesource.com/chromiumos/docs/+/main/developer_guide.md
|
||||
|
||||
|
||||
espeak-ng is in this directory:
|
||||
|
||||
@ -131,7 +131,7 @@ does not require the shared unique id. Consider the same example above.
|
||||
~~~
|
||||
|
||||
## Docs & References:
|
||||
[Custom UIA Property and Pattern registration in Chromium](https://chromium.googlesource.com/chromium/src/+/master/ui/accessibility/platform/uia_registrar_win.h)
|
||||
[Custom UIA Property and Pattern registration in Chromium](https://chromium.googlesource.com/chromium/src/+/main/ui/accessibility/platform/uia_registrar_win.h)
|
||||
|
||||
[UI Automation IItemContainerPattern. It is used to look up IAccessible2 element
|
||||
via a unique id](https://docs.microsoft.com/en-us/windows/win32/api/uiautomationclient/nn-uiautomationclient-iuiautomationitemcontainerpattern)
|
||||
|
||||
@ -510,9 +510,9 @@ which is renderer-side code, and in JavaScript by the [automation API]. The API
|
||||
is defined by [automation.idl], which must be kept synchronized with
|
||||
[ax_enums.mojom].
|
||||
|
||||
[ax.mojom.AXActionData]: https://source.chromium.org/chromium/chromium/src/+/master:ui/accessibility/mojom/ax_action_data.mojom;l=13
|
||||
[ax.mojom.RenderAccessibilityHost::HandleAXEvents()]: https://source.chromium.org/chromium/chromium/src/+/master:content/common/render_accessibility.mojom;l=47
|
||||
[ax.mojom.RenderAccessibility.PerformAction()]: https://source.chromium.org/chromium/chromium/src/+/master:content/common/render_accessibility.mojom;l=86
|
||||
[ax.mojom.AXActionData]: https://source.chromium.org/chromium/chromium/src/+/main:ui/accessibility/mojom/ax_action_data.mojom;l=13
|
||||
[ax.mojom.RenderAccessibilityHost::HandleAXEvents()]: https://source.chromium.org/chromium/chromium/src/+/main:content/common/render_accessibility.mojom;l=47
|
||||
[ax.mojom.RenderAccessibility.PerformAction()]: https://source.chromium.org/chromium/chromium/src/+/main:content/common/render_accessibility.mojom;l=86
|
||||
[AutomationInternalCustomBindings]: https://cs.chromium.org/chromium/src/extensions/renderer/api/automation/automation_internal_custom_bindings.h
|
||||
[AXContentNodeData]: https://cs.chromium.org/chromium/src/content/common/ax_content_node_data.h
|
||||
[AXLayoutObject]: https://cs.chromium.org/chromium/src/third_party/blink/renderer/modules/accessibility/ax_layout_object.h
|
||||
@ -530,7 +530,7 @@ is defined by [automation.idl], which must be kept synchronized with
|
||||
[ViewAccessibility]: https://cs.chromium.org/chromium/src/ui/views/accessibility/view_accessibility.h
|
||||
[Node]: https://cs.chromium.org/chromium/src/third_party/blink/renderer/core/dom/node.h
|
||||
[RenderAccessibilityImpl]: https://cs.chromium.org/chromium/src/content/renderer/accessibility/render_accessibility_impl.h
|
||||
[RenderAccessibilityManager]: https://source.chromium.org/chromium/chromium/src/+/master:content/renderer/accessibility/render_accessibility_manager.h
|
||||
[RenderAccessibilityManager]: https://source.chromium.org/chromium/chromium/src/+/main:content/renderer/accessibility/render_accessibility_manager.h
|
||||
[RenderFrameHostImpl]: https://cs.chromium.org/chromium/src/content/browser/renderer_host/render_frame_host_impl.h
|
||||
[ui::AXNodeData]: https://cs.chromium.org/chromium/src/ui/accessibility/ax_node_data.h
|
||||
[WebAXObject]: https://cs.chromium.org/chromium/src/third_party/blink/public/web/web_ax_object.h
|
||||
|
||||
@ -11,7 +11,7 @@ project is integrated into Chrome on Desktop.
|
||||
## Overview
|
||||
|
||||
Desktop Reader Mode is hidden behind a
|
||||
[base::Feature](https://source.chromium.org/chromium/chromium/src/+/master:components/dom_distiller/core/dom_distiller_features.cc)
|
||||
[base::Feature](https://source.chromium.org/chromium/chromium/src/+/main:components/dom_distiller/core/dom_distiller_features.cc)
|
||||
flag, ‘enable-reader-mode’. To run Chrome with Reader Mode, set the “Enable
|
||||
Reader Mode” flag to “Enabled” in chrome://flags or start Chrome with
|
||||
--enable-feature=”ReaderMode”.
|
||||
@ -72,7 +72,7 @@ forwards it to all registered observers, and caches it.
|
||||
### Toggling Reader Mode
|
||||
Users can toggle reader mode using an omnibox icon or an option, Toggle Reader
|
||||
Mode, in the “customize and control Chrome” menu, both of which execute
|
||||
BrowserCommands [ToggleDistilledView()](https://source.chromium.org/chromium/chromium/src/+/master:chrome/browser/ui/browser_commands.cc;bpv=1;bpt=1;l=1364?q=browser_commands%20dom_distiller&ss=chromium%2Fchromium%2Fsrc).
|
||||
BrowserCommands [ToggleDistilledView()](https://source.chromium.org/chromium/chromium/src/+/main:chrome/browser/ui/browser_commands.cc;bpv=1;bpt=1;l=1364?q=browser_commands%20dom_distiller&ss=chromium%2Fchromium%2Fsrc).
|
||||
|
||||
[ReaderModeIconView](https://cs.chromium.org/chromium/src/chrome/browser/ui/views/reader_mode/reader_mode_icon_view.h)
|
||||
is a DistillabilityObserver and sets its visibility based on the latest result
|
||||
@ -144,7 +144,7 @@ considered a black box.
|
||||
|
||||
In short, content is extracted from the fully rendered article via Javascript
|
||||
(specifically from the compiled Javascript file built from DOM Distiller,
|
||||
[domdistiller.js](https://source.chromium.org/chromium/chromium/src/+/master:third_party/dom_distiller_js/dist/js/domdistiller.js))
|
||||
[domdistiller.js](https://source.chromium.org/chromium/chromium/src/+/main:third_party/dom_distiller_js/dist/js/domdistiller.js))
|
||||
into a DistilledPageProto.
|
||||
|
||||
The DOM Distiller retrieves the currently loaded document’s DOM and converts it
|
||||
@ -166,11 +166,11 @@ the following:
|
||||
|
||||
### Displaying Reader Mode Pages
|
||||
|
||||
A [DistilledPageProto](https://source.chromium.org/chromium/chromium/src/+/master:components/dom_distiller/core/proto/distilled_page.proto)
|
||||
A [DistilledPageProto](https://source.chromium.org/chromium/chromium/src/+/main:components/dom_distiller/core/proto/distilled_page.proto)
|
||||
is created for each page distilled, and is used to generate the HTML of the
|
||||
distilled page.
|
||||
|
||||
Pages are loaded by
|
||||
[DomDistillerViewerSource](https://source.chromium.org/chromium/chromium/src/+/master:components/dom_distiller/content/browser/dom_distiller_viewer_source.h),
|
||||
[DomDistillerViewerSource](https://source.chromium.org/chromium/chromium/src/+/main:components/dom_distiller/content/browser/dom_distiller_viewer_source.h),
|
||||
which serves the HTML and resources for viewing pages. After the DOM is
|
||||
initially loaded, the contents are populated via Javascript.
|
||||
|
||||
@ -44,7 +44,7 @@ out/release/content_shell \
|
||||
```
|
||||
|
||||
For information on modifying or adding web tests, see the main
|
||||
[web tests documentation](https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_tests.md).
|
||||
[web tests documentation](https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_tests.md).
|
||||
|
||||
## DumpAccessibilityTree tests
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ behavior](https://support.google.com/webtools/answer/7347327).
|
||||
|
||||
The ad detection infrastructure is called Ad Tagging. Ad Tagging works by
|
||||
matching resource requests against a filter list (see how the list is
|
||||
[generated](https://chromium.googlesource.com/chromium/src.git/+/master/components/subresource_filter/FILTER_LIST_GENERATION.md))
|
||||
[generated](https://chromium.googlesource.com/chromium/src.git/+/main/components/subresource_filter/FILTER_LIST_GENERATION.md))
|
||||
to determine if they’re ad requests. Any requests matching the filter are tagged
|
||||
as ads. Further, requests (and some DOM elements such as iframes) made on behalf
|
||||
of previously tagged scripts are also tagged as ads by the
|
||||
@ -23,7 +23,7 @@ request made within an ad iframe is considered an ad resource request.
|
||||
|
||||
### Subresource Filter
|
||||
The [Subresource
|
||||
Filter](https://chromium.googlesource.com/chromium/src.git/+/master/components/subresource_filter/README.md)
|
||||
Filter](https://chromium.googlesource.com/chromium/src.git/+/main/components/subresource_filter/README.md)
|
||||
loads the filter list and matches urls against it. The list is distributed via
|
||||
the component updater. This same list and component is used for blocking ads on
|
||||
abusive sites and those that violate the Better Ads Standard.
|
||||
|
||||
@ -400,7 +400,7 @@ will not fail if an analysis check fails. Make sure to check the terminal that
|
||||
the server is running in at regular intervals to fix outstanding issues caught
|
||||
by these analysis checks.
|
||||
|
||||
[fast_local_dev]: https://source.chromium.org/chromium/chromium/src/+/master:build/android/fast_local_dev_server.py
|
||||
[fast_local_dev]: https://source.chromium.org/chromium/chromium/src/+/main:build/android/fast_local_dev_server.py
|
||||
|
||||
#### Incremental Install
|
||||
[Incremental Install](/build/android/incremental_install/README.md) uses
|
||||
|
||||
@ -20,7 +20,7 @@ out/Default/bin/chrome_public_apk launch --args='--disable-fre' 'data:text/html;
|
||||
```
|
||||
|
||||
## Logging
|
||||
[Chromium logging from LOG(INFO)](https://chromium.googlesource.com/chromium/src/+/master/docs/android_logging.md)
|
||||
[Chromium logging from LOG(INFO)](https://chromium.googlesource.com/chromium/src/+/main/docs/android_logging.md)
|
||||
etc., is directed to the Android logcat logging facility. You can filter the
|
||||
messages, e.g. view chromium verbose logging, everything else at warning level
|
||||
with:
|
||||
|
||||
@ -1,10 +1,10 @@
|
||||
# Metadata information for this directory.
|
||||
#
|
||||
# For more information on DIR_METADATA files, see:
|
||||
# https://source.chromium.org/chromium/infra/infra/+/master:go/src/infra/tools/dirmd/README.md
|
||||
# https://source.chromium.org/chromium/infra/infra/+/main:go/src/infra/tools/dirmd/README.md
|
||||
#
|
||||
# For the schema of this file, see Metadata message:
|
||||
# https://source.chromium.org/chromium/infra/infra/+/master:go/src/infra/tools/dirmd/proto/dir_metadata.proto
|
||||
# https://source.chromium.org/chromium/infra/infra/+/main:go/src/infra/tools/dirmd/proto/dir_metadata.proto
|
||||
|
||||
monorail {
|
||||
component: "UI>Browser>Autofill"
|
||||
|
||||
@ -39,5 +39,5 @@ When actively debugging issues, Chrome's `--vmodule` flag is sometimes used to
|
||||
temporarily log messages at lower severities for particular modules.
|
||||
|
||||
[base/logging.h]: ../base/logging.h
|
||||
[session_manager]: https://chromium.googlesource.com/chromiumos/platform2/+/master/login_manager/
|
||||
[Passing Chrome flags from session_manager]: https://chromium.googlesource.com/chromiumos/platform2/+/master/login_manager/docs/flags.md
|
||||
[session_manager]: https://chromium.googlesource.com/chromiumos/platform2/+/main/login_manager/
|
||||
[Passing Chrome flags from session_manager]: https://chromium.googlesource.com/chromiumos/platform2/+/main/login_manager/docs/flags.md
|
||||
|
||||
@ -57,7 +57,7 @@ Yes, but not by default and with some caveats.
|
||||
|
||||
Any team that requires extra capabilities granted to `chrome-untrusted://` should consult with the security team to ensure they are non-dangerous. In this context, we consider non-dangerous any API that we would expose to the renderer process, e.g. UMA.
|
||||
|
||||
We currently use `postMessage()` to expose certain APIs to `chrome-untrusted://`. For example, the Media App uses `postMessage()` to pass a read-only file handle to `chrome-untrusted://media-app` from `chrome-untrusted://`. Teams are encouraged to get a review from someone in [SECURITY_OWNERS](https://source.chromium.org/chromium/chromium/src/+/master:ipc/SECURITY_OWNERS) when exposing capabilities over postMessage.
|
||||
We currently use `postMessage()` to expose certain APIs to `chrome-untrusted://`. For example, the Media App uses `postMessage()` to pass a read-only file handle to `chrome-untrusted://media-app` from `chrome-untrusted://`. Teams are encouraged to get a review from someone in [SECURITY_OWNERS](https://source.chromium.org/chromium/chromium/src/+/main:ipc/SECURITY_OWNERS) when exposing capabilities over postMessage.
|
||||
|
||||
We are hoping to move to Mojo to improve auditability of these APIs and to make the security review required.
|
||||
|
||||
@ -118,7 +118,7 @@ class UntrustedExampleUI : public ui::UntrustedWebUIController {
|
||||
|
||||
2. Register the WebUIConfig
|
||||
|
||||
Add the `WebUIConfig` to the list of WebUIConfigs in `[ChromeUntrustedWebUIControllerFactory](https://source.chromium.org/chromium/chromium/src/+/master:chrome/browser/ui/webui/chrome_untrusted_web_ui_controller_factory.cc)`.
|
||||
Add the `WebUIConfig` to the list of WebUIConfigs in `[ChromeUntrustedWebUIControllerFactory](https://source.chromium.org/chromium/chromium/src/+/main:chrome/browser/ui/webui/chrome_untrusted_web_ui_controller_factory.cc)`.
|
||||
|
||||
```cpp
|
||||
register_config(std::make_unique<chromeos::UntrustedExampleUIConfig>());
|
||||
|
||||
@ -18,7 +18,7 @@ build configurations:
|
||||
## Common setup
|
||||
|
||||
First, follow the [normal Linux build
|
||||
instructions](https://chromium.googlesource.com/chromium/src/+/master/docs/linux/build_instructions.md)
|
||||
instructions](https://chromium.googlesource.com/chromium/src/+/main/docs/linux/build_instructions.md)
|
||||
as usual to get a Chromium checkout.
|
||||
|
||||
You'll also need to add `'chromeos'` to the `target_os` list in your `.gclient`
|
||||
@ -98,8 +98,8 @@ Some useful flags:
|
||||
virtual screens, by display position and size.
|
||||
* `--enable-features=Feature1,OtherFeature2`: Enable specified features.
|
||||
Features are often listed in chrome://flags, or in source files such as
|
||||
[chrome_features.cc](https://source.chromium.org/chromium/chromium/src/+/master:chrome/common/chrome_features.cc)
|
||||
or [ash_features.cc](https://source.chromium.org/chromium/chromium/src/+/master:ash/constants/ash_features.cc).
|
||||
[chrome_features.cc](https://source.chromium.org/chromium/chromium/src/+/main:chrome/common/chrome_features.cc)
|
||||
or [ash_features.cc](https://source.chromium.org/chromium/chromium/src/+/main:ash/constants/ash_features.cc).
|
||||
Note that changing values in chrome://flags does not work for
|
||||
linux-chromeos, and this flag must be used.
|
||||
* `--enable-ui-devtools[=9223]`: Allow debugging of the system UI through
|
||||
@ -201,4 +201,4 @@ supplied in the imported .gni file after the `import()` line.
|
||||
|
||||
For more information (like copying the locally-built Chrome to a device, or
|
||||
running Tast tests), consult Simple Chrome's
|
||||
[full documentation](https://chromium.googlesource.com/chromiumos/docs/+/master/simple_chrome_workflow.md).
|
||||
[full documentation](https://chromium.googlesource.com/chromiumos/docs/+/main/simple_chrome_workflow.md).
|
||||
|
||||
@ -1 +1 @@
|
||||
See [Chromium OS Glossary](https://chromium.googlesource.com/chromiumos/docs/+/master/glossary.md)
|
||||
See [Chromium OS Glossary](https://chromium.googlesource.com/chromiumos/docs/+/main/glossary.md)
|
||||
|
||||
@ -11,7 +11,7 @@
|
||||
specified in [DEPS] and updated via `gclient sync`.
|
||||
* You can [browse Chromium's CIPD repository][browse] online.
|
||||
|
||||
[CIPD]: https://chromium.googlesource.com/infra/luci/luci-go/+/master/cipd/README.md
|
||||
[CIPD]: https://chromium.googlesource.com/infra/luci/luci-go/+/main/cipd/README.md
|
||||
[DEPS]: /DEPS
|
||||
[browse]: https://chrome-infra-packages.appspot.com/p/chromium
|
||||
|
||||
@ -23,7 +23,7 @@
|
||||
* By specifying a 3pp package, you can define how to build certain artifacts and
|
||||
where to upload to CIPD. Then our packagers will do the rest for you.
|
||||
|
||||
[support_3pp]: https://chromium.googlesource.com/infra/infra/+/master/recipes/README.recipes.md#recipe_modules-support_3pp
|
||||
[support_3pp]: https://chromium.googlesource.com/infra/infra/+/main/recipes/README.recipes.md#recipe_modules-support_3pp
|
||||
|
||||
## Why use CIPD & 3pp?:
|
||||
|
||||
@ -96,9 +96,9 @@ into two main sections:
|
||||
* `upload`: contains some details on how the final result gets uploaded to CIPD.
|
||||
See [here][doc_upload] for more details.
|
||||
|
||||
[`spec.proto`]: https://chromium.googlesource.com/infra/infra/+/master/recipes/recipe_modules/support_3pp/spec.proto
|
||||
[doc_create]: https://chromium.googlesource.com/infra/infra/+/master/recipes/README.recipes.md#creation-stages
|
||||
[doc_upload]: https://chromium.googlesource.com/infra/infra/+/master/recipes/README.recipes.md#upload
|
||||
[`spec.proto`]: https://chromium.googlesource.com/infra/infra/+/main/recipes/recipe_modules/support_3pp/spec.proto
|
||||
[doc_create]: https://chromium.googlesource.com/infra/infra/+/main/recipes/README.recipes.md#creation-stages
|
||||
[doc_upload]: https://chromium.googlesource.com/infra/infra/+/main/recipes/README.recipes.md#upload
|
||||
|
||||
Staying with the example from above, the file `sample_cipd_dep/3pp/3pp.pb` may
|
||||
be like the following:
|
||||
@ -355,7 +355,7 @@ cipd_package_definition("my_cipd_package") {
|
||||
sources = [ "//path/to:test_binary_file" ]
|
||||
}
|
||||
```
|
||||
[build/cipd/cipd.gni]: https://source.chromium.org/chromium/chromium/src/+/master:build/cipd/cipd.gni
|
||||
[build/cipd/cipd.gni]: https://source.chromium.org/chromium/chromium/src/+/main:build/cipd/cipd.gni
|
||||
|
||||
### Permissions in CIPD
|
||||
|
||||
|
||||
@ -198,7 +198,7 @@ work on linker bugs without having to have a Chromium build environment.
|
||||
To use `ld.lld`'s `--reproduce` flag, follow these steps:
|
||||
|
||||
1. Locally (build Chromium with a locally-built
|
||||
clang)[https://chromium.googlesource.com/chromium/src.git/+/master/docs/clang.md#Using-a-custom-clang-binary]
|
||||
clang)[https://chromium.googlesource.com/chromium/src.git/+/main/docs/clang.md#Using-a-custom-clang-binary]
|
||||
|
||||
1. After reproducing the link error, build just the failing target with
|
||||
ninja's `-v -d keeprsp` flags added:
|
||||
|
||||
@ -220,7 +220,7 @@ When `--apply-edits` switch is not presented, tool outputs are compared to
|
||||
`*-expected.txt` and if different, the result is saved in `*-actual.txt`. Note
|
||||
that in this case, only one test file is expected.
|
||||
|
||||
[//tools/clang]: https://chromium.googlesource.com/chromium/src/+/master/tools/clang/
|
||||
[//tools/clang]: https://chromium.googlesource.com/chromium/src/+/main/tools/clang/
|
||||
[clang-docs-match-finder]: http://clang.llvm.org/doxygen/classclang_1_1ast__matchers_1_1MatchFinder.html
|
||||
[clang-docs-match-callback]: http://clang.llvm.org/doxygen/classclang_1_1ast__matchers_1_1MatchFinder_1_1MatchCallback.html
|
||||
[matcher-reference]: http://clang.llvm.org/docs/LibASTMatchersReference.html
|
||||
@ -228,7 +228,7 @@ that in this case, only one test file is expected.
|
||||
[clang-docs-replacement]: http://clang.llvm.org/doxygen/classclang_1_1tooling_1_1Replacement.html
|
||||
[clang-docs]: http://clang.llvm.org/doxygen/index.html
|
||||
[clang-tooling-tutorial]: http://clang.llvm.org/docs/LibASTMatchersTutorial.html
|
||||
[//tools/clang/blink_gc_plugin]: https://chromium.googlesource.com/chromium/src/+/master/tools/clang/blink_gc_plugin/
|
||||
[//tools/clang/plugins]: https://chromium.googlesource.com/chromium/src/+/master/tools/clang/plugins/
|
||||
[//tools/clang/rewrite_to_chrome_style]: https://chromium.googlesource.com/chromium/src/+/master/tools/clang/rewrite_to_chrome_style/
|
||||
[//tools/clang/blink_gc_plugin]: https://chromium.googlesource.com/chromium/src/+/main/tools/clang/blink_gc_plugin/
|
||||
[//tools/clang/plugins]: https://chromium.googlesource.com/chromium/src/+/main/tools/clang/plugins/
|
||||
[//tools/clang/rewrite_to_chrome_style]: https://chromium.googlesource.com/chromium/src/+/main/tools/clang/rewrite_to_chrome_style/
|
||||
[clang-tools-extra]: (https://github.com/llvm-mirror/clang-tools-extra)
|
||||
|
||||
@ -104,7 +104,7 @@ the code is updated.
|
||||
|
||||
### OWNERS file details
|
||||
|
||||
Refer to the [source code](https://chromium.googlesource.com/chromium/tools/depot_tools/+/master/owners.py)
|
||||
Refer to the [source code](https://chromium.googlesource.com/chromium/tools/depot_tools/+/main/owners.py)
|
||||
for all details on the file format.
|
||||
|
||||
This example indicates that two people are owners, in addition to any owners
|
||||
|
||||
@ -248,7 +248,7 @@ clean up your local branches. These commands will automatically delete merged
|
||||
branches. Mark the associated crbug as "fixed".
|
||||
|
||||
[//]: # (the reference link section should be alphabetically sorted)
|
||||
[build-instructions]: https://chromium.googlesource.com/chromium/src.git/+/master/docs/#Checking-Out-and-Building
|
||||
[build-instructions]: https://chromium.googlesource.com/chromium/src.git/+/main/docs/#Checking-Out-and-Building
|
||||
[chromium-tree]: https://ci.chromium.org/p/chromium/g/main/console
|
||||
[contributing]: contributing.md
|
||||
[simple-chrome]: https://chromium.googlesource.com/chromiumos/docs/+/HEAD/simple_chrome_workflow.md
|
||||
|
||||
@ -465,7 +465,7 @@ formats.
|
||||
given commit diverged from main.
|
||||
|
||||
[//]: # (the reference link section should be alphabetically sorted)
|
||||
[checkout-and-build]: https://chromium.googlesource.com/chromium/src/+/master/docs/#checking-out-and-building
|
||||
[checkout-and-build]: https://chromium.googlesource.com/chromium/src/+/main/docs/#checking-out-and-building
|
||||
[chrome-dd-review-process]: http://go/chrome-dd-review-process
|
||||
[chromium-design-docs]: https://groups.google.com/a/chromium.org/forum/#!forum/chromium-design-docs
|
||||
[code-reviews-owners]: code_reviews.md#OWNERS-files
|
||||
@ -475,12 +475,12 @@ formats.
|
||||
[core-principles]: https://www.chromium.org/developers/core-principles
|
||||
[corporate-cla]: https://cla.developers.google.com/about/google-corporate?csw=1
|
||||
[cr-authors]: https://chromium.googlesource.com/chromium/src/+/HEAD/AUTHORS
|
||||
[cr-gitiles]: https://chromium.googlesource.com/chromium/src/+/master/
|
||||
[cr-styleguide]: https://chromium.googlesource.com/chromium/src/+/master/styleguide/styleguide.md
|
||||
[cr-gitiles]: https://chromium.googlesource.com/chromium/src/+/main/
|
||||
[cr-styleguide]: https://chromium.googlesource.com/chromium/src/+/main/styleguide/styleguide.md
|
||||
[crbug-new]: https://bugs.chromium.org/p/chromium/issues/entry
|
||||
[crbug]: https://bugs.chromium.org/p/chromium/issues/list
|
||||
[cros-authors]: https://chromium.googlesource.com/chromium/src/+/master/AUTHORS
|
||||
[cros-dev-guide]: https://chromium.googlesource.com/chromiumos/docs/+/master/developer_guide.md
|
||||
[cros-authors]: https://chromium.googlesource.com/chromium/src/+/main/AUTHORS
|
||||
[cros-dev-guide]: https://chromium.googlesource.com/chromiumos/docs/+/main/developer_guide.md
|
||||
[crrev]: https://chromium-review.googlesource.com
|
||||
[depot-tools-setup]: https://commondatastorage.googleapis.com/chrome-infra-docs/flat/depot_tools/docs/html/depot_tools_tutorial.html#_setting_up
|
||||
[design-doc-template]: https://docs.google.com/document/d/14YBYKgk-uSfjfwpKFlp_omgUq5hwMVazy_M965s_1KA
|
||||
|
||||
@ -7,7 +7,7 @@ bootstrap CrOS services' Mojo connection.
|
||||
|
||||
## Bootstrap a new CrOS service
|
||||
|
||||
D-Bus Mojo Connection Service lives in [//chrome/browser/chromeos/dbus/mojo_connection_service_provider.h](https://chromium.googlesource.com/chromium/src.git/+/master/chrome/browser/chromeos/dbus/mojo_connection_service_provider.h).
|
||||
D-Bus Mojo Connection Service lives in [//chrome/browser/chromeos/dbus/mojo_connection_service_provider.h](https://chromium.googlesource.com/chromium/src.git/+/main/chrome/browser/chromeos/dbus/mojo_connection_service_provider.h).
|
||||
|
||||
Follow the example of CrOS Sensors' [changelist](https://chromium-review.googlesource.com/c/chromium/src/+/2352298).
|
||||
|
||||
@ -47,4 +47,4 @@ be enough for multi-login situations and handling failures. The arguments can
|
||||
also be used to determine if Chromium should accept the request, and which Mojo
|
||||
interface should be used to establish the Mojo channel.
|
||||
|
||||
[MojoConnectionService.conf]: https://chromium.googlesource.com/chromium/src.git/+/master/chrome/browser/chromeos/dbus/org.chromium.MojoConnectionService.conf
|
||||
[MojoConnectionService.conf]: https://chromium.googlesource.com/chromium/src.git/+/main/chrome/browser/chromeos/dbus/org.chromium.MojoConnectionService.conf
|
||||
|
||||
@ -1,10 +1,10 @@
|
||||
# Metadata information for this directory.
|
||||
#
|
||||
# For more information on DIR_METADATA files, see:
|
||||
# https://source.chromium.org/chromium/infra/infra/+/master:go/src/infra/tools/dirmd/README.md
|
||||
# https://source.chromium.org/chromium/infra/infra/+/main:go/src/infra/tools/dirmd/README.md
|
||||
#
|
||||
# For the schema of this file, see Metadata message:
|
||||
# https://source.chromium.org/chromium/infra/infra/+/master:go/src/infra/tools/dirmd/proto/dir_metadata.proto
|
||||
# https://source.chromium.org/chromium/infra/infra/+/main:go/src/infra/tools/dirmd/proto/dir_metadata.proto
|
||||
|
||||
monorail {
|
||||
component: "Internals>Core"
|
||||
|
||||
@ -3,7 +3,7 @@
|
||||
This directory contains chromium project documentation in
|
||||
[Gitiles-flavored Markdown](https://gerrit.googlesource.com/gitiles/+/master/Documentation/markdown.md).
|
||||
It is automatically
|
||||
[rendered by Gitiles](https://chromium.googlesource.com/chromium/src/+/master/docs/).
|
||||
[rendered by Gitiles](https://chromium.googlesource.com/chromium/src/+/main/docs/).
|
||||
|
||||
Documents here have been imported
|
||||
from [the Project site](https://www.chromium.org/developers/design-documents).
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
# Dumping the compiled code from a chrome binary
|
||||
|
||||
[Rendered](https://chromium.googlesource.com/chromium/src/+/master/docs/disassemble_code.md)
|
||||
[Rendered](https://chromium.googlesource.com/chromium/src/+/main/docs/disassemble_code.md)
|
||||
|
||||
## Background
|
||||
|
||||
@ -193,6 +193,6 @@ NextSibling():
|
||||
|
||||
## Further reading
|
||||
|
||||
https://chromium.googlesource.com/chromium/src/+/master/docs/linux/minidump_to_core.md#Source-debugging
|
||||
https://chromium.googlesource.com/chromium/src/+/main/docs/linux/minidump_to_core.md#Source-debugging
|
||||
|
||||
https://www.chromium.org/developers/how-tos/debugging-on-windows
|
||||
|
||||
@ -65,7 +65,7 @@ Don't assume that readers know everything you currently know.
|
||||
|
||||
If you got this far and have some experience with Chromium's code, you'll have figured out that these guidelines are aspirational more than what the world looks like today. So what do we do when working with existing code.
|
||||
|
||||
First off: ***[Documentation changes can be TBRed](https://chromium.googlesource.com/chromium/src/+/master/docs/code_reviews.md#documentation-updates)***. Even in-code changes. If you have discovered something that isn't documented, have figured out how it works and would like to pay it forward, feel free to write something down and check it in.
|
||||
First off: ***[Documentation changes can be TBRed](https://chromium.googlesource.com/chromium/src/+/main/docs/code_reviews.md#documentation-updates)***. Even in-code changes. If you have discovered something that isn't documented, have figured out how it works and would like to pay it forward, feel free to write something down and check it in.
|
||||
|
||||
At the component level, if you are the owner of a component that isn't documented, please add a README.md with content as per the above.
|
||||
|
||||
|
||||
@ -78,7 +78,7 @@ For this purpose, DM Server creates a LaForge account for the user. A LaForge
|
||||
account is a shadow Gaia account with scope limited to the Play Store. To prove
|
||||
the user's identity, a SAML flow is employed with DM Server as service provider
|
||||
and AD (or really any other) as identity provider. The SAML flow is triggered by
|
||||
[ArcActiveDirectoryEnrollmentTokenFetcher](https://source.chromium.org/chromium/chromium/src/+/master:chrome/browser/ash/arc/auth/arc_active_directory_enrollment_token_fetcher.h).
|
||||
[ArcActiveDirectoryEnrollmentTokenFetcher](https://source.chromium.org/chromium/chromium/src/+/main:chrome/browser/ash/arc/auth/arc_active_directory_enrollment_token_fetcher.h).
|
||||
|
||||
### Instructions for Google Employees
|
||||
See [go/cros-ad-test-env](https://goto.google.com/cros-ad-test-env) for setting
|
||||
|
||||
@ -65,7 +65,7 @@ Usually you need a policy when
|
||||
traditionally, and we've seen requests from organizations to
|
||||
explicitly spell out the behavior for all possible values and for
|
||||
when the policy is unset.
|
||||
- See [description_guidelines.md](https://chromium.googlesource.com/chromium/src/+/refs/heads/master/docs/enterprise/description_guidelines.md)
|
||||
- See [description_guidelines.md](https://chromium.googlesource.com/chromium/src/+/refs/heads/main/docs/enterprise/description_guidelines.md)
|
||||
for additional guidelines when creating a description, including how
|
||||
various products should be referenced.
|
||||
3. Create a preference and map the policy value to it.
|
||||
@ -85,9 +85,9 @@ Usually you need a policy when
|
||||
3. Test the mapping by adding policy to
|
||||
[policy_test_cases.json](https://cs.chromium.org/chromium/src/chrome/test/data/policy/policy_test_cases.json?q=policy_test_case).
|
||||
4. iOS platform has its own
|
||||
[configuration_policy_handler_list_factory.mm](https://source.chromium.org/chromium/chromium/src/+/master:ios/chrome/browser/policy/configuration_policy_handler_list_factory.mm)
|
||||
[configuration_policy_handler_list_factory.mm](https://source.chromium.org/chromium/chromium/src/+/main:ios/chrome/browser/policy/configuration_policy_handler_list_factory.mm)
|
||||
and
|
||||
[policy_test_cases.json](https://source.chromium.org/chromium/chromium/src/+/master:ios/chrome/test/data/policy/policy_test_cases.json)
|
||||
[policy_test_cases.json](https://source.chromium.org/chromium/chromium/src/+/main:ios/chrome/test/data/policy/policy_test_cases.json)
|
||||
file.
|
||||
4. Disable the user setting UI when the policy is applied.
|
||||
- If your feature can be controlled by GUI in `chrome://settings`, the
|
||||
|
||||
@ -24,8 +24,8 @@ Before using CBCM Takeout API you will need to do some initial setup:
|
||||
## Running the Script
|
||||
|
||||
You can download the scripts
|
||||
[here](https://chromium.googlesource.com/chromium/src/+/refs/heads/master/docs/enterprise/extension_query.py)
|
||||
or here [here](https://chromium.googlesource.com/chromium/src/+/refs/heads/master/docs/enterprise/extension_query_py2.py)
|
||||
[here](https://chromium.googlesource.com/chromium/src/+/refs/heads/main/docs/enterprise/extension_query.py)
|
||||
or here [here](https://chromium.googlesource.com/chromium/src/+/refs/heads/main/docs/enterprise/extension_query_py2.py)
|
||||
for a python 2.7 compatible version.
|
||||
|
||||
With the service account keys, you can now run the script which uses Google API
|
||||
@ -40,4 +40,4 @@ You can run the script from the command-line: python extension_query.py
|
||||
argument names)
|
||||
|
||||
Example Data output Here is an example of what that data will look like:
|
||||
|
||||
|
||||
|
||||
@ -76,7 +76,7 @@ Change that `#if 0` to `#if 1`, build a debug build, then run in a debugger.
|
||||
The debugger will break when any renderer code sees a GL error, and you should
|
||||
be able to examine the call stack to find the issue.
|
||||
|
||||
[gles2_implementation.h]: https://chromium.googlesource.com/chromium/src/+/master/gpu/command_buffer/client/gles2_implementation.h
|
||||
[gles2_implementation.h]: https://chromium.googlesource.com/chromium/src/+/main/gpu/command_buffer/client/gles2_implementation.h
|
||||
|
||||
### Labeling your calls
|
||||
|
||||
|
||||
@ -43,9 +43,9 @@ the previous configuration where new steps were added blindly, and could cause
|
||||
failures on the tryservers. For more details about the configuration of the
|
||||
bots, see the [GPU bot details].
|
||||
|
||||
[recipe framework]: https://chromium.googlesource.com/external/github.com/luci/recipes-py/+/master/doc/user_guide.md
|
||||
[recipes/chromium]: https://chromium.googlesource.com/chromium/tools/build/+/master/scripts/slave/recipes/chromium.py
|
||||
[recipes/chromium_trybot]: https://chromium.googlesource.com/chromium/tools/build/+/master/scripts/slave/recipes/chromium_trybot.py
|
||||
[recipe framework]: https://chromium.googlesource.com/external/github.com/luci/recipes-py/+/main/doc/user_guide.md
|
||||
[recipes/chromium]: https://chromium.googlesource.com/chromium/tools/build/+/main/scripts/slave/recipes/chromium.py
|
||||
[recipes/chromium_trybot]: https://chromium.googlesource.com/chromium/tools/build/+/main/scripts/slave/recipes/chromium_trybot.py
|
||||
[GPU bot details]: gpu_testing_bot_details.md
|
||||
|
||||
The physical hardware for the GPU bots lives in the Swarming pool\*. The
|
||||
@ -159,7 +159,7 @@ If you find it necessary to try patches against other sub-repositories than
|
||||
Chromium (`src/`) and ANGLE (`src/third_party/angle/`), please
|
||||
[file a bug](http://crbug.com/new) with component Internals\>GPU\>Testing.
|
||||
|
||||
[ANGLE project]: https://chromium.googlesource.com/angle/angle/+/master/README.md
|
||||
[ANGLE project]: https://chromium.googlesource.com/angle/angle/+/main/README.md
|
||||
[tryserver.chromium.angle]: https://build.chromium.org/p/tryserver.chromium.angle/waterfall
|
||||
[file a bug]: http://crbug.com/new
|
||||
|
||||
@ -505,15 +505,15 @@ invoke it via:
|
||||
The tests that are run by the GPU bots are described by a couple of JSON files
|
||||
in the Chromium workspace:
|
||||
|
||||
* [`chromium.gpu.json`](https://chromium.googlesource.com/chromium/src/+/master/testing/buildbot/chromium.gpu.json)
|
||||
* [`chromium.gpu.fyi.json`](https://chromium.googlesource.com/chromium/src/+/master/testing/buildbot/chromium.gpu.fyi.json)
|
||||
* [`chromium.gpu.json`](https://chromium.googlesource.com/chromium/src/+/main/testing/buildbot/chromium.gpu.json)
|
||||
* [`chromium.gpu.fyi.json`](https://chromium.googlesource.com/chromium/src/+/main/testing/buildbot/chromium.gpu.fyi.json)
|
||||
|
||||
These files are autogenerated by the following script:
|
||||
|
||||
* [`generate_buildbot_json.py`](https://chromium.googlesource.com/chromium/src/+/master/testing/buildbot/generate_buildbot_json.py)
|
||||
* [`generate_buildbot_json.py`](https://chromium.googlesource.com/chromium/src/+/main/testing/buildbot/generate_buildbot_json.py)
|
||||
|
||||
This script is documented in
|
||||
[`testing/buildbot/README.md`](https://chromium.googlesource.com/chromium/src/+/master/testing/buildbot/README.md). The
|
||||
[`testing/buildbot/README.md`](https://chromium.googlesource.com/chromium/src/+/main/testing/buildbot/README.md). The
|
||||
JSON files are parsed by the chromium and chromium_trybot recipes, and describe
|
||||
two basic types of tests:
|
||||
|
||||
|
||||
@ -66,7 +66,7 @@ differences in behavior between the tryservers and waterfall bots. Since the
|
||||
tryservers mirror waterfall bots, if the waterfall bot is working, the
|
||||
tryserver must almost inherently be working as well.
|
||||
|
||||
[chromium_trybot.py]: https://chromium.googlesource.com/chromium/tools/build/+/master/recipes/recipes/chromium_trybot.py
|
||||
[chromium_trybot.py]: https://chromium.googlesource.com/chromium/tools/build/+/main/recipes/recipes/chromium_trybot.py
|
||||
|
||||
There are some GPU configurations on the waterfall backed by only one machine,
|
||||
or a very small number of machines in the Swarming pool. A few examples are:
|
||||
@ -102,11 +102,11 @@ background on [Isolates] and [Swarming].
|
||||
your target. Find a similar target to yours in order to determine the
|
||||
`type`. The type is referenced in [`src/tools/mb/mb.py`][mb.py].
|
||||
|
||||
[testing/test.gni]: https://chromium.googlesource.com/chromium/src/+/master/testing/test.gni
|
||||
[gpu/BUILD.gn]: https://chromium.googlesource.com/chromium/src/+/master/gpu/BUILD.gn
|
||||
[chrome/test/BUILD.gn]: https://chromium.googlesource.com/chromium/src/+/master/chrome/test/BUILD.gn
|
||||
[gn_isolate_map.pyl]: https://chromium.googlesource.com/chromium/src/+/master/testing/buildbot/gn_isolate_map.pyl
|
||||
[mb.py]: https://chromium.googlesource.com/chromium/src/+/master/tools/mb/mb.py
|
||||
[testing/test.gni]: https://chromium.googlesource.com/chromium/src/+/main/testing/test.gni
|
||||
[gpu/BUILD.gn]: https://chromium.googlesource.com/chromium/src/+/main/gpu/BUILD.gn
|
||||
[chrome/test/BUILD.gn]: https://chromium.googlesource.com/chromium/src/+/main/chrome/test/BUILD.gn
|
||||
[gn_isolate_map.pyl]: https://chromium.googlesource.com/chromium/src/+/main/testing/buildbot/gn_isolate_map.pyl
|
||||
[mb.py]: https://chromium.googlesource.com/chromium/src/+/main/tools/mb/mb.py
|
||||
|
||||
At this point you can build and upload your isolate to the isolate server.
|
||||
|
||||
@ -177,9 +177,9 @@ In the [`tools/build`][tools/build] workspace:
|
||||
specific hardware configuration.
|
||||
|
||||
[tools/build]: https://chromium.googlesource.com/chromium/tools/build/
|
||||
[chromium_gpu.py]: https://chromium.googlesource.com/chromium/tools/build/+/master/recipes/recipe_modules/chromium_tests/builders/chromium_gpu.py
|
||||
[chromium_gpu_fyi.py]: https://chromium.googlesource.com/chromium/tools/build/+/master/recipes/recipe_modules/chromium_tests/builders/chromium_gpu_fyi.py
|
||||
[trybots.py]: https://chromium.googlesource.com/chromium/tools/build/+/master/recipes/recipe_modules/chromium_tests/trybots.py
|
||||
[chromium_gpu.py]: https://chromium.googlesource.com/chromium/tools/build/+/main/recipes/recipe_modules/chromium_tests/builders/chromium_gpu.py
|
||||
[chromium_gpu_fyi.py]: https://chromium.googlesource.com/chromium/tools/build/+/main/recipes/recipe_modules/chromium_tests/builders/chromium_gpu_fyi.py
|
||||
[trybots.py]: https://chromium.googlesource.com/chromium/tools/build/+/main/recipes/recipe_modules/chromium_tests/trybots.py
|
||||
|
||||
In the [`chromium/src`][chromium/src] workspace:
|
||||
|
||||
@ -213,21 +213,21 @@ In the [`chromium/src`][chromium/src] workspace:
|
||||
how builds are triggered, which VMs or machines are used for the
|
||||
builder itself, i.e. for compilation and scheduling swarmed tasks
|
||||
on GPU hardware. See
|
||||
[README.md](https://chromium.googlesource.com/chromium/src/+/master/infra/config/README.md)
|
||||
[README.md](https://chromium.googlesource.com/chromium/src/+/main/infra/config/README.md)
|
||||
in this directory for up to date information.
|
||||
|
||||
[chromium/src]: https://chromium.googlesource.com/chromium/src/
|
||||
[src/testing/buildbot]: https://chromium.googlesource.com/chromium/src/+/master/testing/buildbot
|
||||
[src/infra/config]: https://chromium.googlesource.com/chromium/src/+/master/infra/config
|
||||
[chromium.gpu.json]: https://chromium.googlesource.com/chromium/src/+/master/testing/buildbot/chromium.gpu.json
|
||||
[chromium.gpu.fyi.json]: https://chromium.googlesource.com/chromium/src/+/master/testing/buildbot/chromium.gpu.fyi.json
|
||||
[gn_isolate_map.pyl]: https://chromium.googlesource.com/chromium/src/+/master/testing/buildbot/gn_isolate_map.pyl
|
||||
[mb_config.pyl]: https://chromium.googlesource.com/chromium/src/+/master/tools/mb/mb_config.pyl
|
||||
[generate_buildbot_json.py]: https://chromium.googlesource.com/chromium/src/+/master/testing/buildbot/generate_buildbot_json.py
|
||||
[mixins.pyl]: https://chromium.googlesource.com/chromium/src/+/master/testing/buildbot/mixins.pyl
|
||||
[waterfalls.pyl]: https://chromium.googlesource.com/chromium/src/+/master/testing/buildbot/waterfalls.pyl
|
||||
[test_suites.pyl]: https://chromium.googlesource.com/chromium/src/+/master/testing/buildbot/test_suites.pyl
|
||||
[test_suite_exceptions.pyl]: https://chromium.googlesource.com/chromium/src/+/master/testing/buildbot/test_suite_exceptions.pyl
|
||||
[src/testing/buildbot]: https://chromium.googlesource.com/chromium/src/+/main/testing/buildbot
|
||||
[src/infra/config]: https://chromium.googlesource.com/chromium/src/+/main/infra/config
|
||||
[chromium.gpu.json]: https://chromium.googlesource.com/chromium/src/+/main/testing/buildbot/chromium.gpu.json
|
||||
[chromium.gpu.fyi.json]: https://chromium.googlesource.com/chromium/src/+/main/testing/buildbot/chromium.gpu.fyi.json
|
||||
[gn_isolate_map.pyl]: https://chromium.googlesource.com/chromium/src/+/main/testing/buildbot/gn_isolate_map.pyl
|
||||
[mb_config.pyl]: https://chromium.googlesource.com/chromium/src/+/main/tools/mb/mb_config.pyl
|
||||
[generate_buildbot_json.py]: https://chromium.googlesource.com/chromium/src/+/main/testing/buildbot/generate_buildbot_json.py
|
||||
[mixins.pyl]: https://chromium.googlesource.com/chromium/src/+/main/testing/buildbot/mixins.pyl
|
||||
[waterfalls.pyl]: https://chromium.googlesource.com/chromium/src/+/main/testing/buildbot/waterfalls.pyl
|
||||
[test_suites.pyl]: https://chromium.googlesource.com/chromium/src/+/main/testing/buildbot/test_suites.pyl
|
||||
[test_suite_exceptions.pyl]: https://chromium.googlesource.com/chromium/src/+/main/testing/buildbot/test_suite_exceptions.pyl
|
||||
[README for generate_buildbot_json.py]: ../../testing/buildbot/README.md
|
||||
|
||||
In the [`infradata/config`][infradata/config] workspace (Google internal only,
|
||||
@ -246,11 +246,11 @@ sorry):
|
||||
triggered trybots.
|
||||
|
||||
[infradata/config]: https://chrome-internal.googlesource.com/infradata/config
|
||||
[gpu.star]: https://chrome-internal.googlesource.com/infradata/config/+/master/configs/chromium-swarm/starlark/bots/chromium/gpu.star
|
||||
[chromium.star]: https://chrome-internal.googlesource.com/infradata/config/+/master/configs/chromium-swarm/starlark/bots/chromium/chromium.star
|
||||
[pools.cfg]: https://chrome-internal.googlesource.com/infradata/config/+/master/configs/chromium-swarm/pools.cfg
|
||||
[main.star]: https://chrome-internal.googlesource.com/infradata/config/+/master/main.star
|
||||
[vms.cfg]: https://chrome-internal.googlesource.com/infradata/config/+/master/configs/gce-provider/vms.cfg
|
||||
[gpu.star]: https://chrome-internal.googlesource.com/infradata/config/+/main/configs/chromium-swarm/starlark/bots/chromium/gpu.star
|
||||
[chromium.star]: https://chrome-internal.googlesource.com/infradata/config/+/main/configs/chromium-swarm/starlark/bots/chromium/chromium.star
|
||||
[pools.cfg]: https://chrome-internal.googlesource.com/infradata/config/+/main/configs/chromium-swarm/pools.cfg
|
||||
[main.star]: https://chrome-internal.googlesource.com/infradata/config/+/main/main.star
|
||||
[vms.cfg]: https://chrome-internal.googlesource.com/infradata/config/+/main/configs/gce-provider/vms.cfg
|
||||
|
||||
## Walkthroughs of various maintenance scenarios
|
||||
|
||||
@ -261,7 +261,7 @@ maintaining the GPU bots, and how they'd be addressed.
|
||||
|
||||
This is described in [Adding new tests to the GPU bots].
|
||||
|
||||
[Adding new tests to the GPU bots]: https://chromium.googlesource.com/chromium/src/+/master/docs/gpu/gpu_testing.md#Adding-New-Tests-to-the-GPU-Bots
|
||||
[Adding new tests to the GPU bots]: https://chromium.googlesource.com/chromium/src/+/main/docs/gpu/gpu_testing.md#Adding-New-Tests-to-the-GPU-Bots
|
||||
|
||||
### How to set up new virtual machine instances
|
||||
|
||||
@ -486,14 +486,14 @@ Attempting to set up the builder/tester pair without first landing the
|
||||
[`tools/build`][tools/build] CL for the new builder will result in things
|
||||
breaking as seen in [this bug][misconfigured builder bug].
|
||||
|
||||
[How to add a new manually-triggered trybot]: https://chromium.googlesource.com/chromium/src/+/master/docs/gpu/gpu_testing_bot_details.md#How-to-add-a-new-manually_triggered-trybot
|
||||
[How to add a new manually-triggered trybot]: https://chromium.googlesource.com/chromium/src/+/main/docs/gpu/gpu_testing_bot_details.md#How-to-add-a-new-manually_triggered-trybot
|
||||
|
||||
[ci.star]: https://chromium.googlesource.com/chromium/src/+/master/infra/config/subprojects/ci.star
|
||||
[chromium.gpu.star]: https://chromium.googlesource.com/chromium/src/+/master/infra/config/consoles/chromium.gpu.star
|
||||
[chromium.gpu.fyi.star]: https://chromium.googlesource.com/chromium/src/+/master/infra/config/consoles/chromium.gpu.fyi.star
|
||||
[cr-buildbucket.cfg]: https://chromium.googlesource.com/chromium/src/+/master/infra/config/generated/cr-buildbucket.cfg
|
||||
[luci-scheduler.cfg]: https://chromium.googlesource.com/chromium/src/+/master/infra/config/generated/luci-scheduler.cfg
|
||||
[luci-milo.cfg]: https://chromium.googlesource.com/chromium/src/+/master/infra/config/generated/luci-milo.cfg
|
||||
[ci.star]: https://chromium.googlesource.com/chromium/src/+/main/infra/config/subprojects/ci.star
|
||||
[chromium.gpu.star]: https://chromium.googlesource.com/chromium/src/+/main/infra/config/consoles/chromium.gpu.star
|
||||
[chromium.gpu.fyi.star]: https://chromium.googlesource.com/chromium/src/+/main/infra/config/consoles/chromium.gpu.fyi.star
|
||||
[cr-buildbucket.cfg]: https://chromium.googlesource.com/chromium/src/+/main/infra/config/generated/cr-buildbucket.cfg
|
||||
[luci-scheduler.cfg]: https://chromium.googlesource.com/chromium/src/+/main/infra/config/generated/luci-scheduler.cfg
|
||||
[luci-milo.cfg]: https://chromium.googlesource.com/chromium/src/+/main/infra/config/generated/luci-milo.cfg
|
||||
[GPU FYI Win Builder]: https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/GPU%20FYI%20Win%20Builder
|
||||
[misconfigured builder bug]: https://bugs.chromium.org/p/chromium/issues/detail?id=1163657
|
||||
|
||||
@ -526,7 +526,7 @@ Even for GPU types that have CQ trybots, it is convenient to have
|
||||
manually-triggered trybots as well, since the CQ trybot often runs on more than
|
||||
one GPU type, or some test suites which run on CI bot can be disabled on CQ
|
||||
trybot (when the CQ bot mirrors a
|
||||
[fake bot](https://chromium.googlesource.com/chromium/src/+/master/docs/gpu/gpu_testing_bot_details.md#how-to-add-a-new-try-bot-that-runs-a-subset-of-tests-or-extra-tests)).
|
||||
[fake bot](https://chromium.googlesource.com/chromium/src/+/main/docs/gpu/gpu_testing_bot_details.md#how-to-add-a-new-try-bot-that-runs-a-subset-of-tests-or-extra-tests)).
|
||||
Thus, all CI bots in `chromium.gpu` and `chromium.gpu.fyi` have corresponding
|
||||
manually-triggered trybots, except a few which don't have enough hardware
|
||||
to support it. A manually-triggered trybot should be added at the same time
|
||||
@ -592,9 +592,9 @@ should be possible to send a CL to it.
|
||||
mentioned at the bottom of the "Choose tryjobs" pop-up. Contact the
|
||||
chrome-infra team if this doesn't work as expected.)
|
||||
|
||||
[gpu.try.star]: https://chromium.googlesource.com/chromium/src/+/master/infra/config/subprojects/gpu.try.star
|
||||
[luci.chromium.try.star]: https://chromium.googlesource.com/chromium/src/+/master/infra/config/consoles/luci.chromium.try.star
|
||||
[tryserver.chromium.win.star]: https://chromium.googlesource.com/chromium/src/+/master/infra/config/consoles/tryserver.chromium.win.star
|
||||
[gpu.try.star]: https://chromium.googlesource.com/chromium/src/+/main/infra/config/subprojects/gpu.try.star
|
||||
[luci.chromium.try.star]: https://chromium.googlesource.com/chromium/src/+/main/infra/config/consoles/luci.chromium.try.star
|
||||
[tryserver.chromium.win.star]: https://chromium.googlesource.com/chromium/src/+/main/infra/config/consoles/tryserver.chromium.win.star
|
||||
|
||||
|
||||
### How to add a new try bot that runs a subset of tests or extra tests
|
||||
@ -655,8 +655,8 @@ Win10 Release (CoolNewGPUType)".
|
||||
1. After your CLs land you should be able to find and run `win-myproject-rel` on CLs
|
||||
using Choose Trybots in Gerrit.
|
||||
|
||||
[scheduler-noop-jobs.star]: https://chromium.googlesource.com/chromium/src/+/master/infra/config/generators/scheduler-noop-jobs.star
|
||||
[try.star]: https://chromium.googlesource.com/chromium/src/+/master/infra/config/subprojects/try.star
|
||||
[scheduler-noop-jobs.star]: https://chromium.googlesource.com/chromium/src/+/main/infra/config/generators/scheduler-noop-jobs.star
|
||||
[try.star]: https://chromium.googlesource.com/chromium/src/+/main/infra/config/subprojects/try.star
|
||||
|
||||
|
||||
### How to test and deploy a driver and/or OS update
|
||||
|
||||
@ -61,7 +61,7 @@ so on. The waterfalls we’re interested in are:
|
||||
[Chromium GPU FYI]: https://ci.chromium.org/p/chromium/g/chromium.gpu.fyi/console?reload=120
|
||||
[Chromium SwANGLE]: https://ci.chromium.org/p/chromium/g/chromium.swangle/console?reload=120
|
||||
[ANGLE tryservers]: https://build.chromium.org/p/tryserver.chromium.angle/waterfall
|
||||
[ANGLE Wrangler]: https://chromium.googlesource.com/angle/angle/+/master/infra/ANGLEWrangling.md
|
||||
[ANGLE Wrangler]: https://chromium.googlesource.com/angle/angle/+/main/infra/ANGLEWrangling.md
|
||||
|
||||
## Test Suites
|
||||
|
||||
@ -279,7 +279,7 @@ shift, and a calendar appointment.
|
||||
modifier][gtest-DISABLED] to suppress any failures if necessary.
|
||||
|
||||
[Sheriff-O-Matic]: https://sheriff-o-matic.appspot.com/chromium.gpu
|
||||
[trim culprit cls]: https://source.chromium.org/chromium/chromium/src/+/master:content/test/gpu/trim_culprit_cls.py
|
||||
[trim culprit cls]: https://source.chromium.org/chromium/chromium/src/+/main:content/test/gpu/trim_culprit_cls.py
|
||||
[tree sheriffing page]: https://sites.google.com/a/chromium.org/dev/developers/tree-sheriffs
|
||||
[linux-rel]: https://ci.chromium.org/p/chromium/builders/luci.chromium.try/linux-rel
|
||||
[luci.chromium.try]: https://ci.chromium.org/p/chromium/g/luci.chromium.try/builders
|
||||
@ -293,10 +293,10 @@ https://ci.chromium.org/p/chromium/builders/luci.chromium.try/win7-rel
|
||||
[Swarming Server Stats]: https://chromium-swarm.appspot.com/stats
|
||||
[gold less common failures]: gpu_pixel_testing_with_gold.md#Triaging-Less-Common-Failures
|
||||
[Chrome Internal GPU Pixel Wrangling Instructions]: https://sites.google.com/a/google.com/client3d/documents/chrome-internal-gpu-pixel-wrangling-instructions
|
||||
[src/content/test/gpu/gpu_tests/test_expectations]: https://chromium.googlesource.com/chromium/src/+/master/content/test/gpu/gpu_tests/test_expectations
|
||||
[webgl_conformance_expectations.txt]: https://chromium.googlesource.com/chromium/src/+/master/content/test/gpu/gpu_tests/test_expectations/webgl_conformance_expectations.txt
|
||||
[gpu_process_expectations.txt]: https://chromium.googlesource.com/chromium/src/+/master/content/test/gpu/gpu_tests/test_expectations/gpu_process_expectations.txt
|
||||
[pixel_expectations.txt]: https://chromium.googlesource.com/chromium/src/+/master/content/test/gpu/gpu_tests/test_expectations/pixel_expectations.txt
|
||||
[src/content/test/gpu/gpu_tests/test_expectations]: https://chromium.googlesource.com/chromium/src/+/main/content/test/gpu/gpu_tests/test_expectations
|
||||
[webgl_conformance_expectations.txt]: https://chromium.googlesource.com/chromium/src/+/main/content/test/gpu/gpu_tests/test_expectations/webgl_conformance_expectations.txt
|
||||
[gpu_process_expectations.txt]: https://chromium.googlesource.com/chromium/src/+/main/content/test/gpu/gpu_tests/test_expectations/gpu_process_expectations.txt
|
||||
[pixel_expectations.txt]: https://chromium.googlesource.com/chromium/src/+/main/content/test/gpu/gpu_tests/test_expectations/pixel_expectations.txt
|
||||
[stamping out flakiness]: gpu_testing.md#Stamping-out-Flakiness
|
||||
[gtest-DISABLED]: https://github.com/google/googletest/blob/master/googletest/docs/AdvancedGuide.md#temporarily-disabling-tests
|
||||
[rendering_representative_perf_tests]: ../testing/rendering_representative_perf_tests.md#Updating-Expectations
|
||||
|
||||
@ -35,5 +35,5 @@ When running the **chrome** executable from the command line, SwiftShader can be
|
||||
> **\-\-use-gl=swiftshader**
|
||||
4) As the WebGL fallback, legacy SwiftShader Open GL ES libraries
|
||||
>**\-\-use-gl=swiftshader-webgl**
|
||||
5) As the Vulkan driver (requires the [enable_swiftshader_vulkan](https://source.chromium.org/chromium/chromium/src/+/master:gpu/vulkan/features.gni;l=16) feature)
|
||||
5) As the Vulkan driver (requires the [enable_swiftshader_vulkan](https://source.chromium.org/chromium/chromium/src/+/main:gpu/vulkan/features.gni;l=16) feature)
|
||||
>**--use-vulkan=swiftshader**
|
||||
|
||||
@ -14,9 +14,9 @@ ChromeOS is a downstream client via the [libva] package, with packaged backends
|
||||
for e.g. both [Intel] and [AMD].
|
||||
|
||||
[VaAPI GitHub repository]: https://github.com/intel/libva
|
||||
[libva]: https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/master/x11-libs/libva/
|
||||
[Intel]: https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/master/x11-libs/libva-intel-driver/
|
||||
[AMD]: https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/master/media-libs/libva-amdgpu-driver/
|
||||
[libva]: https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/main/x11-libs/libva/
|
||||
[Intel]: https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/main/x11-libs/libva-intel-driver/
|
||||
[AMD]: https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/main/media-libs/libva-amdgpu-driver/
|
||||
|
||||
## Tracing VaAPI video decoding
|
||||
|
||||
@ -141,7 +141,7 @@ As can be seen, `pkg` ~= `pp0` + `pp1` + 1W, this extra watt is the cost of all
|
||||
the associated silicon, e.g. bridges, bus controllers, caches, and the media
|
||||
processing engine.
|
||||
|
||||
[`dump_intel_rapl_consumption`]: https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/tools/dump_intel_rapl_consumption.cc
|
||||
[`dump_intel_rapl_consumption`]: https://chromium.googlesource.com/chromiumos/platform2/+/main/power_manager/tools/dump_intel_rapl_consumption.cc
|
||||
[video]: https://commons.wikimedia.org/wiki/File:Big_Buck_Bunny_4K.webm
|
||||
[go/power-consumption-meas-in-intel]: http://go/power-consumption-meas-in-intel
|
||||
|
||||
@ -160,7 +160,7 @@ and under Debian systems ([vainfo]). `vainfo` will try to load the appropriate
|
||||
backend driver for the system and/or GPUs and fail if it cannot find/load it.
|
||||
|
||||
[libva-utils]: https://github.com/intel/libva-utils
|
||||
[media-video/libva-utils]: https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/master/media-video/libva-utils
|
||||
[media-video/libva-utils]: https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/main/media-video/libva-utils
|
||||
[vainfo]: https://packages.debian.org/sid/main/vainfo
|
||||
|
||||
### <a name="verify-vaapi"></a> Verify the VaAPI supports and/or uses a given codec
|
||||
|
||||
@ -9,7 +9,7 @@ debugging. It consists of 4 components:
|
||||
`ui/views/debug_utils.h`),
|
||||
1. a custom debugger command
|
||||
- For GDB, see
|
||||
[gdbinit](https://chromium.googlesource.com/chromium/src/+/master/docs/gdbinit.md),
|
||||
[gdbinit](https://chromium.googlesource.com/chromium/src/+/main/docs/gdbinit.md),
|
||||
- For LLDB, use `tools/lldb/lldb_viewg.py`
|
||||
- For other debuggers, it should be relatively easy to adapt the
|
||||
above scripts.
|
||||
@ -24,7 +24,7 @@ To use the tool,
|
||||
1. Make sure you have 'dot' installed (part of graphViz),
|
||||
1. run gdb/lldb on your build and
|
||||
1. For GDB see
|
||||
[gdbinit](https://chromium.googlesource.com/chromium/src/+/master/docs/gdbinit.md),
|
||||
[gdbinit](https://chromium.googlesource.com/chromium/src/+/main/docs/gdbinit.md),
|
||||
1. For LLDB `command script import tools/lldb/lldb_viewg.py` (this can
|
||||
be done automatically in `.lldbinit`),
|
||||
1. stop at any breakpoint inside class `View` (or any derived class), and
|
||||
|
||||
@ -362,7 +362,7 @@ A BSP tree is used to sort and intersect these against each other in the same 3d
|
||||
|
||||
## Glossary
|
||||
|
||||
See: [cc/README.md](https://chromium.googlesource.com/chromium/src/+/master/cc/README.md#glossaries)
|
||||
See: [cc/README.md](https://chromium.googlesource.com/chromium/src/+/main/cc/README.md#glossaries)
|
||||
|
||||
## Other Resources
|
||||
|
||||
|
||||
@ -12,7 +12,7 @@ For example, if you want to use the flag in src/content, you should add a base::
|
||||
* [content/public/common/content_features.h](https://cs.chromium.org/chromium/src/content/public/common/content_features.h)
|
||||
|
||||
If you want to use the flag in blink, you should also read
|
||||
[Runtime Enable Features](https://chromium.googlesource.com/chromium/src/+/master/third_party/blink/renderer/platform/RuntimeEnabledFeatures.md).
|
||||
[Runtime Enable Features](https://chromium.googlesource.com/chromium/src/+/main/third_party/blink/renderer/platform/RuntimeEnabledFeatures.md).
|
||||
|
||||
You can refer to [this CL](https://chromium-review.googlesource.com/c/554510/) and [this document](initialize_blink_features.md)
|
||||
to see
|
||||
@ -22,7 +22,7 @@ to see
|
||||
[[2](https://chromium-review.googlesource.com/c/554510/8/content/public/common/content_features.h)]
|
||||
2. how to use it
|
||||
[[1](https://chromium-review.googlesource.com/c/554510/8/content/common/service_worker/service_worker_utils.cc#153)]
|
||||
3. how to wire your new base::Feature to a blink runtime feature[[1](https://chromium.googlesource.com/chromium/src/+/master/docs/initialize_blink_features.md)]
|
||||
3. how to wire your new base::Feature to a blink runtime feature[[1](https://chromium.googlesource.com/chromium/src/+/main/docs/initialize_blink_features.md)]
|
||||
4. how to use it in blink
|
||||
[[1](https://chromium-review.googlesource.com/c/554510/8/third_party/blnk/renderere/core/workers/worker_thread.cc)]
|
||||
|
||||
|
||||
@ -1,10 +1,10 @@
|
||||
# Metadata information for this directory.
|
||||
#
|
||||
# For more information on DIR_METADATA files, see:
|
||||
# https://source.chromium.org/chromium/infra/infra/+/master:go/src/infra/tools/dirmd/README.md
|
||||
# https://source.chromium.org/chromium/infra/infra/+/main:go/src/infra/tools/dirmd/README.md
|
||||
#
|
||||
# For the schema of this file, see Metadata message:
|
||||
# https://source.chromium.org/chromium/infra/infra/+/master:go/src/infra/tools/dirmd/proto/dir_metadata.proto
|
||||
# https://source.chromium.org/chromium/infra/infra/+/main:go/src/infra/tools/dirmd/proto/dir_metadata.proto
|
||||
|
||||
monorail {
|
||||
component: "Blink>Image"
|
||||
|
||||
@ -1,10 +1,10 @@
|
||||
# Metadata information for this directory.
|
||||
#
|
||||
# For more information on DIR_METADATA files, see:
|
||||
# https://source.chromium.org/chromium/infra/infra/+/master:go/src/infra/tools/dirmd/README.md
|
||||
# https://source.chromium.org/chromium/infra/infra/+/main:go/src/infra/tools/dirmd/README.md
|
||||
#
|
||||
# For the schema of this file, see Metadata message:
|
||||
# https://source.chromium.org/chromium/infra/infra/+/master:go/src/infra/tools/dirmd/proto/dir_metadata.proto
|
||||
# https://source.chromium.org/chromium/infra/infra/+/main:go/src/infra/tools/dirmd/proto/dir_metadata.proto
|
||||
|
||||
monorail {
|
||||
component: "Infra>Client>Chrome"
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
# Dealing with stack traces that involve inlined code
|
||||
|
||||
[Rendered](https://chromium.googlesource.com/chromium/src/+/master/docs/inlined_stack_traces.md)
|
||||
[Rendered](https://chromium.googlesource.com/chromium/src/+/main/docs/inlined_stack_traces.md)
|
||||
|
||||
Sometimes we get crashes with stack traces that are hard to use.
|
||||
They may contain the file and line-number for the inlined method
|
||||
@ -57,7 +57,7 @@ so the code we are interested in is at `0x17c3a78`.
|
||||
|
||||
## Dumping the compiled code
|
||||
|
||||
[This doc](https://chromium.googlesource.com/chromium/src/+/master/docs/disassemble_code.md) describes how to dump the assembler code for a method from a binary.
|
||||
[This doc](https://chromium.googlesource.com/chromium/src/+/main/docs/disassemble_code.md) describes how to dump the assembler code for a method from a binary.
|
||||
In this example, it's a crash from an Android Chrome binary.
|
||||
Only Googlers have access to the unstripped binary files needed for this example
|
||||
but the steps are generic and work with any version of Chromium
|
||||
|
||||
@ -372,14 +372,14 @@ If `artifact` is a directory, you must specify `"compress": true`.
|
||||
[gitiles]: https://gerrit.googlesource.com/gitiles
|
||||
[GN]: ../../tools/gn
|
||||
[instructions]: ./build_instructions.md
|
||||
[iOS recipes]: https://chromium.googlesource.com/chromium/tools/build/+/master/scripts/slave/recipes/ios
|
||||
[iOS recipes]: https://chromium.googlesource.com/chromium/tools/build/+/main/scripts/slave/recipes/ios
|
||||
[iOS simulator]: ../../testing/iossim
|
||||
[recipe module]: https://chromium.googlesource.com/chromium/tools/build/+/master/scripts/slave/recipe_modules/ios
|
||||
[recipe module]: https://chromium.googlesource.com/chromium/tools/build/+/main/scripts/slave/recipe_modules/ios
|
||||
[recipes]: https://chromium.googlesource.com/infra/infra/+/HEAD/doc/users/recipes.md
|
||||
[simulator]: https://developer.apple.com/library/content/documentation/IDEs/Conceptual/iOS_Simulator_Guide/Introduction/Introduction.html
|
||||
[src/ios/build/bots]: ../../ios/build/bots
|
||||
[src/ios/build/bots/scripts]: ../../ios/build/bots/scripts
|
||||
[swarming]: https://chromium.googlesource.com/infra/luci/luci-py/+/master/appengine/swarming/
|
||||
[swarming]: https://chromium.googlesource.com/infra/luci/luci-py/+/main/appengine/swarming/
|
||||
[swarming server]: https://chromium-swarm.appspot.com
|
||||
[test runner]: ../../ios/build/bots/scripts/test_runner.py
|
||||
[tools/build]: https://chromium.googlesource.com/chromium/tools/build
|
||||
|
||||
@ -17,7 +17,7 @@ windows with the same number. You can use
|
||||
unlikely case it is needed. Depending on the needs of the test, you can decide
|
||||
on how to proceed, for example wanting to keep the left window as 0 and the
|
||||
right window as 1. See
|
||||
[`[BrowserViewControllerTestCase testMultiWindowURLLoading]`](https://source.chromium.org/chromium/chromium/src/+/master:ios/chrome/browser/ui/browser_view/browser_view_controller_egtest.mm;l=209)
|
||||
[`[BrowserViewControllerTestCase testMultiWindowURLLoading]`](https://source.chromium.org/chromium/chromium/src/+/main:ios/chrome/browser/ui/browser_view/browser_view_controller_egtest.mm;l=209)
|
||||
as an example of this.
|
||||
|
||||
## Helpers
|
||||
@ -28,7 +28,7 @@ single window counterpart versions but with an extra `inWindowWithNumber`
|
||||
parameter.
|
||||
|
||||
The helpers all live in
|
||||
[ios/chrome/test/earl_grey/chrome_earl_grey.h](https://source.chromium.org/chromium/chromium/src/+/master:ios/chrome/test/earl_grey/chrome_earl_grey.h)
|
||||
[ios/chrome/test/earl_grey/chrome_earl_grey.h](https://source.chromium.org/chromium/chromium/src/+/main:ios/chrome/test/earl_grey/chrome_earl_grey.h)
|
||||
|
||||
### Window Management
|
||||
|
||||
@ -182,7 +182,7 @@ Thanks to the root matcher, a limited number of matchers, require the window
|
||||
number to be specified. `WindowWithNumber` is useful as a root matcher and
|
||||
`MatchInWindowWithNumber` if you want to match without using a root matcher:
|
||||
|
||||
[ios/chrome/test/earl_grey/chrome_matchers.h](https://source.chromium.org/chromium/chromium/src/+/master:ios/chrome/test/earl_grey/chrome_matchers.h)
|
||||
[ios/chrome/test/earl_grey/chrome_matchers.h](https://source.chromium.org/chromium/chromium/src/+/main:ios/chrome/test/earl_grey/chrome_matchers.h)
|
||||
|
||||
```
|
||||
// Matcher for a window with a given number.
|
||||
@ -215,7 +215,7 @@ Drag and drop. But XCUI is good at that, so there are two new
|
||||
client-side-triggered actions that can be used, that work across multiple
|
||||
windows:
|
||||
|
||||
[ios/chrome/test/earl_grey/chrome_xcui_actions.h](https://source.chromium.org/chromium/chromium/src/+/master:ios/chrome/test/earl_grey/chrome_xcui_actions.h)
|
||||
[ios/chrome/test/earl_grey/chrome_xcui_actions.h](https://source.chromium.org/chromium/chromium/src/+/main:ios/chrome/test/earl_grey/chrome_xcui_actions.h)
|
||||
|
||||
```
|
||||
// Action (XCUI, hence local) to long press a cell item with
|
||||
|
||||
@ -197,7 +197,7 @@ The invocation args are logged. You can find the latest arg format at the
|
||||
beginning of stdout from an infra test shard if the above doesn't work.
|
||||
|
||||
|
||||
[config the bots]: https://chromium.googlesource.com/chromium/src/testing/+/refs/heads/master/buildbot/README.md#buildbot-testing-configuration-files
|
||||
[config the bots]: https://chromium.googlesource.com/chromium/src/testing/+/refs/heads/main/buildbot/README.md#buildbot-testing-configuration-files
|
||||
[Defining Test Cases and Test Methods]: https://developer.apple.com/documentation/xctest/defining_test_cases_and_test_methods?language=objc
|
||||
[EarlGrey]: https://github.com/google/EarlGrey/tree/earlgrey2
|
||||
[EarlGrey APIs]: https://github.com/google/EarlGrey/blob/master/docs/api.md
|
||||
@ -206,5 +206,5 @@ beginning of stdout from an infra test shard if the above doesn't work.
|
||||
[Example CL adding App Interface]: https://chromium-review.googlesource.com/c/chromium/src/+/1919147
|
||||
[instructions]: ./build_instructions.md
|
||||
[Running Tests and Viewing Results]: https://developer.apple.com/library/archive/documentation/DeveloperTools/Conceptual/testing_with_xcode/chapters/05-running_tests.html
|
||||
[this AppLaunchManager API]: https://source.chromium.org/chromium/chromium/src/+/master:ios/testing/earl_grey/app_launch_manager.h;drc=d0889865de20c5b3bc59d58674eb2dcc02dd2269;l=47
|
||||
[this AppLaunchManager API]: https://source.chromium.org/chromium/chromium/src/+/main:ios/testing/earl_grey/app_launch_manager.h;drc=d0889865de20c5b3bc59d58674eb2dcc02dd2269;l=47
|
||||
[XCUITest]: https://developer.apple.com/documentation/xctest
|
||||
|
||||
@ -29,26 +29,26 @@ lacros built from the M-101 branch might run on top of the ash version built
|
||||
from the M-100 branch.
|
||||
|
||||
Lacros can be imagined as "Linux chrome with more Wayland support". Lacros uses
|
||||
[ozone](https://chromium.googlesource.com/chromium/src.git/+/master/ui/ozone)
|
||||
[ozone](https://chromium.googlesource.com/chromium/src.git/+/main/ui/ozone)
|
||||
as an abstraction layer for graphics and event handling. Ozone has a "backend"
|
||||
with client-side support for the Wayland compositor protocol.
|
||||
|
||||
Chrome OS has a Wayland server implementation called
|
||||
[exosphere](https://chromium.googlesource.com/chromium/src.git/+/master/components/exo).
|
||||
[exosphere](https://chromium.googlesource.com/chromium/src.git/+/main/components/exo).
|
||||
It is used by ARC (to run Android apps) and Crostini (to run Linux apps).
|
||||
|
||||
Lacros will use exo as the Wayland server for graphics and event handling. Where
|
||||
possible we use stable Wayland protocols. We also share Wayland protocol
|
||||
extensions with ARC and Crostini (e.g.
|
||||
[zaura-shell](https://chromium.googlesource.com/chromium/src.git/+/master/components/exo/wayland/protocol/aura-shell.xml).
|
||||
[zaura-shell](https://chromium.googlesource.com/chromium/src.git/+/main/components/exo/wayland/protocol/aura-shell.xml).
|
||||
Higher-level features (e.g. file picking) use Mojo IPC.
|
||||
|
||||
We call the new Mojo API surface "crosapi". It's similar in concept to Win32 or
|
||||
Cocoa, but much smaller. It's also mostly asynchronous for performance reasons.
|
||||
The API lives in
|
||||
[//chromeos/crosapi](https://chromium.googlesource.com/chromium/src.git/+/master/chromeos/crosapi).
|
||||
[//chromeos/crosapi](https://chromium.googlesource.com/chromium/src.git/+/main/chromeos/crosapi).
|
||||
The ash-side implementation lives in
|
||||
[//chrome/browser/ash/crosapi](https://chromium.googlesource.com/chromium/src.git/+/master/chrome/browser/ash/crosapi).
|
||||
[//chrome/browser/ash/crosapi](https://chromium.googlesource.com/chromium/src.git/+/main/chrome/browser/ash/crosapi).
|
||||
|
||||
Code can be conditionally compiled into lacros via
|
||||
BUILDFLAG(IS_CHROMEOS_LACROS).
|
||||
|
||||
@ -211,7 +211,7 @@ three) but you'll still need to use `--plugin-launcher` or another approach.
|
||||
### Printing Chromium types
|
||||
|
||||
gdb 7 lets us use Python to write pretty-printers for Chromium types. See
|
||||
[gdbinit](https://chromium.googlesource.com/chromium/src/+/master/docs/gdbinit.md)
|
||||
[gdbinit](https://chromium.googlesource.com/chromium/src/+/main/docs/gdbinit.md)
|
||||
to enable pretty-printing of Chromium types. This will import Blink
|
||||
pretty-printers as well.
|
||||
|
||||
@ -351,7 +351,7 @@ your "gn args".
|
||||
When `strip_absolute_paths_from_debug_symbols` is enabled (which is the
|
||||
default), gdb may not be able to find debug files, making source-level debugging
|
||||
impossible. See
|
||||
[gdbinit](https://chromium.googlesource.com/chromium/src/+/master/docs/gdbinit.md)
|
||||
[gdbinit](https://chromium.googlesource.com/chromium/src/+/main/docs/gdbinit.md)
|
||||
to configure gdb to be able to find debug files.
|
||||
|
||||
## Core files
|
||||
|
||||
@ -57,7 +57,7 @@ that we need `libdbus-1-dev` and `libdbus-1-3`. Add these both to the
|
||||
`DEBIAN_PACKAGES` list in
|
||||
[`//build/linux/sysroot_scripts/sysroot-creator-sid.sh`](https://cs.chromium.org/chromium/src/build/linux/sysroot_scripts/sysroot-creator-sid.sh).
|
||||
Building and uploading the sysroot images is detailed in [Linux sysroot
|
||||
images](https://chromium.googlesource.com/chromium/src.git/+/master/docs/sysroot.md).
|
||||
images](https://chromium.googlesource.com/chromium/src.git/+/main/docs/sysroot.md).
|
||||
You may need to add additional dependent libraries for your new library.
|
||||
|
||||
## Whitelist the new dependencies
|
||||
@ -194,5 +194,5 @@ Then add `:libdbus-1-3` to
|
||||
`//third_party/instrumented_libraries:locally_built`'s `deps`.
|
||||
|
||||
See [Linux Instrumented
|
||||
Libraries](https://chromium.googlesource.com/chromium/src.git/+/master/docs/instrumented_libraries.md)
|
||||
Libraries](https://chromium.googlesource.com/chromium/src.git/+/main/docs/instrumented_libraries.md)
|
||||
for instructions on building and uploading the instrumented libraries.
|
||||
|
||||
@ -148,4 +148,4 @@ Sandboxing can make developing harder, see:
|
||||
## See also
|
||||
|
||||
* [LinuxSandboxIPC](sandbox_ipc.md)
|
||||
* [How Chromium's Linux sandbox affects Native Client](https://chromium.googlesource.com/native_client/src/native_client.git/+/master/docs/outer_sandbox.md)
|
||||
* [How Chromium's Linux sandbox affects Native Client](https://chromium.googlesource.com/native_client/src/native_client.git/+/main/docs/outer_sandbox.md)
|
||||
|
||||
@ -1,10 +1,10 @@
|
||||
# Metadata information for this directory.
|
||||
#
|
||||
# For more information on DIR_METADATA files, see:
|
||||
# https://source.chromium.org/chromium/infra/infra/+/master:go/src/infra/tools/dirmd/README.md
|
||||
# https://source.chromium.org/chromium/infra/infra/+/main:go/src/infra/tools/dirmd/README.md
|
||||
#
|
||||
# For the schema of this file, see Metadata message:
|
||||
# https://source.chromium.org/chromium/infra/infra/+/master:go/src/infra/tools/dirmd/proto/dir_metadata.proto
|
||||
# https://source.chromium.org/chromium/infra/infra/+/main:go/src/infra/tools/dirmd/proto/dir_metadata.proto
|
||||
|
||||
monorail {
|
||||
component: "Services>SignIn"
|
||||
|
||||
@ -13,7 +13,7 @@ Are you a Google employee? See
|
||||
## System requirements
|
||||
|
||||
* A 64-bit Intel Mac running 10.15.4+. (Building on Arm Macs is
|
||||
[not yet supported](https://chromium.googlesource.com/chromium/src.git/+/master/docs/mac_arm64.md).)
|
||||
[not yet supported](https://chromium.googlesource.com/chromium/src.git/+/main/docs/mac_arm64.md).)
|
||||
* [Xcode](https://developer.apple.com/xcode/) 12.2+. This version of Xcode
|
||||
comes with ...
|
||||
* The macOS 11.0 SDK. Run
|
||||
|
||||
@ -1,10 +1,10 @@
|
||||
# Metadata information for this directory.
|
||||
#
|
||||
# For more information on DIR_METADATA files, see:
|
||||
# https://source.chromium.org/chromium/infra/infra/+/master:go/src/infra/tools/dirmd/README.md
|
||||
# https://source.chromium.org/chromium/infra/infra/+/main:go/src/infra/tools/dirmd/README.md
|
||||
#
|
||||
# For the schema of this file, see Metadata message:
|
||||
# https://source.chromium.org/chromium/infra/infra/+/master:go/src/infra/tools/dirmd/proto/dir_metadata.proto
|
||||
# https://source.chromium.org/chromium/infra/infra/+/main:go/src/infra/tools/dirmd/proto/dir_metadata.proto
|
||||
|
||||
monorail {
|
||||
component: "Blink>Media"
|
||||
|
||||
@ -21,7 +21,7 @@ Wildcards can be used to run specific sets of tests:
|
||||
`tast run $HOST video.DecodeAccelPerf*1080P60FPS`
|
||||
|
||||
Check the
|
||||
[tast video folder](https://chromium.googlesource.com/chromiumos/platform/tast-tests/+/refs/heads/master/src/chromiumos/tast/local/bundles/cros/video/)
|
||||
[tast video folder](https://chromium.googlesource.com/chromiumos/platform/tast-tests/+/refs/heads/main/src/chromiumos/tast/local/bundles/cros/video/)
|
||||
for a list of all available tests.
|
||||
See the
|
||||
[Tast quickstart guide](https://chromium.googlesource.com/chromiumos/platform/tast/+/HEAD/docs/quickstart.md)
|
||||
|
||||
@ -24,7 +24,7 @@ Wildcards can be used to run specific sets of tests:
|
||||
* Run all VP9 profile 2 tests: `tast run $HOST video.DecodeAccelVP92*`
|
||||
|
||||
Check the
|
||||
[tast video folder](https://chromium.googlesource.com/chromiumos/platform/tast-tests/+/refs/heads/master/src/chromiumos/tast/local/bundles/cros/video/)
|
||||
[tast video folder](https://chromium.googlesource.com/chromiumos/platform/tast-tests/+/refs/heads/main/src/chromiumos/tast/local/bundles/cros/video/)
|
||||
for a list of all available tests.
|
||||
See the
|
||||
[Tast quickstart guide](https://chromium.googlesource.com/chromiumos/platform/tast/+/HEAD/docs/quickstart.md)
|
||||
|
||||
@ -21,7 +21,7 @@ Wildcards can be used to run specific sets of tests:
|
||||
* Run all VP8 tests: `tast run $HOST video.EncodeAccel.vp8*`
|
||||
|
||||
Check the
|
||||
[tast video folder](https://chromium.googlesource.com/chromiumos/platform/tast-tests/+/refs/heads/master/src/chromiumos/tast/local/bundles/cros/video/)
|
||||
[tast video folder](https://chromium.googlesource.com/chromiumos/platform/tast-tests/+/refs/heads/main/src/chromiumos/tast/local/bundles/cros/video/)
|
||||
for a list of all available tests.
|
||||
See the
|
||||
[Tast quickstart guide](https://chromium.googlesource.com/chromiumos/platform/tast/+/HEAD/docs/quickstart.md)
|
||||
|
||||
@ -1,10 +1,10 @@
|
||||
# Metadata information for this directory.
|
||||
#
|
||||
# For more information on DIR_METADATA files, see:
|
||||
# https://source.chromium.org/chromium/infra/infra/+/master:go/src/infra/tools/dirmd/README.md
|
||||
# https://source.chromium.org/chromium/infra/infra/+/main:go/src/infra/tools/dirmd/README.md
|
||||
#
|
||||
# For the schema of this file, see Metadata message:
|
||||
# https://source.chromium.org/chromium/infra/infra/+/master:go/src/infra/tools/dirmd/proto/dir_metadata.proto
|
||||
# https://source.chromium.org/chromium/infra/infra/+/main:go/src/infra/tools/dirmd/proto/dir_metadata.proto
|
||||
|
||||
monorail {
|
||||
component: "Internals>Instrumentation>Memory"
|
||||
|
||||
@ -161,7 +161,7 @@ or take a look at one of the existing examples such as
|
||||
[tracing@chromium.org][mailtracing] for questions and support.
|
||||
|
||||
[dp-slides]: https://docs.google.com/presentation/d/1GI3HY3Mm5-Mvp6eZyVB0JiaJ-u3L1MMJeKHJg4lxjEI/present?slide=id.g995514d5c_1_45
|
||||
[malloc-dp]: https://chromium.googlesource.com/chromium/src.git/+/master/base/trace_event/malloc_dump_provider.cc
|
||||
[malloc-dp]: https://chromium.googlesource.com/chromium/src.git/+/main/base/trace_event/malloc_dump_provider.cc
|
||||
[hotlist]: https://code.google.com/p/chromium/issues/list?q=label:Hotlist-MemoryInfra
|
||||
[mailtracing]: mailto:tracing@chromium.org
|
||||
|
||||
|
||||
@ -29,8 +29,8 @@ two things:
|
||||
2. Register and unregister you dump provider with the
|
||||
[`MemoryDumpManager`][mdm].
|
||||
|
||||
[mdp]: https://chromium.googlesource.com/chromium/src/+/master/base/trace_event/memory_dump_provider.h
|
||||
[mdm]: https://chromium.googlesource.com/chromium/src/+/master/base/trace_event/memory_dump_manager.h
|
||||
[mdp]: https://chromium.googlesource.com/chromium/src/+/main/base/trace_event/memory_dump_provider.h
|
||||
[mdm]: https://chromium.googlesource.com/chromium/src/+/main/base/trace_event/memory_dump_manager.h
|
||||
|
||||
## Creating a Memory Dump Provider
|
||||
|
||||
@ -68,9 +68,9 @@ For many components, this may be all that is needed. See
|
||||
[Handling Shared Memory Allocations](#Handling-Shared-Memory-Allocations) and
|
||||
[Suballocations](#Suballocations) for information on more complex use cases.
|
||||
|
||||
[resource-pool]: https://chromium.googlesource.com/chromium/src/+/master/cc/resources/resource_pool.h
|
||||
[mem-alloc-dump]: https://chromium.googlesource.com/chromium/src/+/master/base/trace_event/memory_allocator_dump.h
|
||||
[pmd]: https://chromium.googlesource.com/chromium/src/+/master/base/trace_event/process_memory_dump.h
|
||||
[resource-pool]: https://chromium.googlesource.com/chromium/src/+/main/cc/resources/resource_pool.h
|
||||
[mem-alloc-dump]: https://chromium.googlesource.com/chromium/src/+/main/base/trace_event/memory_allocator_dump.h
|
||||
[pmd]: https://chromium.googlesource.com/chromium/src/+/main/base/trace_event/process_memory_dump.h
|
||||
|
||||
## Registering a Memory Dump Provider
|
||||
|
||||
@ -95,7 +95,7 @@ complex and may be a number of things:
|
||||
* If your component already uses a custom `base::SingleThreadTaskRunner` for
|
||||
executing tasks on a specific thread, you should likely use this runner.
|
||||
|
||||
[task-runner-handle]: https://chromium.googlesource.com/chromium/src/+/master/base/thread_task_runner_handle.h
|
||||
[task-runner-handle]: https://chromium.googlesource.com/chromium/src/+/main/base/thread_task_runner_handle.h
|
||||
|
||||
## Unregistration
|
||||
|
||||
@ -175,4 +175,4 @@ which make up a texture. To create a suballocation, instead of calling
|
||||
[`ProcessMemoryDump::AddSubAllocation`][pmd], providing the ID of the parent
|
||||
allocation as the first parameter.
|
||||
|
||||
[texture-manager]: https://chromium.googlesource.com/chromium/src/+/master/gpu/command_buffer/service/texture_manager.cc
|
||||
[texture-manager]: https://chromium.googlesource.com/chromium/src/+/main/gpu/command_buffer/service/texture_manager.cc
|
||||
|
||||
@ -38,7 +38,7 @@ These benchmarks are run continuously on the [chrome.perf][] waterfall,
|
||||
collecting and reporting results on the
|
||||
[Chrome Performance Dashboard][chromeperf].
|
||||
|
||||
[system_health]: https://chromium.googlesource.com/chromium/src/+/master/tools/perf/page_sets/system_health/
|
||||
[system_health]: https://chromium.googlesource.com/chromium/src/+/main/tools/perf/page_sets/system_health/
|
||||
[chrome.perf]: https://ci.chromium.org/p/chrome/g/chrome.perf/console
|
||||
[chromeperf]: https://chromeperf.appspot.com/report
|
||||
|
||||
|
||||
@ -1,10 +1,10 @@
|
||||
# Metadata information for this directory.
|
||||
#
|
||||
# For more information on DIR_METADATA files, see:
|
||||
# https://source.chromium.org/chromium/infra/infra/+/master:go/src/infra/tools/dirmd/README.md
|
||||
# https://source.chromium.org/chromium/infra/infra/+/main:go/src/infra/tools/dirmd/README.md
|
||||
#
|
||||
# For the schema of this file, see Metadata message:
|
||||
# https://source.chromium.org/chromium/infra/infra/+/master:go/src/infra/tools/dirmd/proto/dir_metadata.proto
|
||||
# https://source.chromium.org/chromium/infra/infra/+/main:go/src/infra/tools/dirmd/proto/dir_metadata.proto
|
||||
|
||||
monorail {
|
||||
component: "Internals>Instrumentation>Memory"
|
||||
|
||||
@ -23,6 +23,6 @@ Note, this is a community curated list. No one is sitting around trying to tabul
|
||||
* [Reduced 1.3 MB](https://codereview.chromium.org/1156003008) from browser private dirty by decoding images from ImageManager cache on demand
|
||||
* [Reduced 2-10MB](https://codereview.chromium.org/1377483003) from browser process by shrinking IPC buffers after large messages were passed
|
||||
* [Reduced < 2 MB](https://chromium-review.googlesource.com/c/chromium/src/+/945748) from background tabs of both Chrome and WebView on Android Go device. See further [information](https://bugs.chromium.org/p/chromium/issues/detail?id=833769) on the internal bots for Android.
|
||||
* Developed [Memory-Infra](https://chromium.googlesource.com/chromium/src/+/master/components/tracing/docs/memory_infra.md), a timeline-based memory profiling system integrated into chrome:://tracing
|
||||
* Developed [Memory-Infra](https://chromium.googlesource.com/chromium/src/+/main/components/tracing/docs/memory_infra.md), a timeline-based memory profiling system integrated into chrome:://tracing
|
||||
* Developed [System health benchmarks](https://docs.google.com/document/d/1BM_6lBrPzpMNMtcyi2NFKGIzmzIQ1oH3OlNG27kDGNU/edit?ts=57e92782), a set of benchmarks that give us consistent metrics for our reduction efforts
|
||||
* [Visualized Chrome's memory consumption in real-world website](https://docs.google.com/document/d/1JfnW6RpRDuuZITQ3xuFUIRBfC_KOG5xXUuW8U_UePJU/edit)s
|
||||
|
||||
@ -116,7 +116,7 @@ TODO(awong): Write about options to script and the flame graph.
|
||||
|
||||
### Instructions
|
||||
1. Get 2 or more [symbolized heap dump](#heap-dumps)
|
||||
3. Run resulting traces through [`diff_heap_profiler.py`](https://chromium.googlesource.com/catapult/+/master/experimental/tracing/bin/diff_heap_profiler.py) to show a list of new allocations.
|
||||
3. Run resulting traces through [`diff_heap_profiler.py`](https://chromium.googlesource.com/catapult/+/main/experimental/tracing/bin/diff_heap_profiler.py) to show a list of new allocations.
|
||||
|
||||
-----------
|
||||
## <a name="heap-dumps"></a>Heap Dumps
|
||||
|
||||
@ -161,4 +161,4 @@ They are typically registered in
|
||||
`ContentBrowserClient::CreateThrottlesForNavigation`.
|
||||
|
||||
|
||||
[WebContentsObserver]: https://source.chromium.org/chromium/chromium/src/+/master:content/public/browser/web_contents_observer.h
|
||||
[WebContentsObserver]: https://source.chromium.org/chromium/chromium/src/+/main:content/public/browser/web_contents_observer.h
|
||||
|
||||
@ -9,4 +9,4 @@ Since every new port for Chromium has a maintenance cost, here are some guidelin
|
||||
* Chromium engineers are not expected to maintain them.
|
||||
* As much as possible, try to use existing branches/ifdefs.
|
||||
* While changes in src/base are unavoidable, higher level directories shouldn't have to change. i.e. existing porting APIs should be used. We would not accept new rendering pipelines as an example.
|
||||
* Send an email to [src/OWNERS](https://chromium.googlesource.com/chromium/src/+/master/ENG_REVIEW_OWNERS) for approval.
|
||||
* Send an email to [src/OWNERS](https://chromium.googlesource.com/chromium/src/+/main/ENG_REVIEW_OWNERS) for approval.
|
||||
|
||||
@ -41,7 +41,7 @@ effectively a Python script. Each recipe is divided into *steps*. Each *step*
|
||||
represents a well-defined action, such as updating the repository to point to
|
||||
tip of tree, or compiling the necessary build artifacts.
|
||||
|
||||
[recipe]: https://chromium.googlesource.com/external/github.com/luci/recipes-py/+/master/doc/user_guide.md
|
||||
[recipe]: https://chromium.googlesource.com/external/github.com/luci/recipes-py/+/main/doc/user_guide.md
|
||||
|
||||
|
||||
|
||||
|
||||
@ -1,10 +1,10 @@
|
||||
# Metadata information for this directory.
|
||||
#
|
||||
# For more information on DIR_METADATA files, see:
|
||||
# https://source.chromium.org/chromium/infra/infra/+/master:go/src/infra/tools/dirmd/README.md
|
||||
# https://source.chromium.org/chromium/infra/infra/+/main:go/src/infra/tools/dirmd/README.md
|
||||
#
|
||||
# For the schema of this file, see Metadata message:
|
||||
# https://source.chromium.org/chromium/infra/infra/+/master:go/src/infra/tools/dirmd/proto/dir_metadata.proto
|
||||
# https://source.chromium.org/chromium/infra/infra/+/main:go/src/infra/tools/dirmd/proto/dir_metadata.proto
|
||||
|
||||
monorail {
|
||||
component: "Privacy"
|
||||
|
||||
@ -1,10 +1,10 @@
|
||||
# Metadata information for this directory.
|
||||
#
|
||||
# For more information on DIR_METADATA files, see:
|
||||
# https://source.chromium.org/chromium/infra/infra/+/master:go/src/infra/tools/dirmd/README.md
|
||||
# https://source.chromium.org/chromium/infra/infra/+/main:go/src/infra/tools/dirmd/README.md
|
||||
#
|
||||
# For the schema of this file, see Metadata message:
|
||||
# https://source.chromium.org/chromium/infra/infra/+/master:go/src/infra/tools/dirmd/proto/dir_metadata.proto
|
||||
# https://source.chromium.org/chromium/infra/infra/+/main:go/src/infra/tools/dirmd/proto/dir_metadata.proto
|
||||
|
||||
monorail {
|
||||
component: "Privacy>Fingerprinting"
|
||||
|
||||
@ -28,10 +28,10 @@ possible that changes may miss branch date and require a merge post branch.
|
||||
**Merge**: any change that is cherry picked from trunk to a release branch.
|
||||
|
||||
Please read overview of [Chrome Release
|
||||
Cycle](https://chromium.googlesource.com/chromium/src.git/+/master/docs/process/release_cycle.md)
|
||||
Cycle](https://chromium.googlesource.com/chromium/src.git/+/main/docs/process/release_cycle.md)
|
||||
to understand in detail how the Chrome release cycle works and understand key
|
||||
release concepts and terminology. Please read [Defining Release
|
||||
Blockers](https://chromium.googlesource.com/chromium/src.git/+/master/docs/process/release_blockers.md)
|
||||
Blockers](https://chromium.googlesource.com/chromium/src.git/+/main/docs/process/release_blockers.md)
|
||||
to understand how issues/bugs are categorized as release blocking.
|
||||
List of schedule and release owners can be found at [Chrome
|
||||
Calendar](https://chromepmo.appspot.com/calendar) (Googlers only, opening to all in the near future).
|
||||
|
||||
@ -137,7 +137,7 @@ Ensure you are using GDB on Linux, not LLDB.
|
||||
|
||||
Linux :
|
||||
See
|
||||
https://chromium.googlesource.com/chromium/src/+/master/docs/linux/debugging.md
|
||||
https://chromium.googlesource.com/chromium/src/+/main/docs/linux/debugging.md
|
||||
|
||||
macOS :
|
||||
https://chromium.googlesource.com/chromium/src/+/main/docs/mac/debugging.md
|
||||
|
||||
@ -1,10 +1,10 @@
|
||||
# Metadata information for this directory.
|
||||
#
|
||||
# For more information on DIR_METADATA files, see:
|
||||
# https://source.chromium.org/chromium/infra/infra/+/master:go/src/infra/tools/dirmd/README.md
|
||||
# https://source.chromium.org/chromium/infra/infra/+/main:go/src/infra/tools/dirmd/README.md
|
||||
#
|
||||
# For the schema of this file, see Metadata message:
|
||||
# https://source.chromium.org/chromium/infra/infra/+/master:go/src/infra/tools/dirmd/proto/dir_metadata.proto
|
||||
# https://source.chromium.org/chromium/infra/infra/+/main:go/src/infra/tools/dirmd/proto/dir_metadata.proto
|
||||
|
||||
monorail {
|
||||
component: "Security"
|
||||
|
||||
@ -29,7 +29,7 @@ example "lookalike" patterns include:
|
||||
* Domains that embed other domain names within their own hostname, such as
|
||||
`google.com.example.com`.
|
||||
* Domains that use IDN
|
||||
[homographs](https://chromium.googlesource.com/chromium/src/+/master/docs/idn.md),
|
||||
[homographs](https://chromium.googlesource.com/chromium/src/+/main/docs/idn.md),
|
||||
such as `goögle.com`.
|
||||
|
||||
This list is not exhaustive, and developers are encouraged to avoid using
|
||||
|
||||
@ -142,7 +142,7 @@ which may include:
|
||||
|
||||
These mechanisms must clearly disclose the origin of the request, and follow
|
||||
Chromium's
|
||||
[guidelines on displaying URLs](https://chromium.googlesource.com/chromium/src/+/master/docs/security/url_display_guidelines/url_display_guidelines.md).
|
||||
[guidelines on displaying URLs](https://chromium.googlesource.com/chromium/src/+/main/docs/security/url_display_guidelines/url_display_guidelines.md).
|
||||
Implementations may be tested using tools such as
|
||||
[Trickuri](https://github.com/chromium/trickuri).
|
||||
|
||||
|
||||
@ -41,7 +41,7 @@ provide concrete recommendations for web developers responsible for protecting
|
||||
users' data.
|
||||
|
||||
[spectre]: https://spectreattack.com/
|
||||
[post-spectre-rethink]: https://chromium.googlesource.com/chromium/src/+/master/docs/security/side-channel-threat-model.md
|
||||
[post-spectre-rethink]: https://chromium.googlesource.com/chromium/src/+/main/docs/security/side-channel-threat-model.md
|
||||
[site-isolation]: https://www.chromium.org/Home/chromium-security/site-isolation
|
||||
[project-fission]: https://wiki.mozilla.org/Project_Fission
|
||||
|
||||
@ -126,7 +126,7 @@ This model is spelled out in more detail in both Chromium's
|
||||
[fetch-metadata]: https://web.dev/fetch-metadata/
|
||||
[corp]: https://resourcepolicy.fyi/
|
||||
[coop]: https://docs.google.com/document/d/1Ey3MXcLzwR1T7aarkpBXEwP7jKdd2NvQdgYvF8_8scI/edit
|
||||
[corb]: https://chromium.googlesource.com/chromium/src/+/master/services/network/cross_origin_read_blocking_explainer.md
|
||||
[corb]: https://chromium.googlesource.com/chromium/src/+/main/services/network/cross_origin_read_blocking_explainer.md
|
||||
[orb]: https://github.com/annevk/orb
|
||||
|
||||
|
||||
|
||||
@ -134,7 +134,7 @@ timeframe.)
|
||||
##### Incompleteness of CORB
|
||||
|
||||
Site Isolation depends on [cross-origin read
|
||||
blocking](https://chromium.googlesource.com/chromium/src/+/master/content/browser/loader/cross_origin_read_blocking_explainer.md)
|
||||
blocking](https://chromium.googlesource.com/chromium/src/+/main/content/browser/loader/cross_origin_read_blocking_explainer.md)
|
||||
(CORB; formerly known as cross-site document blocking or XSDB) to prevent a
|
||||
malicious website from pulling in sensitive cross-origin data. Otherwise, an
|
||||
attacker could use markup like `<img src="http://example.com/secret.json">` to
|
||||
|
||||
@ -13,7 +13,7 @@ See below for how the process differs on ChromeOS.
|
||||
|
||||
Shutdown starts when nothing keeps Chrome alive. Typically, this happens when
|
||||
all browser windows are closed, but other things can [keep Chrome
|
||||
alive](https://source.chromium.org/chromium/chromium/src/+/master:components/keep_alive_registry/keep_alive_types.h).
|
||||
alive](https://source.chromium.org/chromium/chromium/src/+/main:components/keep_alive_registry/keep_alive_types.h).
|
||||
|
||||
When nothing keeps Chrome alive, `BrowserProcessImpl::Unpin` asks the main
|
||||
thread's message loop to quit as soon as it no longer has tasks ready to run
|
||||
|
||||
@ -1,10 +1,10 @@
|
||||
# Metadata information for this directory.
|
||||
#
|
||||
# For more information on DIR_METADATA files, see:
|
||||
# https://source.chromium.org/chromium/infra/infra/+/master:go/src/infra/tools/dirmd/README.md
|
||||
# https://source.chromium.org/chromium/infra/infra/+/main:go/src/infra/tools/dirmd/README.md
|
||||
#
|
||||
# For the schema of this file, see Metadata message:
|
||||
# https://source.chromium.org/chromium/infra/infra/+/master:go/src/infra/tools/dirmd/proto/dir_metadata.proto
|
||||
# https://source.chromium.org/chromium/infra/infra/+/main:go/src/infra/tools/dirmd/proto/dir_metadata.proto
|
||||
|
||||
monorail {
|
||||
component: "Speed"
|
||||
|
||||
@ -125,13 +125,13 @@ to learn how to use traces to debug performance issues.
|
||||
|
||||
### Are there debugging tips specific to certain benchmarks?
|
||||
|
||||
* [Memory](https://chromium.googlesource.com/chromium/src/+/master/docs/memory-infra/memory_benchmarks.md)
|
||||
* [Memory](https://chromium.googlesource.com/chromium/src/+/main/docs/memory-infra/memory_benchmarks.md)
|
||||
* [Android binary size](apk_size_regressions.md)
|
||||
* [Micro-benchmarks](microbenchmark_regressions.md)
|
||||
|
||||
### How do I profile?
|
||||
|
||||
Here is the [documentation on CPU Profiling Chrome](https://chromium.googlesource.com/chromium/src/+/master/docs/profiling.md)
|
||||
Here is the [documentation on CPU Profiling Chrome](https://chromium.googlesource.com/chromium/src/+/main/docs/profiling.md)
|
||||
|
||||
## If you don't believe your CL could be the cause
|
||||
|
||||
|
||||
@ -67,7 +67,7 @@ Otherwise, file a bug (TODO: [Make this template automatic](https://github.com/c
|
||||
> [https://ci.chromium.org/p/chromium/builders/luci.chromium.try/android-binary-size/**$TRYJOB_NUMBER**](https://ci.chromium.org/p/chromium/builders/luci.chromium.try/android-binary-size/11111)
|
||||
>
|
||||
> Debugging size regressions is documented at:
|
||||
> https://chromium.googlesource.com/chromium/src/+/master/docs/speed/apk_size_regressions.md#Debugging-Apk-Size-Increase
|
||||
> https://chromium.googlesource.com/chromium/src/+/main/docs/speed/apk_size_regressions.md#Debugging-Apk-Size-Increase
|
||||
>
|
||||
> Based on the trybot result: **20kb of native code, 8kb of pngs. *(or some other explanation as to what caused the growth).***
|
||||
>
|
||||
|
||||
@ -1,10 +1,10 @@
|
||||
# Metadata information for this directory.
|
||||
#
|
||||
# For more information on DIR_METADATA files, see:
|
||||
# https://source.chromium.org/chromium/infra/infra/+/master:go/src/infra/tools/dirmd/README.md
|
||||
# https://source.chromium.org/chromium/infra/infra/+/main:go/src/infra/tools/dirmd/README.md
|
||||
#
|
||||
# For the schema of this file, see Metadata message:
|
||||
# https://source.chromium.org/chromium/infra/infra/+/master:go/src/infra/tools/dirmd/proto/dir_metadata.proto
|
||||
# https://source.chromium.org/chromium/infra/infra/+/main:go/src/infra/tools/dirmd/proto/dir_metadata.proto
|
||||
|
||||
monorail {
|
||||
component: "Test>Telemetry"
|
||||
|
||||
@ -25,5 +25,5 @@ Both desktop & mobile:
|
||||
|
||||
|
||||
Instructions for how to run these benchmarks:
|
||||
* [Running them locally](https://chromium.googlesource.com/catapult/+/master/telemetry/docs/run_benchmarks_locally.md)
|
||||
* [Running on perf trybot](https://chromium.googlesource.com/chromium/src/+/master/docs/speed/perf_trybots.md)
|
||||
* [Running them locally](https://chromium.googlesource.com/catapult/+/main/telemetry/docs/run_benchmarks_locally.md)
|
||||
* [Running on perf trybot](https://chromium.googlesource.com/chromium/src/+/main/docs/speed/perf_trybots.md)
|
||||
|
||||
@ -10,9 +10,9 @@ but for performance coverage.
|
||||
|
||||
## Writing Tests
|
||||
Each test entry point is a HTML file written using
|
||||
[runner.js](https://chromium.googlesource.com/chromium/src/+/master/third_party/blink/perf_tests/resources/runner.js)
|
||||
[runner.js](https://chromium.googlesource.com/chromium/src/+/main/third_party/blink/perf_tests/resources/runner.js)
|
||||
testing framework. The test file is placed inside a sub folder of
|
||||
[blink/perf_tests/](https://chromium.googlesource.com/chromium/src/+/master/third_party/blink/perf_tests/)
|
||||
[blink/perf_tests/](https://chromium.googlesource.com/chromium/src/+/main/third_party/blink/perf_tests/)
|
||||
and is started by importing `runner.js` script into the document:
|
||||
```
|
||||
<script src="../resources/runner.js"></script>
|
||||
@ -83,9 +83,9 @@ also compute the total CPU times for trace events 'A' & 'B' per `foo()` run:
|
||||
|
||||
Example tracing synchronous tests:
|
||||
|
||||
* [append-child-measure-time.html](https://chromium.googlesource.com/chromium/src/+/master/third_party/blink/perf_tests/test_data/append-child-measure-time.html)
|
||||
* [append-child-measure-time.html](https://chromium.googlesource.com/chromium/src/+/main/third_party/blink/perf_tests/test_data/append-child-measure-time.html)
|
||||
|
||||
* [simple-html-measure-page-load-time.html](https://chromium.googlesource.com/chromium/src/+/master/third_party/blink/perf_tests/test_data/simple-html-measure-page-load-time.html)
|
||||
* [simple-html-measure-page-load-time.html](https://chromium.googlesource.com/chromium/src/+/main/third_party/blink/perf_tests/test_data/simple-html-measure-page-load-time.html)
|
||||
|
||||
|
||||
### Asynchronous Perf Tests
|
||||
@ -143,9 +143,9 @@ example of synchronous tracing test above.
|
||||
|
||||
Example of tracing asynchronous tests:
|
||||
|
||||
[color-changes-measure-frame-time.html](https://chromium.googlesource.com/chromium/src/+/master/third_party/blink/perf_tests/test_data/color-changes-measure-frame-time.html)
|
||||
[color-changes-measure-frame-time.html](https://chromium.googlesource.com/chromium/src/+/main/third_party/blink/perf_tests/test_data/color-changes-measure-frame-time.html)
|
||||
|
||||
[simple-blob-measure-async.html](https://chromium.googlesource.com/chromium/src/+/master/third_party/blink/perf_tests/test_data/simple-blob-measure-async.html)
|
||||
[simple-blob-measure-async.html](https://chromium.googlesource.com/chromium/src/+/main/third_party/blink/perf_tests/test_data/simple-blob-measure-async.html)
|
||||
|
||||
|
||||
### Service Worker Perf Tests
|
||||
@ -153,7 +153,7 @@ You can also run perf tests in service workers. You need to trigger the test
|
||||
with `PerfTestRunner.startMeasureValuesInWorker()` in a page. Within the `run`
|
||||
method provided to this function, you can initialize a worker and ask the
|
||||
worker to run the workload by using `measureRunsPerSecond()` defined in
|
||||
[worker-test-helper.js](https://chromium.googlesource.com/chromium/src/+/master/third_party/blink/perf_tests/resources/worker-test-helper.js).
|
||||
[worker-test-helper.js](https://chromium.googlesource.com/chromium/src/+/main/third_party/blink/perf_tests/resources/worker-test-helper.js).
|
||||
|
||||
`measureRunsPerSecond()` returns a promise which resolves to the test result.
|
||||
The worker should send the result back to the page, and the page records the
|
||||
@ -162,9 +162,9 @@ recorded, the test finishes.
|
||||
|
||||
Here is an example for testing Cache Storage API of service workers:
|
||||
|
||||
[cache-open-add-delete-10K-service-worker.html](https://chromium.googlesource.com/chromium/src/+/master/third_party/blink/perf_tests/service_worker/cache-open-add-delete-10K-service-worker.html)
|
||||
[cache-open-add-delete-10K-service-worker.html](https://chromium.googlesource.com/chromium/src/+/main/third_party/blink/perf_tests/service_worker/cache-open-add-delete-10K-service-worker.html)
|
||||
|
||||
[cache-open-add-delete-10K-service-worker.js](https://chromium.googlesource.com/chromium/src/+/master/third_party/blink/perf_tests/service_worker/resources/cache-open-add-delete-10K-service-worker.js)
|
||||
[cache-open-add-delete-10K-service-worker.js](https://chromium.googlesource.com/chromium/src/+/main/third_party/blink/perf_tests/service_worker/resources/cache-open-add-delete-10K-service-worker.js)
|
||||
|
||||
## Running Tests
|
||||
|
||||
|
||||
@ -26,7 +26,7 @@ Cluster Telemetry service. You can specify a Gerrit patch for them and compare
|
||||
the results with and without the patch applied.
|
||||
|
||||
### Using Perf Try Bots
|
||||
[Perf Try Bots](https://chromium.googlesource.com/chromium/src/+/master/docs/speed/perf_trybots.md)
|
||||
[Perf Try Bots](https://chromium.googlesource.com/chromium/src/+/main/docs/speed/perf_trybots.md)
|
||||
lets you run only single story of `loading.desktop` or `loading.mobile`, because
|
||||
an entire loading benchmark is too large to run as a perf try job. You should
|
||||
only set the `Story` field, and leave the `Story Tags` field blank. Invalid
|
||||
@ -47,7 +47,7 @@ Googler only).
|
||||
For more in-depth analysis and shorter cycle times, it can be helpful to run the tests locally.
|
||||
|
||||
First, [prepare your test device for
|
||||
Telemetry](https://chromium.googlesource.com/chromium/src/+/master/docs/speed/benchmark/telemetry_device_setup.md).
|
||||
Telemetry](https://chromium.googlesource.com/chromium/src/+/main/docs/speed/benchmark/telemetry_device_setup.md).
|
||||
|
||||
Once you've done this, you can start the Telemetry benchmark with:
|
||||
|
||||
@ -62,9 +62,9 @@ where `benchmark_name` can be `loading.desktop` or `loading.mobile`.
|
||||
The loading test cases are divided into groups based on their network traffic
|
||||
settings and cache conditions.
|
||||
|
||||
All available traffic settings can be found in [traffic_setting.py](https://chromium.googlesource.com/catapult/+/master/telemetry/telemetry/page/traffic_setting.py)
|
||||
All available traffic settings can be found in [traffic_setting.py](https://chromium.googlesource.com/catapult/+/main/telemetry/telemetry/page/traffic_setting.py)
|
||||
|
||||
All available caching conditions can be found in [cache_temperature.py](https://chromium.googlesource.com/catapult/+/master/telemetry/telemetry/page/cache_temperature.py)
|
||||
All available caching conditions can be found in [cache_temperature.py](https://chromium.googlesource.com/catapult/+/main/telemetry/telemetry/page/cache_temperature.py)
|
||||
|
||||
Test cases of `loading.desktop` and `loading.mobile` are named with their
|
||||
corresponding settings. For example, `DevOpera_cold_3g` test case loads
|
||||
@ -90,8 +90,8 @@ or chrome-speed-metrics@google.com (Googlers only).
|
||||
|
||||
## Adding new loading test cases
|
||||
New test cases can be added by modifying
|
||||
[loading_desktop.py](https://chromium.googlesource.com/chromium/src/+/master/tools/perf/page_sets/loading_desktop.py)
|
||||
or [loading_mobile.py](https://chromium.googlesource.com/chromium/src/+/master/tools/perf/page_sets/loading_mobile.py) page sets.
|
||||
[loading_desktop.py](https://chromium.googlesource.com/chromium/src/+/main/tools/perf/page_sets/loading_desktop.py)
|
||||
or [loading_mobile.py](https://chromium.googlesource.com/chromium/src/+/main/tools/perf/page_sets/loading_mobile.py) page sets.
|
||||
|
||||
For example, to add a new case of loading
|
||||
`https://en.wikipedia.org/wiki/Cats_and_the_Internet` on 2G and 3G networks with
|
||||
|
||||
@ -36,7 +36,7 @@ Rendering metrics are [written in Javascript](https://cs.chromium.org/chromium/s
|
||||
|
||||
## How to run rendering benchmarks on local devices
|
||||
|
||||
First, set up your device by following the instructions [here](https://chromium.googlesource.com/chromium/src/+/master/docs/speed/benchmark/telemetry_device_setup.md). You can then run telemetry benchmarks locally using:
|
||||
First, set up your device by following the instructions [here](https://chromium.googlesource.com/chromium/src/+/main/docs/speed/benchmark/telemetry_device_setup.md). You can then run telemetry benchmarks locally using:
|
||||
|
||||
`./tools/perf/run_benchmark <benchmark_name> --browser=<browser>`
|
||||
|
||||
@ -56,16 +56,16 @@ Other useful options for the command are:
|
||||
|
||||
## How to run rendering benchmarks on try bots
|
||||
|
||||
For more consistent results and to identify whether your change has resulted in a rendering regression, you can run the rendering benchmarks using a [perf try job](https://chromium.googlesource.com/chromium/src/+/master/docs/speed/perf_trybots.md). In order to do this, you need to first upload a CL, which allows results to be generated with and without your patch.
|
||||
For more consistent results and to identify whether your change has resulted in a rendering regression, you can run the rendering benchmarks using a [perf try job](https://chromium.googlesource.com/chromium/src/+/main/docs/speed/perf_trybots.md). In order to do this, you need to first upload a CL, which allows results to be generated with and without your patch.
|
||||
|
||||
## How to handle regressions
|
||||
|
||||
If your changes have resulted in a regression in a metric that is monitored by [perf alerts](https://chromeperf.appspot.com/alerts?sortby=end_revision&sortdirection=down), you will be assigned to a bug. This will contain information about the specific metric and how much it was regressed, as well as a Pinpoint link that will help you investigate further. For instance, you will be able to obtain traces from the try bot runs. This [link](https://chromium.googlesource.com/chromium/src/+/master/docs/speed/addressing_performance_regressions.md) contains detailed steps on how to deal with regressions. Rendering metrics use trace events logged under the benchmark and toplevel trace categories.
|
||||
If your changes have resulted in a regression in a metric that is monitored by [perf alerts](https://chromeperf.appspot.com/alerts?sortby=end_revision&sortdirection=down), you will be assigned to a bug. This will contain information about the specific metric and how much it was regressed, as well as a Pinpoint link that will help you investigate further. For instance, you will be able to obtain traces from the try bot runs. This [link](https://chromium.googlesource.com/chromium/src/+/main/docs/speed/addressing_performance_regressions.md) contains detailed steps on how to deal with regressions. Rendering metrics use trace events logged under the benchmark and toplevel trace categories.
|
||||
|
||||
If you already have a trace and want to debug the metric computation part, you can just run the metric:
|
||||
`tracing/bin/run_metric <path-to-trace-file> renderingMetric`
|
||||
|
||||
If you are specifically investigating a regression related to janks, [this document](https://chromium.googlesource.com/chromium/src/+/master/docs/speed/debug-janks.md) may be useful.
|
||||
If you are specifically investigating a regression related to janks, [this document](https://chromium.googlesource.com/chromium/src/+/main/docs/speed/debug-janks.md) may be useful.
|
||||
|
||||
## How to add more pages
|
||||
|
||||
|
||||
@ -13,7 +13,7 @@ $ tools/perf/run_benchmark --browser=system dummy_benchmark.noisy_benchmark_1
|
||||
```
|
||||
|
||||
Otherwise have a look at the required catapult dependencies listed in the
|
||||
[.vpython](https://chromium.googlesource.com/chromium/src/+/master/.vpython)
|
||||
[.vpython](https://chromium.googlesource.com/chromium/src/+/main/.vpython)
|
||||
spec file.
|
||||
|
||||
## Desktop benchmarks
|
||||
@ -29,7 +29,7 @@ possible (e.g: AntiVirus,..) before running the benchmarks.
|
||||
### ChromeOS
|
||||
|
||||
Virtual Machine: see
|
||||
[cros_vm.md doc](https://chromium.googlesource.com/chromiumos/docs/+/master/cros_vm.md)
|
||||
[cros_vm.md doc](https://chromium.googlesource.com/chromiumos/docs/+/main/cros_vm.md)
|
||||
|
||||
Actual CrOS machine: please contact achuith@, cywang@ from CrOS teams for
|
||||
advice.
|
||||
|
||||
@ -1,10 +1,10 @@
|
||||
# Metadata information for this directory.
|
||||
#
|
||||
# For more information on DIR_METADATA files, see:
|
||||
# https://source.chromium.org/chromium/infra/infra/+/master:go/src/infra/tools/dirmd/README.md
|
||||
# https://source.chromium.org/chromium/infra/infra/+/main:go/src/infra/tools/dirmd/README.md
|
||||
#
|
||||
# For the schema of this file, see Metadata message:
|
||||
# https://source.chromium.org/chromium/infra/infra/+/master:go/src/infra/tools/dirmd/proto/dir_metadata.proto
|
||||
# https://source.chromium.org/chromium/infra/infra/+/main:go/src/infra/tools/dirmd/proto/dir_metadata.proto
|
||||
|
||||
monorail {
|
||||
component: "Speed>Release"
|
||||
|
||||
@ -205,8 +205,8 @@ For more information on when to use `const char *` vs `const char[]`, see
|
||||
|
||||
## Code Locations
|
||||
|
||||
- [Trybot recipe](https://source.chromium.org/chromium/chromium/tools/build/+/master:recipes/recipes/binary_size_trybot.py),
|
||||
[CI recipe](https://source.chromium.org/chromium/chromium/tools/build/+/master:recipes/recipes/binary_size_generator_tot.py),
|
||||
[recipe module](https://source.chromium.org/chromium/chromium/tools/build/+/master:recipes/recipe_modules/binary_size/api.py)
|
||||
- [Trybot recipe](https://source.chromium.org/chromium/chromium/tools/build/+/main:recipes/recipes/binary_size_trybot.py),
|
||||
[CI recipe](https://source.chromium.org/chromium/chromium/tools/build/+/main:recipes/recipes/binary_size_generator_tot.py),
|
||||
[recipe module](https://source.chromium.org/chromium/chromium/tools/build/+/main:recipes/recipe_modules/binary_size/api.py)
|
||||
- [Link to src-side checks](/tools/binary_size/trybot_commit_size_checker.py)
|
||||
- [Link to Gerrit Plugin](https://chromium.googlesource.com/infra/gerrit-plugins/chromium-binary-size/)
|
||||
|
||||
@ -26,7 +26,7 @@ Note that this list is not at all comprehensive. If you encounter an alert that
|
||||
|
||||
|
||||
|
||||
Sheriff-o-matic may occasionally fail to recognize a benchmark failure is due to story failures: because of this, it's worth double-checking [the test logs](https://chromium.googlesource.com/chromium/src/+/master/docs/speed/bot_health_sheriffing/how_to_access_test_logs.md#getting-a-list-of-stories-that-failed) for a general benchmark failure to verify that it's not due to a story failure.
|
||||
Sheriff-o-matic may occasionally fail to recognize a benchmark failure is due to story failures: because of this, it's worth double-checking [the test logs](https://chromium.googlesource.com/chromium/src/+/main/docs/speed/bot_health_sheriffing/how_to_access_test_logs.md#getting-a-list-of-stories-that-failed) for a general benchmark failure to verify that it's not due to a story failure.
|
||||
|
||||
**What action to take: **File a P1 bug, CCing the benchmark owner(s) (found [here](https://docs.google.com/spreadsheets/d/1xaAo0_SU3iDfGdqDJZX_jRV0QtkufwHUKH3kQKF3YQs/edit#gid=0)).
|
||||
|
||||
@ -34,11 +34,11 @@ Add to the bug:
|
||||
|
||||
* A link to the failing test's log
|
||||
|
||||
* [Any relevant failure stack trace](https://chromium.googlesource.com/chromium/src/+/master/docs/speed/bot_health_sheriffing/how_to_access_test_logs.md#identifying-why-a-story-failed)
|
||||
* [Any relevant failure stack trace](https://chromium.googlesource.com/chromium/src/+/main/docs/speed/bot_health_sheriffing/how_to_access_test_logs.md#identifying-why-a-story-failed)
|
||||
|
||||
* The revision range at which the story started failing (most easily found [through the flakiness dashboard](https://chromium.googlesource.com/chromium/src/+/master/docs/speed/bot_health_sheriffing/what_test_is_failing.md))
|
||||
* The revision range at which the story started failing (most easily found [through the flakiness dashboard](https://chromium.googlesource.com/chromium/src/+/main/docs/speed/bot_health_sheriffing/what_test_is_failing.md))
|
||||
|
||||
Once the bug is filed, [disable the failing story](https://chromium.googlesource.com/chromium/src/+/master/docs/speed/bot_health_sheriffing/how_to_disable_a_story.md) and [launch a bisect over the revision range of the breakage](https://chromium.googlesource.com/chromium/src/+/master/docs/speed/bot_health_sheriffing/how_to_launch_a_functional_bisect.md), and snooze the alert for 24h to give the bisect time to finish. Once the story is disabled, lower its priority to P2 and assign the bug to the benchmark owner.
|
||||
Once the bug is filed, [disable the failing story](https://chromium.googlesource.com/chromium/src/+/master/docs/speed/bot_health_sheriffing/how_to_disable_a_story.md) and [launch a bisect over the revision range of the breakage](https://chromium.googlesource.com/chromium/src/+/main/docs/speed/bot_health_sheriffing/how_to_launch_a_functional_bisect.md), and snooze the alert for 24h to give the bisect time to finish. Once the story is disabled, lower its priority to P2 and assign the bug to the benchmark owner.
|
||||
|
||||
**[Canonical example](https://bugs.cromium.org/p/chromium/issues/detail?id=809063)**
|
||||
|
||||
@ -56,7 +56,7 @@ Add to the bug:
|
||||
|
||||
* A clear request to Infra > Labs (e.g. "Labs team, could you please take a look at this bot to see why tests aren't running?")
|
||||
|
||||
Once the bug is filed, [snooze the alert](https://chromium.googlesource.com/chromium/src/+/master/docs/speed/bot_health_sheriffing/how_to_snooze_an_alert.md) for 24 hours.
|
||||
Once the bug is filed, [snooze the alert](https://chromium.googlesource.com/chromium/src/+/main/docs/speed/bot_health_sheriffing/how_to_snooze_an_alert.md) for 24 hours.
|
||||
|
||||
Sometimes, Infra>Labs may request additional help in debugging the problem. For example, they may notice that this bot repeatedly goes down and may ask for your help in figuring out why. If this happens and you're unsure what next step to take, reach out for help [on chat](https://hangouts.google.com/group/80kY8Glh1AqcbQP92).
|
||||
|
||||
@ -72,7 +72,7 @@ Sometimes, Infra>Labs may request additional help in debugging the problem. For
|
||||
|
||||
### Benchmark harness failure
|
||||
|
||||
**How to recognize: **Sheriff-o-matic will indicate that an entire benchmark is failing (i.e. no story failures will be listed). [The logs](https://chromium.googlesource.com/chromium/src/+/master/docs/speed/bot_health_sheriffing/how_to_access_test_logs.md) will contain a failure that's not attributable to any particular story. For example:
|
||||
**How to recognize: **Sheriff-o-matic will indicate that an entire benchmark is failing (i.e. no story failures will be listed). [The logs](https://chromium.googlesource.com/chromium/src/+/main/docs/speed/bot_health_sheriffing/how_to_access_test_logs.md) will contain a failure that's not attributable to any particular story. For example:
|
||||
|
||||
|
||||
|
||||
@ -82,7 +82,7 @@ Add to the bug:
|
||||
|
||||
* A link to the failing test's log
|
||||
|
||||
* [Any relevant failure stack trace](https://chromium.googlesource.com/chromium/src/+/master/docs/speed/bot_health_sheriffing/how_to_access_test_logs.md#identifying-why-a-story-failed)
|
||||
* [Any relevant failure stack trace](https://chromium.googlesource.com/chromium/src/+/main/docs/speed/bot_health_sheriffing/how_to_access_test_logs.md#identifying-why-a-story-failed)
|
||||
|
||||
* The revision range at which the story started failing. Because entire benchmark failures don't appear in the flakiness dashboard, you'll have to manually skim recent test run logs to identify when the failure started.
|
||||
|
||||
|
||||
@ -13,21 +13,21 @@ The goal of the perf bot health sheriff rotation is to ensure that the benchmark
|
||||
|
||||
## Quick links
|
||||
|
||||
* [How to determine what story is failing](https://chromium.googlesource.com/chromium/src/+/master/docs/speed/bot_health_sheriffing/what_test_is_failing.md)
|
||||
* [How to disable a story](https://chromium.googlesource.com/chromium/src/+/master/docs/speed/bot_health_sheriffing/how_to_disable_a_story.md)
|
||||
* [How to launch a functional bisect](https://chromium.googlesource.com/chromium/src/+/master/docs/speed/bot_health_sheriffing/how_to_launch_a_functional_bisect.md)
|
||||
* [How to snooze an alert](https://chromium.googlesource.com/chromium/src/+/master/docs/speed/bot_health_sheriffing/how_to_snooze_an_alert.md)
|
||||
* [How to access test logs](https://chromium.googlesource.com/chromium/src/+/master/docs/speed/bot_health_sheriffing/how_to_access_test_logs.md)
|
||||
* [How to handle a new problem](https://chromium.googlesource.com/chromium/src/+/master/docs/speed/bot_health_sheriffing/how_to_handle_a_new_problem.md)
|
||||
* [How to follow up on an alert](https://chromium.googlesource.com/chromium/src/+/master/docs/speed/bot_health_sheriffing/how_to_follow_up_on_an_alert.md)
|
||||
* [How to address duplicate alerts](https://chromium.googlesource.com/chromium/src/+/master/docs/speed/bot_health_sheriffing/how_to_address_duplicate_alerts.md)
|
||||
* [Glossary](https://chromium.googlesource.com/chromium/src/+/master/docs/speed/bot_health_sheriffing/glossary.md)
|
||||
* [How to determine what story is failing](https://chromium.googlesource.com/chromium/src/+/main/docs/speed/bot_health_sheriffing/what_test_is_failing.md)
|
||||
* [How to disable a story](https://chromium.googlesource.com/chromium/src/+/main/docs/speed/bot_health_sheriffing/how_to_disable_a_story.md)
|
||||
* [How to launch a functional bisect](https://chromium.googlesource.com/chromium/src/+/main/docs/speed/bot_health_sheriffing/how_to_launch_a_functional_bisect.md)
|
||||
* [How to snooze an alert](https://chromium.googlesource.com/chromium/src/+/main/docs/speed/bot_health_sheriffing/how_to_snooze_an_alert.md)
|
||||
* [How to access test logs](https://chromium.googlesource.com/chromium/src/+/main/docs/speed/bot_health_sheriffing/how_to_access_test_logs.md)
|
||||
* [How to handle a new problem](https://chromium.googlesource.com/chromium/src/+/main/docs/speed/bot_health_sheriffing/how_to_handle_a_new_problem.md)
|
||||
* [How to follow up on an alert](https://chromium.googlesource.com/chromium/src/+/main/docs/speed/bot_health_sheriffing/how_to_follow_up_on_an_alert.md)
|
||||
* [How to address duplicate alerts](https://chromium.googlesource.com/chromium/src/+/main/docs/speed/bot_health_sheriffing/how_to_address_duplicate_alerts.md)
|
||||
* [Glossary](https://chromium.googlesource.com/chromium/src/+/main/docs/speed/bot_health_sheriffing/glossary.md)
|
||||
|
||||
[TOC]
|
||||
|
||||
## Vocabulary
|
||||
|
||||
Definitions of various bot health related vocabulary can be found in our [glossary](https://chromium.googlesource.com/chromium/src/+/master/docs/speed/bot_health_sheriffing/glossary.md).
|
||||
Definitions of various bot health related vocabulary can be found in our [glossary](https://chromium.googlesource.com/chromium/src/+/main/docs/speed/bot_health_sheriffing/glossary.md).
|
||||
|
||||
## High-level responsibilities
|
||||
|
||||
@ -73,7 +73,7 @@ This category of alert should have a bug already linked with it. This link can b
|
||||
|
||||
|
||||
|
||||
Instructions can be found [here](https://chromium.googlesource.com/chromium/src/+/master/docs/speed/bot_health_sheriffing/how_to_follow_up_on_an_alert.md) on how to follow up with an existing alert.
|
||||
Instructions can be found [here](https://chromium.googlesource.com/chromium/src/+/main/docs/speed/bot_health_sheriffing/how_to_follow_up_on_an_alert.md) on how to follow up with an existing alert.
|
||||
|
||||
### Is this a new alert caused by the same root cause as an already-triaged alert?
|
||||
|
||||
@ -89,13 +89,13 @@ are both in the list of current of alerts but represent the same failure.
|
||||
|
||||
It can sometimes be tricky to differentiate between these alerts and ones caused by completely new problems, but sheriffs can always treat an alert as new and merge it with another later.
|
||||
|
||||
Instructions can be found [here](https://chromium.googlesource.com/chromium/src/+/master/docs/speed/bot_health_sheriffing/how_to_address_duplicate_alerts.md) on how to handle a duplicate alert.
|
||||
Instructions can be found [here](https://chromium.googlesource.com/chromium/src/+/main/docs/speed/bot_health_sheriffing/how_to_address_duplicate_alerts.md) on how to handle a duplicate alert.
|
||||
|
||||
### Is this a new alert caused by a new problem?
|
||||
|
||||
This category of alert doesn't yet have a bug associated with it. It's the most common category and requires the most expertise to handle.
|
||||
|
||||
Instructions can be found [here](https://chromium.googlesource.com/chromium/src/+/master/docs/speed/bot_health_sheriffing/how_to_handle_a_new_problem.md) on how to handle an alert for a new problem.
|
||||
Instructions can be found [here](https://chromium.googlesource.com/chromium/src/+/main/docs/speed/bot_health_sheriffing/how_to_handle_a_new_problem.md) on how to handle an alert for a new problem.
|
||||
|
||||
## After your shift is over
|
||||
|
||||
|
||||
@ -12,7 +12,7 @@
|
||||
[Source code](https://github.com/catapult-project/catapult/tree/master/experimental/trace_on_tap)
|
||||
|
||||
## Investigating janky scroll/animation
|
||||
See [this detailed guide](https://chromium.googlesource.com/chromium/src/+/master/docs/speed/debug-janks.md).
|
||||
See [this detailed guide](https://chromium.googlesource.com/chromium/src/+/main/docs/speed/debug-janks.md).
|
||||
|
||||
<!--- TODO: ## Bug SLO for perf bugs -->
|
||||
|
||||
|
||||
@ -1,10 +1,10 @@
|
||||
# Metadata information for this directory.
|
||||
#
|
||||
# For more information on DIR_METADATA files, see:
|
||||
# https://source.chromium.org/chromium/infra/infra/+/master:go/src/infra/tools/dirmd/README.md
|
||||
# https://source.chromium.org/chromium/infra/infra/+/main:go/src/infra/tools/dirmd/README.md
|
||||
#
|
||||
# For the schema of this file, see Metadata message:
|
||||
# https://source.chromium.org/chromium/infra/infra/+/master:go/src/infra/tools/dirmd/proto/dir_metadata.proto
|
||||
# https://source.chromium.org/chromium/infra/infra/+/main:go/src/infra/tools/dirmd/proto/dir_metadata.proto
|
||||
|
||||
monorail {
|
||||
component: "Speed>Benchmarks"
|
||||
|
||||
@ -3,7 +3,7 @@
|
||||
## Changes in Chrome 89
|
||||
|
||||
In Chrome 89, an improvement was made to the code that reports First Contentful
|
||||
Paint to [URL-Keyed Metrics](https://chromium.googlesource.com/chromium/src/+/master/services/metrics/ukm_api.md).
|
||||
Paint to [URL-Keyed Metrics](https://chromium.googlesource.com/chromium/src/+/main/services/metrics/ukm_api.md).
|
||||
This change increases the number of reports of First Contentful Paint that Chrome
|
||||
receives right before the user closes a tab.
|
||||
[Source code for this change](https://chromium-review.googlesource.com/c/chromium/src/+/2552628).
|
||||
|
||||
@ -53,7 +53,7 @@ For some jobs, this work is executed by the tester instead.
|
||||
|
||||
* [Perf Sheriff Rotation](perf_regression_sheriffing.md)
|
||||
* [Perfbot Health Sheriffing Rotation](bot_health_sheriffing/main.md)
|
||||
* [How to SSH to Bots in Lab](https://chrome-internal.googlesource.com/infra/infra_internal/+/master/doc/ssh.md)
|
||||
* [How to SSH to Bots in Lab](https://chrome-internal.googlesource.com/infra/infra_internal/+/main/doc/ssh.md)
|
||||
(googlers only!)
|
||||
* TODO: Page on how to repro failures locally
|
||||
* TODO: Page on how to hack on buildbot/recipe code
|
||||
|
||||
@ -16,7 +16,7 @@ memory for idle and backgrounded tabs.
|
||||
* [Mailing List](https://groups.google.com/a/chromium.org/forum/#!forum/memory-dev)
|
||||
* Performance-Memory [Bug
|
||||
Queue](https://bugs.chromium.org/p/chromium/issues/list?can=2&q=Performance%3DMemory)
|
||||
* [Docs](https://chromium.googlesource.com/chromium/src/+/master/docs/memory)
|
||||
* [Docs](https://chromium.googlesource.com/chromium/src/+/main/docs/memory)
|
||||
|
||||
## Power
|
||||
|
||||
|
||||
@ -1,10 +1,10 @@
|
||||
# Metadata information for this directory.
|
||||
#
|
||||
# For more information on DIR_METADATA files, see:
|
||||
# https://source.chromium.org/chromium/infra/infra/+/master:go/src/infra/tools/dirmd/README.md
|
||||
# https://source.chromium.org/chromium/infra/infra/+/main:go/src/infra/tools/dirmd/README.md
|
||||
#
|
||||
# For the schema of this file, see Metadata message:
|
||||
# https://source.chromium.org/chromium/infra/infra/+/master:go/src/infra/tools/dirmd/proto/dir_metadata.proto
|
||||
# https://source.chromium.org/chromium/infra/infra/+/main:go/src/infra/tools/dirmd/proto/dir_metadata.proto
|
||||
|
||||
monorail {
|
||||
component: "Blink>PerformanceAPIs"
|
||||
|
||||
@ -22,7 +22,7 @@ incentives they need to improve it. We aim to:
|
||||
Chrome needs a small, consistent set of high quality user experience metrics.
|
||||
Chrome Speed Metrics is responsible for authoring reference implementations of
|
||||
these metrics implemented using Trace Based Metrics v2 (TBMv2) in
|
||||
[tracing/metrics](https://source.chromium.org/chromium/chromium/src/+/master:third_party/catapult/tracing/tracing/metrics/).
|
||||
[tracing/metrics](https://source.chromium.org/chromium/chromium/src/+/main:third_party/catapult/tracing/tracing/metrics/).
|
||||
These reference implementations will often require adding C++ instrumentation.
|
||||
Some metrics work will also be driven by more focused metrics teams, such as the
|
||||
work on Frame Throughput. Chrome Speed Metrics also owns UMA/UKM metrics, and
|
||||
@ -51,7 +51,7 @@ improve Chrome’s UX.
|
||||
|
||||
### Own Core Metrics
|
||||
The Chrome Speed Metrics team will gradually gain ownership of
|
||||
[tracing/metrics](https://source.chromium.org/chromium/chromium/src/+/master:third_party/catapult/tracing/tracing/metrics/),
|
||||
[tracing/metrics](https://source.chromium.org/chromium/chromium/src/+/main:third_party/catapult/tracing/tracing/metrics/),
|
||||
and will be responsible for the long term code health of this directory. We’re
|
||||
also ramping up ownership in the Web Perf API space.
|
||||
|
||||
|
||||
@ -90,7 +90,7 @@
|
||||
* **Largest Contentful Paint**: include removed nodes ([bug](https://bugs.chromium.org/p/chromium/issues/detail?id=1045640))
|
||||
and ignored images occupying the full viewport ([bug](https://bugs.chromium.org/p/chromium/issues/detail?id=1133883)).
|
||||
* **Cumulative Layout Shift**: implemented various fixes, see
|
||||
[changelog](https://chromium.googlesource.com/chromium/src/+/master/docs/speed/metrics_changelog/README.md).
|
||||
[changelog](https://chromium.googlesource.com/chromium/src/+/main/docs/speed/metrics_changelog/README.md).
|
||||
|
||||
## 2020 Q4 Objectives
|
||||
|
||||
@ -156,7 +156,7 @@
|
||||
* [LargestContentfulPaint](#lcp-20203):
|
||||
* Did analysis on how LCP would change when removed content is included.
|
||||
* Ignored paints occurring with opacity 0.
|
||||
* CumulativeLayoutShift [fixes](https://chromium.googlesource.com/chromium/src/+/master/docs/speed/metrics_changelog/cls.md):
|
||||
* CumulativeLayoutShift [fixes](https://chromium.googlesource.com/chromium/src/+/main/docs/speed/metrics_changelog/cls.md):
|
||||
* Ignored shifts from video thumb sliders.
|
||||
* Fixed computations for ink overflow and transforms.
|
||||
* Updated computations when child moves alongside their parent element.
|
||||
|
||||
@ -1,10 +1,10 @@
|
||||
# Metadata information for this directory.
|
||||
#
|
||||
# For more information on DIR_METADATA files, see:
|
||||
# https://source.chromium.org/chromium/infra/infra/+/master:go/src/infra/tools/dirmd/README.md
|
||||
# https://source.chromium.org/chromium/infra/infra/+/main:go/src/infra/tools/dirmd/README.md
|
||||
#
|
||||
# For the schema of this file, see Metadata message:
|
||||
# https://source.chromium.org/chromium/infra/infra/+/master:go/src/infra/tools/dirmd/proto/dir_metadata.proto
|
||||
# https://source.chromium.org/chromium/infra/infra/+/main:go/src/infra/tools/dirmd/proto/dir_metadata.proto
|
||||
|
||||
monorail {
|
||||
component: "Services>Sync"
|
||||
|
||||
@ -1,10 +1,10 @@
|
||||
# Metadata information for this directory.
|
||||
#
|
||||
# For more information on DIR_METADATA files, see:
|
||||
# https://source.chromium.org/chromium/infra/infra/+/master:go/src/infra/tools/dirmd/README.md
|
||||
# https://source.chromium.org/chromium/infra/infra/+/main:go/src/infra/tools/dirmd/README.md
|
||||
#
|
||||
# For the schema of this file, see Metadata message:
|
||||
# https://source.chromium.org/chromium/infra/infra/+/master:go/src/infra/tools/dirmd/proto/dir_metadata.proto
|
||||
# https://source.chromium.org/chromium/infra/infra/+/main:go/src/infra/tools/dirmd/proto/dir_metadata.proto
|
||||
|
||||
monorail {
|
||||
component: "Test"
|
||||
|
||||
@ -30,12 +30,12 @@ test, and ensure each test resets to that state.
|
||||
|
||||
If a few tests within a larger batched suite cannot be batched (eg. it tests
|
||||
process initialization), you may add the
|
||||
[@RequiresRestart](https://source.chromium.org/chromium/chromium/src/+/master:base/test/android/javatests/src/org/chromium/base/test/util/RequiresRestart.java;bpv=1;bpt=1;l=19?q=RequiresRestart&ss=chromium%2Fchromium%2Fsrc&originalUrl=https:%2F%2Fcs.chromium.org%2F&gsn=RequiresRestart&gs=kythe%3A%2F%2Fchromium.googlesource.com%2Fchromium%2Fsrc%3Flang%3Djava%3Fpath%3Dorg.chromium.base.test.util.RequiresRestart%23b5e85d5c8071e18f350b7f2c5014310bd2cabd0e0d3d176949c991ea18403f55)
|
||||
[@RequiresRestart](https://source.chromium.org/chromium/chromium/src/+/main:base/test/android/javatests/src/org/chromium/base/test/util/RequiresRestart.java;bpv=1;bpt=1;l=19?q=RequiresRestart&ss=chromium%2Fchromium%2Fsrc&originalUrl=https:%2F%2Fcs.chromium.org%2F&gsn=RequiresRestart&gs=kythe%3A%2F%2Fchromium.googlesource.com%2Fchromium%2Fsrc%3Flang%3Djava%3Fpath%3Dorg.chromium.base.test.util.RequiresRestart%23b5e85d5c8071e18f350b7f2c5014310bd2cabd0e0d3d176949c991ea18403f55)
|
||||
annotation, which will exclude that test from the batch.
|
||||
|
||||
## Types of Batched tests
|
||||
|
||||
### [UNIT_TESTS](https://source.chromium.org/chromium/chromium/src/+/master:base/test/android/javatests/src/org/chromium/base/test/util/Batch.java;bpv=1;bpt=1;l=51?q=Batch.java&ss=chromium%2Fchromium%2Fsrc&originalUrl=https:%2F%2Fcs.chromium.org%2F&gsn=UNIT_TESTS&gs=kythe%3A%2F%2Fchromium.googlesource.com%2Fchromium%2Fsrc%3Flang%3Djava%3Fpath%3Dorg.chromium.base.test.util.Batch%2319ebd2758adfaed0bda0e97542f70ca5b1564e7c1fa0f8c2bcb9e8170b75684d)
|
||||
### [UNIT_TESTS](https://source.chromium.org/chromium/chromium/src/+/main:base/test/android/javatests/src/org/chromium/base/test/util/Batch.java;bpv=1;bpt=1;l=51?q=Batch.java&ss=chromium%2Fchromium%2Fsrc&originalUrl=https:%2F%2Fcs.chromium.org%2F&gsn=UNIT_TESTS&gs=kythe%3A%2F%2Fchromium.googlesource.com%2Fchromium%2Fsrc%3Flang%3Djava%3Fpath%3Dorg.chromium.base.test.util.Batch%2319ebd2758adfaed0bda0e97542f70ca5b1564e7c1fa0f8c2bcb9e8170b75684d)
|
||||
|
||||
Tests that belong in this category are tests that are effectively unit tests.
|
||||
They may be written as instrumentation tests rather than junit tests for a
|
||||
@ -54,7 +54,7 @@ to take advantage of feature annotations in your test you will have to use
|
||||
Features#JUnitProcessor instead of Features#InstrumentationProcessor.
|
||||
|
||||
|
||||
### [PER_CLASS](https://source.chromium.org/chromium/chromium/src/+/master:base/test/android/javatests/src/org/chromium/base/test/util/Batch.java;bpv=1;bpt=1;l=39?q=Batch.java&ss=chromium%2Fchromium%2Fsrc&originalUrl=https:%2F%2Fcs.chromium.org%2F&gsn=PER_CLASS&gs=kythe%3A%2F%2Fchromium.googlesource.com%2Fchromium%2Fsrc%3Flang%3Djava%3Fpath%3Dorg.chromium.base.test.util.Batch%23780b702db42a1901f05647fd29f75d443bc4efd2db588848b4aedf826ddf9e21)
|
||||
### [PER_CLASS](https://source.chromium.org/chromium/chromium/src/+/main:base/test/android/javatests/src/org/chromium/base/test/util/Batch.java;bpv=1;bpt=1;l=39?q=Batch.java&ss=chromium%2Fchromium%2Fsrc&originalUrl=https:%2F%2Fcs.chromium.org%2F&gsn=PER_CLASS&gs=kythe%3A%2F%2Fchromium.googlesource.com%2Fchromium%2Fsrc%3Flang%3Djava%3Fpath%3Dorg.chromium.base.test.util.Batch%23780b702db42a1901f05647fd29f75d443bc4efd2db588848b4aedf826ddf9e21)
|
||||
|
||||
This batching type is typically for larger and more complex test suites, and
|
||||
will run the suite in its own batch. This will reduce the complexity of managing
|
||||
@ -74,7 +74,7 @@ batch instead of once per test suite. To put multiple test suites into the same
|
||||
batch, you will have to use a shared custom batch name
|
||||
([example](https://chromium-review.googlesource.com/c/chromium/src/+/2307650)).
|
||||
When batching across suites you’ll want to use something like
|
||||
[BlankCTATabInitialStateRule](https://source.chromium.org/chromium/chromium/src/+/master:chrome/test/android/javatests/src/org/chromium/chrome/test/batch/BlankCTATabInitialStateRule.java?q=BlankCTATabInitialStateRule&ss=chromium&originalUrl=https:%2F%2Fcs.chromium.org%2F)
|
||||
[BlankCTATabInitialStateRule](https://source.chromium.org/chromium/chromium/src/+/main:chrome/test/android/javatests/src/org/chromium/chrome/test/batch/BlankCTATabInitialStateRule.java?q=BlankCTATabInitialStateRule&ss=chromium&originalUrl=https:%2F%2Fcs.chromium.org%2F)
|
||||
to persist static state (like the Activity) between test suites and perform any
|
||||
necessary state cleanup between tests.
|
||||
|
||||
@ -99,7 +99,7 @@ that. Other common state like SharedPreferences
|
||||
any heavy work in them (and will run twice for parameterized tests). See
|
||||
[issue 1090043](https://crbug.com/1090043).
|
||||
* Sometimes it can be very difficult to figure out which test in a batch is
|
||||
causing another test to fail. A good first step is to minimize [_TEST_BATCH_MAX_GROUP_SIZE](https://source.chromium.org/chromium/chromium/src/+/master:build/android/pylib/local/device/local_device_instrumentation_test_run.py;drc=3ab9a142091516aa57f10feebc46dee649ae4589;l=109)
|
||||
causing another test to fail. A good first step is to minimize [_TEST_BATCH_MAX_GROUP_SIZE](https://source.chromium.org/chromium/chromium/src/+/main:build/android/pylib/local/device/local_device_instrumentation_test_run.py;drc=3ab9a142091516aa57f10feebc46dee649ae4589;l=109)
|
||||
to minimize the number of tests within the batch while still reproducing the
|
||||
failure. Then, you can use multiple gtest filter patterns to control which tests
|
||||
run together. Ex:
|
||||
|
||||
@ -305,12 +305,12 @@ reported usually grows after that.
|
||||
### How can I improve [coverage dashboard]?
|
||||
|
||||
The code for the service and dashboard currently lives along with findit at
|
||||
[this location](https://chromium.googlesource.com/infra/infra/+/master/appengine/findit/)
|
||||
[this location](https://chromium.googlesource.com/infra/infra/+/main/appengine/findit/)
|
||||
because of significant shared logic.
|
||||
|
||||
The code used by the bots that generate the coverage data lives (among other
|
||||
places) in the
|
||||
[code coverage recipe module](https://chromium.googlesource.com/chromium/tools/build/+/master/scripts/slave/recipe_modules/code_coverage/).
|
||||
[code coverage recipe module](https://chromium.googlesource.com/chromium/tools/build/+/main/scripts/slave/recipe_modules/code_coverage/).
|
||||
|
||||
### Why is coverage for X not reported or unreasonably low, even though there is a test for X?
|
||||
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user