0

Fix references to moved files in documentation.

Bug: 1255932
Change-Id: Id76970abfa7262ede732ff0d1ffefa36e4a8f5a0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3219351
Reviewed-by: John Chen <johnchen@chromium.org>
Reviewed-by: Jeremy Roman <jbroman@chromium.org>
Reviewed-by: Eric Orth <ericorth@chromium.org>
Commit-Queue: Patrick Monette <pmonette@chromium.org>
Cr-Commit-Position: refs/heads/main@{#936987}
This commit is contained in:
Patrick Monette
2021-11-01 19:20:22 +00:00
committed by Chromium LUCI CQ
parent 6994b91fbc
commit 2d93ad9012
4 changed files with 7 additions and 7 deletions
chrome/test/chromedriver/docs
docs
net/dns
third_party/blink/tools/blinkpy/presubmit

@ -21,7 +21,7 @@ to post tasks between threads.
Each thread in ChromeDriver is wrapped by a
[`base::Thread`](https://source.chromium.org/chromium/chromium/src/+/main:base/threading/thread.h?q=%22class%20BASE_EXPORT%20Thread%22) object.
This object exposes a
[`base::TaskRunner`](https://source.chromium.org/chromium/chromium/src/+/main:base/task_runner.h?q=base::TaskRunner),
[`base::TaskRunner`](https://source.chromium.org/chromium/chromium/src/+/main:base/task/task_runner.h?q=base::TaskRunner),
which provides the ability to post tasks to that thread.\
When thread A wants to call a function on thread B, it finds the `TaskRunner`
object corresponding to thread B, and calls its `TaskRunner::PostTask` method.\

@ -203,7 +203,7 @@ base::ThreadPool::PostTask(
### Posting via a TaskRunner
A parallel
[`base::TaskRunner`](https://cs.chromium.org/chromium/src/base/task_runner.h) is
[`base::TaskRunner`](https://cs.chromium.org/chromium/src/base/task/task_runner.h) is
an alternative to calling `base::ThreadPool::PostTask*()` directly. This is
mainly useful when it isnt known in advance whether tasks will be posted in
parallel, in sequence, or to a single-thread (ref. [Posting a Sequenced
@ -240,7 +240,7 @@ less invasive ways of controlling tasks in tests).
A sequence is a set of tasks that run one at a time in posting order (not
necessarily on the same thread). To post tasks as part of a sequence, use a
[`base::SequencedTaskRunner`](https://cs.chromium.org/chromium/src/base/sequenced_task_runner.h).
[`base::SequencedTaskRunner`](https://cs.chromium.org/chromium/src/base/task/sequenced_task_runner.h).
### Posting to a New Sequence
@ -340,7 +340,7 @@ thread/sequence is covered in the PostTask sections above.
## Posting Multiple Tasks to the Same Thread
If multiple tasks need to run on the same thread, post them to a
[`base::SingleThreadTaskRunner`](https://cs.chromium.org/chromium/src/base/single_thread_task_runner.h).
[`base::SingleThreadTaskRunner`](https://cs.chromium.org/chromium/src/base/task/single_thread_task_runner.h).
All tasks posted to the same `base::SingleThreadTaskRunner` run on the same thread in
posting order.

@ -219,7 +219,7 @@ Specific sources for a request can be
specified using `net::HostResolver::ResolveHostParameters::source` and
[`net::HostResolverSource`](/net/dns/host_resolver_source.h).
The Job will then use *Task objects that implement the behavior specific to the
The Job will then use \*Task objects that implement the behavior specific to the
particular resolution sources.
#### SYSTEM
@ -249,7 +249,7 @@ always be used for **address resolves** when **any** of the following are true:
Secure DNS requests cannot be made using the system resolver.
`net::HostResolverManager::ProcTask` uses a blocking
[`base::TaskRunner`](/base/task_runner.h) to make blocking resolution requests.
[`base::TaskRunner`](/base/task/task_runner.h) to make blocking resolution requests.
On a timeout, additional attempts are made, but previous attempts are not
cancelled as there is no cancellation mechanism for `getaddrinfo()`. The first
attempt to complete is used and any other attempt completions are ignored.

@ -112,7 +112,7 @@ _CONFIG = [
# //base/allocator/partition_allocator/partition_alloc_constants.h
'base::kAlignment',
# //base/bind_post_task.h
# //base/task/bind_post_task.h
'base::BindPostTask',
# //base/bits.h