Stack benchmark output is not visible in terminal

[wdanilo]

Hello!
I've configured benchmarks in my cabal config and when I'm running stack bench, stacks builds all necessary components (including the ones needed by benchmarks) and the last line of the build process is <pkg name>: benchmarks.

I can see benchmarks output among logs and if some benchmarks fail I can see it in the terminal too. But if everything succeeds, the logs are just hidden in the cmd. Is there a way to reveal them?

[mgsloan]

If you run a single benchmark, do you get its output? It's using the same logic that's used to determine if a build log is outputted - if it's a target and the last thing executing, IIRC. I agree that this should be improved - see this issue: #426

stack bench is a bit of a rougher part of stack. I've just realized we should probably execute them sequentially: #1913

This means that they wouldn't run in parallel with other tasks, and so it's reasonable to send their output directly to the user.

[rrnewton]

So it sounds like once #1913 is fixed, this will automatically be fixed as a consequence of the existing print-serial-output policy?

[mgsloan]

Yes, hopefully so. It may require some tweaks to that logic, though, remains to be seen. Good thing to consider when working on #1913!

[mgsloan]

Actually, I was simply wrong about #1913. So, we are actually executing tests and benchmarks sequentially. In that case, it makes sense to me to output it to the terminal by default.