Skip to content


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Commits on Aug 7, 2013
  1. Brian Anderson
Commits on Oct 4, 2012
  1. Brian Anderson
Commits on Sep 12, 2012
  1. Brian Anderson
Commits on Aug 2, 2012
  1. Brian Anderson

    Convert ret to return

    brson authored
Commits on Aug 1, 2012
  1. Brian Anderson

    Fix failing tests

    brson authored
Commits on May 24, 2012
  1. Brian Anderson

    bench: Add hard mode to benchmarks. Activate with RUST_BENCH.

    brson authored
    RUST_BENCH is on automatically when running `make perf`
Commits on Jan 15, 2012
  1. Brian Anderson

    bench: Lower the default inputs on many shootout benchmarks

    brson authored
    Make them run a bit faster during normal testing
  2. Brian Anderson
Commits on Nov 10, 2011
  1. Brian Anderson
Commits on Sep 20, 2011
  1. Brian Anderson

    Un-xfail various tests

    brson authored
Commits on Sep 12, 2011
  1. Brian Anderson

    Merge branch 'unwind'

    brson authored
  2. Brian Anderson

    XFAIL bench/shootout-nbody

    brson authored
    This is the only file in the whole codebase that depends on the (broken) llvm
    native ABI.
Commits on Aug 20, 2011
  1. Brian Anderson


    brson authored
    This changes the indexing syntax from .() to [], the vector syntax from ~[] to
    [] and the extension syntax from #fmt() to #fmt[]
Commits on Aug 12, 2011
  1. Brian Anderson

    Convert most working tests to ivecs

    brson authored
    I tried to pay attention to what was actually being tested so, e.g. when I
    test was just using a vec as a boxed thing, I converted to boxed ints, etc.
    Haven't converted the macro tests yet. Not sure what to do there.
Commits on Aug 3, 2011
  1. Brian Anderson
Commits on Aug 2, 2011
  1. Brian Anderson
Commits on Jul 24, 2011
  1. Brian Anderson

    The Big Test Suite Overhaul

    brson authored
    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
    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 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.
Something went wrong with that request. Please try again.