Benchmarks are executed in parallel with other tasks

[mgsloan]

This probably isn't what we want, as it can affect benchmark results!

[rrnewton]

Yes, this makes the benchmark results by default corrupt!

[mgsloan]

Agreed, bumping to P1

[mgsloan]

Hah, upon looking into this I found that the logic is already there to run tests and benchmarks sequentially:

stack/src/Control/Concurrent/Execute.hs

Line 111 in d63395e

(ActionId _ ATFinal, Just lock) -> do

My mistake