For a quick and dirty benchmark I thought I might be able to just a unittest main called from via a class deriving from BenchmarkBase in benchmark_harness via a command line main().
The unittests expects are written synchronously - but the the benchmark reports complete to the console first, then all the deluge of PASS: things go out to the console.
I realise this is not the best way of writing a benchmark - it was just an unsuccessful experiment. I would like to know why I am seeing the benchmark report come back before the the test PASS lines to the console though.