about summary refs log tree commit diff
path: root/src/test/stdtest/task.rs
AgeCommit message (Collapse)AuthorLines
2012-01-17libcore: Move core tests into libcoreBrian Anderson-80/+0
2012-01-13libcore: Add task::tryBrian Anderson-0/+21
2012-01-11add section on spawn_connected to tutorial and pull test into fileNiko Matsakis-19/+0
2012-01-08add spawn_connectedNiko Matsakis-0/+19
2012-01-06fix how we walk functions to match new closure fmtNiko Matsakis-1/+1
2012-01-06port over the tests to use the new APINiko Matsakis-4/+4
2012-01-06rewrite task testsNiko Matsakis-35/+17
2012-01-05Switch to new param kind bound syntaxMarijn Haverbeke-1/+1
And remove support for the old syntax
2011-12-22Register new snapshots, purge log_err and log_full in favour of log(...).Graydon Hoare-3/+3
2011-12-22Register snapshots and switch logging over to use of log_full or #error / ↵Graydon Hoare-6/+6
#debug.
2011-12-13Copy first batch of material from libstd to libcore.Graydon Hoare-2/+4
2011-11-18Update stdlib, compiler, and tests to new kind systemMarijn Haverbeke-1/+1
This involved adding 'copy' to more generics than I hoped, but an experiment with making it implicit showed that that way lies madness -- unless enforced, you will not remember to mark functions that don't copy as not requiring copyable kind. Issue #1177
2011-10-29Cleanup the existing platform-specific ignored testsBrian Anderson-14/+2
2011-10-28Move to short kind kinds words in test suiteMarijn Haverbeke-1/+1
Issue #1076
2011-10-25Update our code to new type parameter kind syntaxMarijn Haverbeke-1/+1
Closes #1067
2011-10-20Remove temporary fn# syntaxBrian Anderson-7/+7
2011-10-20Get windows working under the bare function regimeBrian Anderson-0/+16
Had to ignore some task failure tests due to the current implementation of spawn which guarantees that there's always something in the spawned task that needs to be unwound. Fixed some win-specific build problems.
2011-10-20Drop the 2 from the spawn*2 functionsBrian Anderson-8/+8
Issue #1022
2011-10-20Convert tests to use bare-fn spawnBrian Anderson-22/+17
Issue #1022
2011-09-12Pretty-print for new arg-mode syntaxMarijn Haverbeke-1/+1
2011-09-02Reformat. Issue #855Brian Anderson-4/+2
2011-08-26Adding a test case to make sure spawning polymorphic functions works.Eric Holk-0/+12
2011-08-25Cleaning up task and comm exports, updating all the test cases.Eric Holk-25/+9
2011-08-20ReformatBrian Anderson-4/+4
This changes the indexing syntax from .() to [], the vector syntax from ~[] to [] and the extension syntax from #fmt() to #fmt[]
2011-08-17Convenience methods for spawning and joining tasks.Eric Holk-0/+8
2011-08-17Using move-mode for spawn thunks to avoid race conditions.Eric Holk-4/+8
2011-08-16Updating to new type parameter syntax.Eric Holk-2/+2
2011-08-16New channel-based task status notifications.Eric Holk-0/+32
2011-08-16Removed trans_comm.rs from the compiler. Updating aio/sio to work with the ↵Eric Holk-8/+0
new chan and port system, started on a networking module for the standard library.
2011-08-15Removed spawn and task from the parser. Updated all the tests except for the ↵Eric Holk-5/+5
benchmarks.
2011-08-15Fixed memory accounting and task stack creation bugs.Eric Holk-1/+1
2011-08-15Working on more spawn test cases.Eric Holk-0/+6
2011-08-15Added a library version of spawn. Before long, we can remove the old version.Eric Holk-0/+5
2011-08-11Un-ignore stdtest::task::test_sleepBrian Anderson-1/+0
Works for me.
2011-07-27Remove task::workerBrian Anderson-23/+0
It was too unsafe to live. It already apeared to be causing problems with eholk's incoming task changes, so I'm killing it now before it can spread.
2011-07-27Reformat for new syntaxMarijn Haverbeke-37/+31
2011-07-24Add task::send and task::recvBrian Anderson-0/+8
2011-07-24Add task::worker. Spawns a task and returns a channel to itBrian 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-24Reindent lib-task.rsBrian Anderson-15/+15
2011-07-24The Big Test Suite OverhaulBrian Anderson-0/+34
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.