"Nice" report for failed forks/benchmarks

[Vladimir Sitnikov]

> I'd think if benchmark fails, then the result should be marked as
failure as well. No recovery is possible.

If warmup fails, then no luck.

If at least single measurement iteration succeeds, then we might be
interested in some of the profiling results.
Overall benchmark might fail due to "OutOfMemory", however
"·gc.alloc.rate.norm" is still relevant.

What if we add secondary sample that tells user that particular
benchmark failed at iteration X?

For instance:

 Benchmark
(autoCloseStatements)  (leakPct)  Mode  Cnt       Score        Error
FinalizeStatement.createAndLeak
true          0  avgt    2   OutOfMemoryError at iteration 3
FinalizeStatement.createAndLeak:·gc.alloc.rate.norm
true          0  avgt    2     192,026

Vladimir