aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Miek Gieben <miek@miek.nl> 2018-09-27 22:04:04 +0100
committerGravatar GitHub <noreply@github.com> 2018-09-27 22:04:04 +0100
commit2fc3f5e0b10ad4e79d952d2ac2bc8d4e7534f4e1 (patch)
treeef91d1515aee206eb96258177572b846d5bf20bb
parent1c95ede2acdf95babfa603818b8a20e3cebc12ad (diff)
downloadcoredns-2fc3f5e0b10ad4e79d952d2ac2bc8d4e7534f4e1.tar.gz
coredns-2fc3f5e0b10ad4e79d952d2ac2bc8d4e7534f4e1.tar.zst
coredns-2fc3f5e0b10ad4e79d952d2ac2bc8d4e7534f4e1.zip
benchmark are spammy (#2144)
This is indeed (as Chris said) too spammy; disable the ping back of the results for now - and rethink it a bit. See #2109 Signed-off-by: Miek Gieben <miek@miek.nl>
-rw-r--r--.benchmark.sh3
1 files changed, 3 insertions, 0 deletions
diff --git a/.benchmark.sh b/.benchmark.sh
index 2910dddc4..2fcceaf80 100644
--- a/.benchmark.sh
+++ b/.benchmark.sh
@@ -2,6 +2,9 @@
set -e +o pipefail
+# bit too spammy
+return
+
if [ "$TRAVIS_PULL_REQUEST" != "false" ] ; then
echo -e "NOTE: The CPU benchmarks are performed on Travis VMs and vary widly between runs," > .benchmark.body
echo -e " you can't trust them. The memory benchmarks are OK\n\n" >> .benchmark.body