rust/src/compiletest/compiletest.rs, branch 1.3.0https://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=1.3.02015-07-11T21:47:56+00:00Implement RFC 10582015-07-11T21:47:56+00:00Simonas Kazlauskasgit@kazlauskas.me2015-07-11T11:34:57+00:00urn:sha1:7a90865db5b9bbf4e94580a886e3ab187d91c83cFallout in tests and docs from feature renamings2015-06-17T16:07:16+00:00Alex Crichtonalex@alexcrichton.com2015-06-10T20:33:52+00:00urn:sha1:ce1a965cf54ce65fc43b535c27029ce183214063compiletest: remove JIT2015-06-13T16:53:07+00:00Tamir Dubersteintamird@gmail.com2015-06-13T16:53:07+00:00urn:sha1:7f04b8ff07ba0c27c2aef957d7aa3ed4404fc877Revamp codegen tests to check IR quality instead of quantity2015-05-27T10:08:31+00:00Björn Steinbrinkbsteinbr@gmail.com2015-05-24T16:07:52+00:00urn:sha1:677367599e8383c355b8e8261cafe3ce44c9c6de
The current codegen tests only compare IR line counts between similar
rust and C programs, the latter getting compiled with clang. That looked
like a good idea back then, but actually things like lifetime intrinsics
mean that less IR isn't always better, so the metric isn't really
helpful.
Instead, we can start doing tests that check specific aspects of the
generated IR, like attributes or metadata. To do that, we can use LLVM's
FileCheck tool which has a number of useful features for such tests.
To start off, I created some tests for a few things that were recently
added and/or broken.
Squeeze the last bits of `task`s in documentation in favor of `thread`2015-05-08T17:24:18+00:00Barosl Leevcs@barosl.com2015-05-08T15:12:29+00:00urn:sha1:ff332b6467b2b93831c3f0ae3665e920ec725959
An automated script was run against the `.rs` and `.md` files,
subsituting every occurrence of `task` with `thread`. In the `.rs`
files, only the texts in the comment blocks were affected.
Run benchmarks once, as a test by default.2015-05-02T05:45:23+00:00Huon Wilsondbau.pp+github@gmail.com2015-05-02T03:38:51+00:00urn:sha1:d73545ceca711f88e3e79120c77fa83c2a1994e7
E.g. if `foo.rs` looks like
#![feature(test)]
extern crate test;
#[bench]
fn bar(b: &mut test::Bencher) {
b.iter(|| {
1
})
}
#[test]
fn baz() {}
#[bench]
fn qux(b: &mut test::Bencher) {
b.iter(|| {
panic!()
})
}
Then
$ rustc --test foo.rs
$ ./foo
running 3 tests
test baz ... ok
test qux ... FAILED
test bar ... ok
failures:
---- qux stdout ----
thread 'qux' panicked at 'explicit panic', bench.rs:17
failures:
qux
test result: FAILED. 2 passed; 1 failed; 0 ignored; 0 measured
$ ./foo --bench ba
running 2 tests
test baz ... ignored
test bar ... bench: 97 ns/iter (+/- 74)
test result: ok. 0 passed; 0 failed; 1 ignored; 1 measured
In particular, the two benchmark are being run as tests in the default
mode.
This helps for the main distribution, since benchmarks are only run with
`PLEASE_BENCH=1`, which is rarely set (and never set on the test bots),
and helps for code-coverage tools: benchmarks are run and so don't count
as dead code.
Fixes #15842.
Negative case of `len()` -> `is_empty()`2015-04-15T03:26:03+00:00Tamir Dubersteintamird@gmail.com2015-03-24T23:54:09+00:00urn:sha1:10f15e72e6c265eb43d34dba564d86dbf1c4fb99
`s/([^\(\s]+\.)len\(\) [(?:!=)>] 0/!$1is_empty()/g`
More test fixes2015-04-14T17:14:19+00:00Alex Crichtonalex@alexcrichton.com2015-04-10T20:51:53+00:00urn:sha1:b8760afe478f5f2e10687b70146ac7123df2319bcompiletest: Re-add raise_fd_limit2015-04-14T17:14:11+00:00Alex Crichtonalex@alexcrichton.com2015-04-10T17:36:13+00:00urn:sha1:84a89ed3effb37c86ca686adbb447275f3562a09
This apparently fixes obscure bugs on OSX!
compiletest: Add support for running rustdoc tests2015-04-08T00:54:33+00:00Alex Crichtonalex@alexcrichton.com2015-04-06T20:48:17+00:00urn:sha1:10359de4051d56feeacd455946b93ec48e6511fc
Add a new test directory called 'rustdoc' where all files inside are documented
and run against the `htmldocck` script to have assertions about the output.