| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2011-12-13 | Copy first batch of material from libstd to libcore. | Graydon Hoare | -1/+1 | |
| 2011-11-17 | remove compile-command from local variable blocks | Niko Matsakis | -1/+0 | |
| 2011-11-11 | Rehabilitate run-pass/task-killjoin.rs | Brian Anderson | -9/+7 | |
| 2011-08-31 | Replace xfail-stageN with simply xfail-test | Marijn Haverbeke | -3/+1 | |
| Closes #799 | ||||
| 2011-08-31 | Revert "Replace xfail-stageN with simply xfail-test" | Marijn Haverbeke | -1/+3 | |
| This reverts commit 574194f6bcfb90b9f8486002b83babc4c21208c0. | ||||
| 2011-08-31 | Replace xfail-stageN with simply xfail-test | Marijn Haverbeke | -3/+1 | |
| Closes #799 | ||||
| 2011-08-17 | Using move-mode for spawn thunks to avoid race conditions. | Eric Holk | -2/+4 | |
| 2011-08-15 | XFAIL run-pass/task-killjoin | Brian Anderson | -0/+4 | |
| Seems to be failing with some consistency | ||||
| 2011-08-15 | Porting a bunch of tests over. | Eric Holk | -4/+4 | |
| 2011-08-11 | Bring run-pass/task-killjoin up to date and un-XFAIL | Brian Anderson | -12/+11 | |
| 2011-08-03 | Remove all xfail-stage0 directives | Brian Anderson | -1/+0 | |
| While it is still technically possible to test stage 0, it is not part of any of the main testing rules and maintaining xfail-stage0 is a chore. Nobody should worry about how tests fare in stage0. | ||||
| 2011-07-27 | Fix damage done by the pretty-printer | Marijn Haverbeke | -6/+41 | |
| 2011-07-27 | Reformat for new syntax | Marijn Haverbeke | -41/+6 | |
| 2011-07-22 | Add xfail-stage3 directives to tests | Brian Anderson | -0/+2 | |
| The new test runners run stage 3 | ||||
| 2011-06-15 | Fix a bunch of compile-command lines to use RBUILD | Graydon Hoare | -1/+1 | |
| 2011-05-03 | Assume xfail-stage0 implies stage1 and stage2 in tests, for now. | Graydon Hoare | -0/+2 | |
| 2011-03-25 | Switch xfail system to use comments embedded in source files. | Graydon Hoare | -0/+1 | |
| 2011-01-03 | Don't attempt to wake tasks that aren't blocked. | Brian Anderson | -0/+36 | |
| It's possible for a supervised task to kill and wake its supervising task then immediately try to wake it again if the supervising task has joined the supervised. This is the easiest way to prevent that. | ||||
