about summary refs log tree commit diff
path: root/src/doc
diff options
context:
space:
mode:
authorYuki Okushi <huyuumi.dev@gmail.com>2020-07-05 02:40:39 +0900
committerWho? Me?! <mark-i-m@users.noreply.github.com>2020-07-04 13:06:27 -0500
commitf266ef6d85d5aaa2661e7f604acab74e37726111 (patch)
tree166a8cbaedb1c698eecc00501c46e00c4a60f3ae /src/doc
parent8a640ae662e9e3343f8471b0016f414662d1f262 (diff)
downloadrust-f266ef6d85d5aaa2661e7f604acab74e37726111.tar.gz
rust-f266ef6d85d5aaa2661e7f604acab74e37726111.zip
Fix link for armhf-gnu Dockerfile
Diffstat (limited to 'src/doc')
-rw-r--r--src/doc/rustc-dev-guide/src/tests/intro.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/src/doc/rustc-dev-guide/src/tests/intro.md b/src/doc/rustc-dev-guide/src/tests/intro.md
index b772da01102..0f517f8712b 100644
--- a/src/doc/rustc-dev-guide/src/tests/intro.md
+++ b/src/doc/rustc-dev-guide/src/tests/intro.md
@@ -266,7 +266,7 @@ emulation on Travis.  The following will take a look at how a target's tests
 are run under emulation.
 
 The Docker image for [armhf-gnu] includes [QEMU] to emulate the ARM CPU
-architecture.  Included in the Rust tree are the tools [remote-test-client]
+architecture. Included in the Rust tree are the tools [remote-test-client]
 and [remote-test-server] which are programs for sending test programs and
 libraries to the emulator, and running the tests within the emulator, and
 reading the results.  The Docker image is set up to launch
@@ -279,7 +279,7 @@ communicate with the server to coordinate running tests (see
 >
 > It's also unclear to me how the wasm or asm.js tests are run.
 
-[armhf-gnu]: https://github.com/rust-lang/rust/tree/master/src/ci/docker/armhf-gnu
+[armhf-gnu]: https://github.com/rust-lang/rust/tree/master/src/ci/docker/host-x86_64/armhf-gnu/Dockerfile
 [QEMU]: https://www.qemu.org/
 [remote-test-client]: https://github.com/rust-lang/rust/tree/master/src/tools/remote-test-client
 [remote-test-server]: https://github.com/rust-lang/rust/tree/master/src/tools/remote-test-server