Performance benchmarking CI step failure reflects as success

[countvajhula]

When the benchmarks step fails, it still returns a success error code, and the job only fails on the next step, obscuring the source of the problem, like in this example.

See this conversation for more context. Excerpts:

"the | used in this command obscures the error result of the first command in the pipeline. Should be able to fix this in the future: https://unix.stackexchange.com/questions/14270/get-exit-status-of-process-thats-piped-to-another"

"yea, I suspect set -o pipefail is what you want for that."

[countvajhula]

Considering this closed unless we discover otherwise.