Marking lakitu-full unimportant until it no longer consistently fails |
||
Issue descriptionThis is a tracking issue for the importance of the lakitu-full builder. The lakitu-full builder hasn't had a successful build since 2018-12-02 and appears to be languishing due to lack of attention. If the build being red for over a month hasn't been a problem, it shouldn't cause master-full to be red. As of 2019-01-07, the lakitu-full builder is failing in VMTests for unknown reasons and in the Report stage due to bad credentials as in issue 900740.
,
Jan 7
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/chromite/+/45a2fcf1fc36ba611a5665ca011b1712a1564ffa commit 45a2fcf1fc36ba611a5665ca011b1712a1564ffa Author: Chris McDonald <cjmcdonald@chromium.org> Date: Mon Jan 07 22:59:36 2019 chromeos_config: Mark kevin64-full and lakitu-full as unimportant These builders failing for a month hasn't been a problem, so they shouldn't be important enough to mark master-full as failng. BUG=chromium:919630, chromium:878565 TEST=None Change-Id: Ie982efffa5d1696b7e5e55e00665065bfc0c94dd Reviewed-on: https://chromium-review.googlesource.com/1399461 Commit-Ready: Chris McDonald <cjmcdonald@chromium.org> Tested-by: Chris McDonald <cjmcdonald@chromium.org> Reviewed-by: Manoj Gupta <manojgupta@chromium.org> Reviewed-by: Mike Nichols <mikenichols@chromium.org> [modify] https://crrev.com/45a2fcf1fc36ba611a5665ca011b1712a1564ffa/config/chromeos_config.py [modify] https://crrev.com/45a2fcf1fc36ba611a5665ca011b1712a1564ffa/config/config_dump.json
,
Jan 11
|
||
►
Sign in to add a comment |
||
Comment 1 by mikenichols@google.com
, Jan 7