SoM: label wolf-tot-paladin builds as sanity |
||||
Issue descriptionSoM should indicate when any wolf-tot-paladin failures occur that they are a sanity build and are just building against ToT. This indicates that issues in the build are not from any changes in the CQ run but instead either infra, or ToT code (that has gotten through the CQ or been chumped). Include a yaqs link or descriptive text as apppropriate. akeshet: Is *-tot-paladin a reasonable regexp to use to label as sanity?
,
Sep 22 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/chromite/+/a5a27d6ef59b745857651e9880349456f5fa5f35 commit a5a27d6ef59b745857651e9880349456f5fa5f35 Author: David Riley <davidriley@chromium.org> Date: Fri Sep 22 02:38:29 2017 som_alerts_dispatcher: add yaqs entry for sanity builds. BUG= chromium:723055 TEST=som_alerts_dispatcher.py --som_host sheriff-o-matic-staging.appspot.com --som_tree chromeos ~cros/.cache/cidb_creds 1857329,1000 Change-Id: I400c23a86fe36f90e6278fbc9e1ea512f560de2c Reviewed-on: https://chromium-review.googlesource.com/677061 Commit-Ready: David Riley <davidriley@chromium.org> Tested-by: David Riley <davidriley@chromium.org> Reviewed-by: Don Garrett <dgarrett@chromium.org> [modify] https://crrev.com/a5a27d6ef59b745857651e9880349456f5fa5f35/scripts/som_alerts_dispatcher.py
,
Sep 25 2017
,
Jan 22 2018
,
Jan 23 2018
|
||||
►
Sign in to add a comment |
||||
Comment 1 by akes...@chromium.org
, Sep 18 2017