summary refs log tree commit diff
path: root/src/doc/rustc-dev-guide
diff options
context:
space:
mode:
authorSantiago Pastorino <spastorino@gmail.com>2020-02-17 16:58:21 -0300
committerWho? Me?! <mark-i-m@users.noreply.github.com>2020-03-17 12:16:02 -0500
commit5f9b355df629cd90d8073b22433c8e239bec58fe (patch)
tree0b7e7672e800afe92f568f4a624d5ae778ffd1c3 /src/doc/rustc-dev-guide
parentce46c24c0c0701277bd33dd270c394a3fcaffad5 (diff)
downloadrust-5f9b355df629cd90d8073b22433c8e239bec58fe.tar.gz
rust-5f9b355df629cd90d8073b22433c8e239bec58fe.zip
It may Take a lot of time instead of 2 hours
Diffstat (limited to 'src/doc/rustc-dev-guide')
-rw-r--r--src/doc/rustc-dev-guide/src/walkthrough.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/src/doc/rustc-dev-guide/src/walkthrough.md b/src/doc/rustc-dev-guide/src/walkthrough.md
index 5d54404efa7..226391e6e85 100644
--- a/src/doc/rustc-dev-guide/src/walkthrough.md
+++ b/src/doc/rustc-dev-guide/src/walkthrough.md
@@ -192,8 +192,8 @@ it.
 When your review approves the PR, it will go into a queue for yet another bot
 called `@bors`.  `@bors` manages the CI build/merge queue. When your PR reaches
 the head of the `@bors` queue, `@bors` will test out the merge by running all
-tests against your PR on Travis CI. This takes about 2 hours as of this
-writing.  If all tests pass, the PR is merged and becomes part of the next
+tests against your PR on Travis CI. This takes may take a lot of time to
+finish. If all tests pass, the PR is merged and becomes part of the next
 nightly compiler!
 
 There are a couple of things that may happen for some PRs during the review process