2016-09-02 08:55:29 +00:00
|
|
|
[workspace]
|
|
|
|
members = [
|
|
|
|
"bootstrap",
|
|
|
|
"rustc",
|
2017-02-15 16:53:18 +00:00
|
|
|
"libstd",
|
|
|
|
"libtest",
|
2016-09-02 08:55:29 +00:00
|
|
|
"tools/cargotest",
|
|
|
|
"tools/compiletest",
|
|
|
|
"tools/error_index_generator",
|
|
|
|
"tools/linkchecker",
|
|
|
|
"tools/rustbook",
|
2017-06-12 19:35:47 +00:00
|
|
|
"tools/unstable-book-gen",
|
2016-09-02 08:55:29 +00:00
|
|
|
"tools/tidy",
|
2017-01-24 22:37:04 +00:00
|
|
|
"tools/build-manifest",
|
travis: Parallelize tests on Android
Currently our slowest test suite on android, run-pass, takes over 5 times longer
than the x86_64 component (~400 -> ~2200s). Typically QEMU emulation does indeed
add overhead, but not 5x for this kind of workload. One of the slowest parts of
the Android process is that *compilation* happens serially. Tests themselves
need to run single-threaded on the emulator (due to how the test harness works)
and this forces the compiles themselves to be single threaded.
Now Travis gives us more than one core per machine, so it'd be much better if we
could take advantage of them! The emulator itself is still fundamentally
single-threaded, but we should see a nice speedup by sending binaries for it to
run much more quickly.
It turns out that we've already got all the tools to do this in-tree. The
qemu-test-{server,client} that are in use for the ARM Linux testing are a
perfect match for the Android emulator. This commit migrates the custom adb
management code in compiletest/rustbuild to the same qemu-test-{server,client}
implementation that ARM Linux uses.
This allows us to lift the parallelism restriction on the compiletest test
suites, namely run-pass. Consequently although we'll still basically run the
tests themselves in single threaded mode we'll be able to compile all of them in
parallel, keeping the pipeline much more full and using more cores for the work
at hand. Additionally the architecture here should be a bit speedier as it
should have less overhead than adb which is a whole new process on both the host
and the emulator!
Locally on an 8 core machine I've seen the run-pass test suite speed up from
taking nearly an hour to only taking 6 minutes. I don't think we'll see quite a
drastic speedup on Travis but I'm hoping this change can place the Android tests
well below 2 hours instead of just above 2 hours.
Because the client/server here are now repurposed for more than just QEMU,
they've been renamed to `remote-test-{server,client}`.
Note that this PR does not currently modify how debuginfo tests are executed on
Android. While parallelizable it wouldn't be quite as easy, so that's left to
another day. Thankfully that test suite is much smaller than the run-pass test
suite.
As a final fix I discovered that the ARM and Android test suites were actually
running all library unit tests (e.g. stdtest, coretest, etc) twice. I've
corrected that to only run tests once which should also give a nice boost in
overall cycle time here.
2017-04-26 15:52:19 +00:00
|
|
|
"tools/remote-test-client",
|
|
|
|
"tools/remote-test-server",
|
2017-05-08 22:01:13 +00:00
|
|
|
"tools/rust-installer",
|
2017-04-20 21:32:54 +00:00
|
|
|
"tools/cargo",
|
2017-07-23 02:01:58 +00:00
|
|
|
"tools/rustdoc",
|
2017-04-20 21:32:54 +00:00
|
|
|
"tools/rls",
|
2017-06-30 18:58:54 +00:00
|
|
|
# FIXME(https://github.com/rust-lang/cargo/issues/4089): move these to exclude
|
|
|
|
"tools/rls/test_data/borrow_error",
|
|
|
|
"tools/rls/test_data/completion",
|
|
|
|
"tools/rls/test_data/find_all_refs",
|
|
|
|
"tools/rls/test_data/find_all_refs_no_cfg_test",
|
|
|
|
"tools/rls/test_data/goto_def",
|
|
|
|
"tools/rls/test_data/highlight",
|
|
|
|
"tools/rls/test_data/hover",
|
|
|
|
"tools/rls/test_data/rename",
|
|
|
|
"tools/rls/test_data/reformat",
|
|
|
|
"tools/rls/test_data/bin_lib_no_cfg_test",
|
|
|
|
"tools/rls/test_data/multiple_bins",
|
|
|
|
"tools/rls/test_data/bin_lib",
|
|
|
|
"tools/rls/test_data/reformat_with_range",
|
2017-08-24 05:52:28 +00:00
|
|
|
"tools/rls/test_data/find_impls",
|
|
|
|
"tools/rls/test_data/infer_bin",
|
|
|
|
"tools/rls/test_data/infer_custom_bin",
|
|
|
|
"tools/rls/test_data/infer_lib",
|
|
|
|
"tools/rls/test_data/omit_init_build",
|
2017-04-20 21:32:54 +00:00
|
|
|
]
|
|
|
|
|
2017-05-20 16:33:53 +00:00
|
|
|
# Curiously, compiletest will segfault if compiled with opt-level=3 on 64-bit
|
|
|
|
# MSVC when running the compile-fail test suite when a should-fail test panics.
|
|
|
|
# But hey if this is removed and it gets past the bots, sounds good to me.
|
|
|
|
[profile.release]
|
|
|
|
opt-level = 2
|
|
|
|
[profile.bench]
|
|
|
|
opt-level = 2
|
|
|
|
|
2016-11-16 17:19:02 +00:00
|
|
|
# These options are controlled from our rustc wrapper script, so turn them off
|
|
|
|
# here and have them controlled elsewhere.
|
|
|
|
[profile.dev]
|
|
|
|
debug = false
|
|
|
|
debug-assertions = false
|
|
|
|
[profile.test]
|
|
|
|
debug = false
|
|
|
|
debug-assertions = false
|
2017-04-29 23:11:58 +00:00
|
|
|
|
2017-08-28 15:57:37 +00:00
|
|
|
[patch.'https://github.com/rust-lang/cargo']
|
|
|
|
cargo = { path = "tools/cargo" }
|