about summary refs log tree commit diff
path: root/src/liballoc_jemalloc
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2018-04-04 15:38:10 +0000
committerbors <bors@rust-lang.org>2018-04-04 15:38:10 +0000
commit17fea66ba46bb32d1a49495518d899cede1d298a (patch)
tree53b6b618b54b8d795f4f612339df31bf6626da98 /src/liballoc_jemalloc
parent5758c2dd14fd29caf7c7bb2123eb6b23443b9233 (diff)
parent184d3bca6cc1ac2023bbd723223d1a9bd4d4380b (diff)
downloadrust-17fea66ba46bb32d1a49495518d899cede1d298a.tar.gz
rust-17fea66ba46bb32d1a49495518d899cede1d298a.zip
Auto merge of #48913 - Mark-Simulacrum:rustbuild-test, r=alexcrichton
Add tests to rustbuild

In order to run tests, we cfg out various parts of rustbuild. Generally
speaking, these are filesystem and process-spawning operations. Then, rustbuild
is run "as normal" and the various steps that where run are retrieved from the
cache and checked against the expected results.

Note that this means that the current implementation primarily tests "what" we
build, but doesn't actually test that what we build *will* build. In other
words, it doesn't do any form of dependency verification for any crate. This is
possible to implement, but is considered future work.

This implementation strives to cfg out as little code as possible; it also does
not currently test anywhere near all of rustbuild. The current tests are also
not checked for "correctness," rather, they simply represent what we do as of
this commit, which may be wrong.

Test cases are drawn from the old implementation of rustbuild, though the
expected results may vary.

r? @alexcrichton
Diffstat (limited to 'src/liballoc_jemalloc')
0 files changed, 0 insertions, 0 deletions