It will be reactivated someday.  Don't make me regret burning --timeout for the global timeout.

I think fastest has only timeout for per-test.  My reasoning was, if each test completes, there's no way to predict how long a suite might take (due to parallelism, load, choice of a mix of tests).  Though a user might say, I'm willing to wait "10 minutes" so just fail back if it takes longer, because I'll be back from Starbucks by then.  (Respectively, the rest room, xerox machine for a fresh resume, water cooler.)

I noticed that @paulp 's Testicolor has a notion of "expected failures". In fastest, it's --tolerance.  That's a slightly different notion, but probably the same use case.

I went overboard with the command line because @paulp 's option processor is so much fun.

This is from last summer. I no longer remember the difference between --fork and --forking without thinking about it (and I don't plan on thinking about it).  The interesting one is --ticket, which merely matched test names, but was intended to run tests which declared themselves to test a ticket and also all the tests which ever failed while you were working on this ticket, as a heuristic against regression without running the entire suite.

```
$ fastest --help
Usage: partest [<options>] [<testfiles>]

  To control test output:
    --help         show this message
    --version      show version
    --debug        enable debug output
    --verbose      show progress
    --summary      summary results only
    --statistics   would you like some numbers with that?
    --silent       show nothing
    --show-log     show log output on error
    --show-diff    show diff between log and check file
    --colors       do it with style
    --gui          do it with swing

  To select libraries and sources for testing:
    --build        where to find lib/*.jar
    --classes      where to find classes
    --pack         selects --build=build/pack
    --quick        selects --classes=build/quick/classes
    --installed    selects --build=./lib
    --dist         selects --build=dists/latest/lib
    --latest       detect the latest from quick, pack, installed, dist
    --sourcepath   set path to test sources

  To select tests to run:
    --all          run all tests
    --failed       run previously failed tests
    --aggregate    compile tests in aggregate
    --pos          Testing compiler (on files whose compilation should succeed)
    --neg          Testing compiler (on files whose compilation should fail)
    --run          Testing interpreter and backend
    --jvm          Testing JVM backend
    --res          Testing resident compiler
    --fsc          Testing compile server (on files whose compilation should succeed)
    --buildmanager Testing Build Manager
    --shootout     Testing shootout tests
    --script       Testing script tests
    --scalacheck   Running ScalaCheck tests
    --scalap       Running scalap decompiler tests
    --specialized  Testing specialization
    --presentation Testing presentation compiler
    --instrumented Running instrumented tests
    --ant          Testing Ant task
    --grep         run all tests with any file containing <expr>
    --skip         skip tests selected by <expr>
    --ticket       run tests for ticket #<NNNN>

  Options for test in development:
    --list         list tests that would run (dry run)
    --limit        abort after limit failures
    --tolerance    succeed on up to tolerance failures
    --ignore       ignore missing or bad tests
    --timeout      timeout to fail a test, as a duration (default: 10 minutes)
    --cleaning     on success, delete artifacts from previous failure
    --update       on failure, update check files

  To select how to run the compilers and tests:
    --fork         fork compilation processes
    --forking      fork [scalac, javac, tests]
    --reuse        reuse compiler instances
    --disk         compiler inputs and outputs on disk
    --cachecp      reduce io on class path access
    --par          parallelism

```