summary refs log tree commit diff
path: root/src/tools/publish_toolstate.py
diff options
context:
space:
mode:
authorMark Rousskov <mark.simulacrum@gmail.com>2020-02-20 19:46:09 -0500
committerMark Rousskov <mark.simulacrum@gmail.com>2020-02-20 19:46:09 -0500
commite7ee42baeb54f6484fa76a88e03b3168ff3147ce (patch)
tree2bb739033debf5fd05126fe7ba96765a0ec4bf1e /src/tools/publish_toolstate.py
parent6af388b25050bca26710be7e4030e17bf6d8d2f7 (diff)
downloadrust-e7ee42baeb54f6484fa76a88e03b3168ff3147ce.tar.gz
rust-e7ee42baeb54f6484fa76a88e03b3168ff3147ce.zip
Do not ping the infrastructure team on toolstate changes
To my knowledge, there is essentially never any particular action that the
infra team needs to take on these pings, and they are currently relatively
annoying.
Diffstat (limited to 'src/tools/publish_toolstate.py')
-rwxr-xr-xsrc/tools/publish_toolstate.py4
1 files changed, 2 insertions, 2 deletions
diff --git a/src/tools/publish_toolstate.py b/src/tools/publish_toolstate.py
index 967333c1ace..81d44a3df25 100755
--- a/src/tools/publish_toolstate.py
+++ b/src/tools/publish_toolstate.py
@@ -211,14 +211,14 @@ def update_latest(
                 if new > old:
                     # things got fixed or at least the status quo improved
                     changed = True
-                    message += '🎉 {} on {}: {} → {} (cc {}, @rust-lang/infra).\n' \
+                    message += '🎉 {} on {}: {} → {} (cc {}).\n' \
                         .format(tool, os, old, new, maintainers)
                 elif new < old:
                     # tests or builds are failing and were not failing before
                     changed = True
                     title = '💔 {} on {}: {} → {}' \
                         .format(tool, os, old, new)
-                    message += '{} (cc {}, @rust-lang/infra).\n' \
+                    message += '{} (cc {}).\n' \
                         .format(title, maintainers)
                     # See if we need to create an issue.
                     if tool == 'miri':