Testing/development utilities

[alexpatel]

There are three parts of the patch:

• Full testlist of what tests pass/fail on QEMU/X86_64 with 2 cores
• A new script in tools/harness that will build a kernel and automagically run all the tests from a testlist against it. All the outputs/console output from each test is put in results/ (see tools/harness/scalebench.py).
• A Dockerfile for building an image with Barrelfish QEMU/x86_64 installed on it that will execute the testlist script when run. The point of this Dockerfile is: if you're hacking and want to build/test, instead of ssh'ing into nomnomnom or your VM (or even building locally) you can just do docker build . -t bf && docker run bf and hake, make, and the testlist is run in a replicable container environment.

The details about how to use these utilities are added to tools/harness/README

For issue https://github.com/Harvard-PRINCESS/Guppy/issues/43

[alexpatel]

I have also added a configuration file that integrates Barrelfish building/testing with the Circle CI continuous integration SaaS.

For any commit that gets pushed to Github on any branch, Circle CI will create a Docker container that hakes/makes/runs a bunch of tests on QEMU/x86_64. If any step in that pipeline fails, Circle CI will report the failure over e-mail (to the branch author) and prevent any PR merges on Github for that branch.

@mwookawa, the way to set up Circle CI is to sign up for Circle CI with your Github account. Circle CI will then pull a list of your public repositories; just check Guppy and then it's all set up. If you then commit to the ahp_testing branch and push to Github then the build will show up on the Circle CI Guppy dashboard.

Note: for the on-premise hardware + Pandaboards, we can spin-up a Flask server on nomnomnom that will get triggered by Circle CI to build/run and then report the tests back.