apk_size_regressions.md: Binary size sheriffs no longer need to worry about broken bot

The bot is now the same as is used by other perf tests, so if it is
broken, it will not go unnoticed / will be covered by tree sheriffs.


Change-Id: If63c11f92c43d0ecc45953b63301d95a31510f7b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1676346
Auto-Submit: Andrew Grieve <agrieve@chromium.org>
Reviewed-by: Eric Stevenson <estevenson@chromium.org>
Commit-Queue: Eric Stevenson <estevenson@chromium.org>
Cr-Commit-Position: refs/heads/master@{#672089}

docs/speed/apk_size_regressions.md

@@ -184,16 +184,6 @@ Close the bug as "Won't Fix".
 
 ## Step 2: Check Alerts Regularly
 
- * **IMPORTANT: Check the [perf bot page](https://ci.chromium.org/buildbot/chromium.perf/Android%20Builder%20Perf/)
- several times a day to make sure it isn't broken (and ping/file a bug if it is).**
-   * At the very least you need to check this once in the morning and once in
-   the afternoon.
-   * If you don't and the builder is broken either you or the next sheriff will
-   have to manually build and diff the broken range (via. `diagnose_bloat.py`)
-   to see if we missed any regressions.
-   * This is necessary even if the next passing build doesn't create an alert
-   because the range could contain a large regression with multiple offsetting
-   decreases.
  * Check [alert page](https://chromeperf.appspot.com/alerts?sheriff=Binary%20Size%20Sheriff) regularly for new alerts.
  * Join [g/chrome-binary-size-alerts](https://goto.google.com/chrome-binary-size-alerts).
  * Deal with alerts as outlined above.
\ No newline at end of file