How partest chooses the compiler / library:

  * ''-Dpartest.build=build/four-pack'' -> will search for libraries in
    ''lib'' directory of given path
  * ''--pack'' -> will set ''partest.build=build/pack'', and run all tests.
    add ''--[kind]'' to run a selected set of tests.
  * auto detection:
    - partest.build property -> ''bin'' / ''lib'' directories
    - distribution (''dists/latest'')
    - supersabbus pack (''build/pack'')
    - sabbus quick (''build/quick'')
    - installed dist (test files in ''misc/scala-test/files'')

How partest choses test files: the test files must be accessible from
the directory on which partest is run. So the test files must be either
at:
  * ./test/files
  * ./files (cwd is "test")
  * ./misc/scala-test/files (installed scala distribution)

Other arguments:
  * --pos          next files test a compilation success
  * --neg          next files test a compilation failure
  * --run          next files test the interpreter and all backends
  * --jvm          next files test the JVM backend
  * --res          next files test the resident compiler
  * --buildmanager next files test the build manager
  * --shootout     next files are shootout tests
  * --script       next files test the script runner
  * ''-Dpartest.scalac_opts=...'' -> add compiler options
  * ''--verbose'' -> print verbose messages
  * ''-Dpartest.debug=true'' -> print debug messages