[enhancement] Need automation to run stress test as part of CI process

[Thomi Richards]

We need to run the mir stress test suite as part of the CI automation process. This requires the following:

 * A Jenkins job that take a source branch as a parameter. That job should provision an up-to-date saucy machine and:
  - Build the source branch packages
  - Install the mir-demos and mir-test-tools packages
  - From a VT, run mir_demo_server
  - run "mir_stress -n 60", and check the return code of the mir_stress program. If it exited with a RC of 0, the jenkins job should pass. If it exits with any other return code, or fails to exit after 60 seconds (maybe 80 seconds, to give it some grace time), the job should fail.
  - (optional) Sends Ctrl+C to the mir_demo_server.

Once that's in place we need to hook this job up to the mir CI stack, so we cannot land mir code that breaks the stress tests.

[Francis Ginther (fginther)]

Spoke to Thomi and his only machine request is the more threads the better. We have a couple of intel i5 boxes available for this, ps-radeon-hd6870-he and ps-nvidia-gs8400-le. Both are i5 with 4 cpu cores. The graphics chipset doesn't really matter for this testing.

[Alberto Aguirre (albaguirre)]

Something to consider for Jenkaas.

[Michał Sawicz (saviq)]

Syncing task from Mir.