# Plan to test parallel rustc

**URL:** <https://internals.rust-lang.org/t/plan-to-test-parallel-rustc/11487>\
**Category:** announcements\
**Created:** [December 16, 2019, 9:08pm UTC](https://internals.rust-lang.org/t/plan-to-test-parallel-rustc/11487 "2019-12-16T21:08:56Z")\
**Posts on this page:** 1\
**Showing post:** 29

<div class="post-metadata">

**Author:** ![Ixrec](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/ixrec/32/6754_2.png) [@Ixrec](https://internals.rust-lang.org/u/Ixrec)\
**Post date:** [December 19, 2019, 8:12pm UTC](https://internals.rust-lang.org/t/plan-to-test-parallel-rustc/11487/29 "2019-12-19T20:12:07Z")

</div>

AFAIK, a huge part of the point of asking the public to test this is so that they can test it on _their_ code, including private codebases not published to [crates.io](http://crates.io), so asking everyone to use the same crates would not even be testing what we want to test anymore (especially since it's still limited to 4 threads by default, so a lot of hardware variation won't kick in yet).

> [@pythoneer](#):
>
> a script that would automatically install the needed compiler versions, ... and invokes the different scenarios

The first post of the sister thread basically is that already; it lists 10 shell commands that do all of these steps: [Help test parallel rustc!](https://internals.rust-lang.org/t/help-test-parallel-rustc/11503)

---

_[View the full topic](https://internals.rust-lang.org/t/plan-to-test-parallel-rustc/11487)._