summaryrefslogtreecommitdiff
path: root/testsuite/tests/parser/should_compile/T15323.stderr
diff options
context:
space:
mode:
authorBen Gamari <ben@smart-cactus.org>2020-06-13 04:56:27 -0400
committerBen Gamari <ben@smart-cactus.org>2020-06-13 04:59:06 -0400
commit8bba1c26193e704d2d6bb2be9a2fac668b0ea54c (patch)
tree724acd8446d2bf9b4164e72ba8bf8f0ee0c7214c /testsuite/tests/parser/should_compile/T15323.stderr
parent220c2d34a34727d696cc4b44a1b87aba83231ce4 (diff)
downloadhaskell-8bba1c26193e704d2d6bb2be9a2fac668b0ea54c.tar.gz
gitlab-ci: Always push perf notes
Previously we ci.sh would run with `set -e` implying that we wouldn't push perf notes if the testsuite were to fail, even if it *only* failed due to perf notes. This rendered the whole performance testing story quite fragile as a single regressing commit would cause every successive commit to fail since a new baseline would not be uploaded. Fix this by ensuring that we always push performance notes.
Diffstat (limited to 'testsuite/tests/parser/should_compile/T15323.stderr')
0 files changed, 0 insertions, 0 deletions