Change toolstate to no longer fail on nightly

Previously, toolstate would always error the build if the tool regressed
(or didn't improve to test-pass). This isn't great for rollups, in
particular, as it means we basically can't viably rollup tool updates.

In most cases, when trying to land a submodule (tool) change, you mostly
want to just bump the sub-commit, and don't care too much if that
actually fully fixes the tool.

Author: Mark-Simulacrum

src/ci/docker/x86_64-gnu-tools/checktools.sh

@@ -56,7 +56,11 @@ verify_submodule_changed() {
             echo "If you do NOT intend to update '$1', please ensure you did not accidentally"
             echo "change the submodule at '$2'. You may ask your reviewer for the"
             echo "proper steps."
-            exit 3
+            # exit if we're in beta week, otherwise we don't want to,
+            # it's fine to land changes/regressions to toolstate
+            if [ $SIX_WEEK_CYCLE -ge 35 ]; then
+                exit 3
+            fi
         fi
     fi
 }
@@ -105,21 +109,11 @@ status_check() {
 
 status_check "submodule_changed"
 
-CHECK_NOT="$(readlink -f "$(dirname $0)/checkregression.py")"
 # This callback is called by `commit_toolstate_change`, see `repo.sh`.
 change_toolstate() {
-    # only update the history
-    if python2.7 "$CHECK_NOT" "$OS" "$TOOLSTATE_FILE" "_data/latest.json" changed; then
-        echo 'Toolstate is not changed. Not updating.'
-    else
-        if [ $SIX_WEEK_CYCLE -ge 35 ]; then
-            # Reject any regressions during the week before beta cutoff.
-            python2.7 "$CHECK_NOT" "$OS" "$TOOLSTATE_FILE" "_data/latest.json" regressed
-        fi
-        sed -i "1 a\\
+    sed -i "1 a\\
 $COMMIT\t$(cat "$TOOLSTATE_FILE")
 " "history/$OS.tsv"
-    fi
 }
 
 if [ "$RUST_RELEASE_CHANNEL" = nightly ]; then