Make kip-paladin not experimental
Reported by
jrbarnette@chromium.org,
Jun 5 2017
|
||
Issue descriptionkip-paladin is still experimental, purportedly because of bug 696679 . However, I see no evidence of that bug still occurring. I _do_ see evidence of kip-paladin finding bugs that should be rejected by the CQ. We need to make kip-paladin not experimental again.
,
Jun 6 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/chromite/+/259242ed15e6bd33a3e7ac44f810f01db7c81a4a commit 259242ed15e6bd33a3e7ac44f810f01db7c81a4a Author: Ilja H. Friedel <ihf@chromium.org> Date: Tue Jun 06 06:49:38 2017 chromos_config: mark kip important. This could have prevented the baytrail graphics failure. BUG= chromium:727778 , chromium:729668 TEST=None. Change-Id: I337a5097c65ecdb3eab1bfa30188336d0c0e9c2d Reviewed-on: https://chromium-review.googlesource.com/524037 Commit-Ready: Ilja H. Friedel <ihf@chromium.org> Tested-by: Ilja H. Friedel <ihf@chromium.org> Reviewed-by: Ilja H. Friedel <ihf@chromium.org> [modify] https://crrev.com/259242ed15e6bd33a3e7ac44f810f01db7c81a4a/cbuildbot/config_dump.json [modify] https://crrev.com/259242ed15e6bd33a3e7ac44f810f01db7c81a4a/cbuildbot/chromeos_config.py
,
Jun 6 2017
|
||
►
Sign in to add a comment |
||
Comment 1 by jrbarnette@chromium.org
, Jun 5 2017