anchor.diff:  There are several command line flags that can be specified to customize how `test161` runs tests.
   
   * `-dry-run` (`-r`): Show the tests that would be run, but don't run them.
  +* `-explain` (`-x`): Show test detail, such as name, descriptions, `sys161 configuration`, commands, and expected output.
   * `-sequential` (`-s`): By default the output of all tests are interleaved, which can be hard to debug.
   Specify this option to run tests one at a time.
   * `-no-dependencies` (`-n`): Run the given tests without also running their dependencies. In test files, you can specify a
  
positive.code: conf:
    cpus: 8
    ram: 1M
    disk1:
      sectors: min(2 * ram, 8000) # 8000 is a minimum due to a current sys161 bug
      rpm: 7200
      nodoom: true
  
negative.code: 
  == Configuration
  
  Out of the box, `test161` can't do much without a set of <<tests>>, <<targets>>,
  and <<commands>>, as well as an OS/161 `root` directory which contains your
  kernel. If you are starting from the https://github.com/ops-class/os161[ops-class OS/161 sources],
  as soon as you configure, compile, and install your userland binaries and kernel, `test161`
  will work in either your root or source trees.
  
  === Submission
  
  In order to submit to the https://test161.ops-class.org[test161 server], you
  need to configure your username/token, which can be done with:
  
  [source,bash]
  ----
  test161 config add-user <username> <token>
  ----
  
  Removing users and changing configured tokens can be done with:
  
  [source,bash]
  ----
  test161 config del-user <username>              // Delete user information
  test161 config change-token <username> <token>  // Change token
  ----
  
  === Custom Configuration
  
  The ops-class sources create symlinks between your OS/161 source directory and
  root directory, which may not always be what you want. To support partial
  environments where either source or root cannot be inferred from the other,
  you can use `test161 config` to set the directory containing tests, targets,
  and commands:
  
  [source,bash]
  ----
  test161 config test161dir <path>
  ----
  
  This allows you to run `test161 run ...` from your root directory.
  
  ==== Secure Overlay
  
  The `test161` server uses an overlay directory, containing an overlay for each
  assignment, which it rsyncs over student submissions before compiling. The
  overlay contains files that we don't trust from students, e.g. make files, anything
  that prints SUCCESS. To enable an overlay for local testing, set the
  `TEST161_OVERLAY` environment variable to the overlay path.
  
  ==== Local Server
  
  Set the TEST161_SERVER environment variable for testing submissions with a local
  server.
  
  ==== Printing Configuration
  
  To view the current test161 configuration, simply run `test161 config`.
  
  == Usage
  
  