rust - https://github.com/rust-lang/rust

Age	Commit message (Collapse)	Author	Lines
2011-07-24	Add task::worker. Spawns a task and returns a channel to it	Brian Anderson	-0/+23
	It takes a lot of boilerplate to create a task and establish a way to talk to it. This function simplifies that, allowing you to write something like 'worker(f).chan <\| start'. Implementation is very unsafe and only works for a few types of channels, but something like this is very useful.
2011-07-24	Reindent lib-task.rs	Brian Anderson	-15/+15

2011-07-24	The Big Test Suite Overhaul	Brian Anderson	-1/+2525
	This replaces the make-based test runner with a set of Rust-based test runners. I believe that all existing functionality has been preserved. The primary objective is to dogfood the Rust test framework. A few main things happen here: 1) The run-pass/lib-* tests are all moved into src/test/stdtest. This is a standalone test crate intended for all standard library tests. It compiles to build/test/stdtest.stageN. 2) rustc now compiles into yet another build artifact, this one a test runner that runs any tests contained directly in the rustc crate. This allows much more fine-grained unit testing of the compiler. It compiles to build/test/rustctest.stageN. 3) There is a new custom test runner crate at src/test/compiletest that reproduces all the functionality for running the compile-fail, run-fail, run-pass and bench tests while integrating with Rust's test framework. It compiles to build/test/compiletest.stageN. 4) The build rules have been completely changed to use the new test runners, while also being less redundant, following the example of the recent stageN.mk rewrite. It adds two new features to the cfail/rfail/rpass/bench tests: 1) Tests can specify multiple 'error-pattern' directives which must be satisfied in order. 2) Tests can specify a 'compile-flags' directive which will make the test runner provide additional command line arguments to rustc. There are some downsides, the primary being that Rust has to be functioning pretty well just to run _any_ tests, which I imagine will be the source of some frustration when the entire test suite breaks. Will also cause some headaches during porting. Not having individual make rules, each rpass, etc test no longer remembers between runs whether it completed successfully. As a result, it's not possible to incrementally fix multiple tests by just running 'make check', fixing a test, and repeating without re-running all the tests contained in the test runner. Instead you can filter just the tests you want to run by using the TESTNAME environment variable. This also dispenses with the ability to run stage0 tests, but they tended to be broken more often than not anyway.
2011-07-16	Removing error logging from test	Brian Anderson	-1/+0

2011-07-16	Sort tests before running them. Issue #428	Brian Anderson	-0/+45

2011-07-16	Remove unused variable from test tests	Brian Anderson	-1/+1

2011-07-14	Add a flag to run ignored tests. Issue #428	Brian Anderson	-0/+40

2011-07-14	Add a facility for ignoring tests. Issue #428	Brian Anderson	-0/+37
	Adding the #[ignore] attribute will cause the test not to be run, though it will still show up in the list of tests.
2011-07-09	Add sha1 and int tests to stdtest. Issue #428	Brian Anderson	-0/+110

2011-07-06	Add a stdtest crate to hold the standard library tests	Brian Anderson	-0/+10
	This will link to std and compile with the --test flag. Eventually the run-pass/lib* tests will move here. We could also put the std tests directly into the library and compile both a library version and a test version, but I think this way will make for faster builds. Issue #428