lumpy-incremental-paladin failed when it should have passed |
|||||||
Issue descriptionhttps://uberchromegw.corp.google.com/i/chromeos/builders/lumpy-incremental-paladin/builds/11912 The build failed in BuildPackages (pre-patch) but then succeeded in post-patch. The expected behavior for the incremental builder in such a case is that the slave is marked as PASSED. But this one failed.
,
Apr 21 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/chromite/+/35becf8e74912023147ee3ec60c4072e291da77e commit 35becf8e74912023147ee3ec60c4072e291da77e Author: Aviv Keshet <akeshet@chromium.org> Date: Fri Apr 21 20:11:51 2017 chromeos_config: temporarily mark lumpy-incremental-paladin unimportant BUG=chromium:714226 TEST=None Change-Id: I8eb1cd32826ed9053d7a0a1da6015e571ca558a7 Reviewed-on: https://chromium-review.googlesource.com/484743 Reviewed-by: Aviv Keshet <akeshet@chromium.org> Tested-by: Aviv Keshet <akeshet@chromium.org> [modify] https://crrev.com/35becf8e74912023147ee3ec60c4072e291da77e/cbuildbot/config_dump.json [modify] https://crrev.com/35becf8e74912023147ee3ec60c4072e291da77e/cbuildbot/chromeos_config.py
,
Apr 21 2017
,
Apr 25 2017
@nxia / dgarrett - are we ready to move this back to "important" ?
,
Apr 25 2017
I don't think we've addressed the problem, so probably no.
,
May 16 2017
Is there another bug tracking the fix that I should dupe this to? Who's owning next steps?
,
May 16 2017
I looked into the code history before, I think the bug has been there for a long time. Not a small fix, assign it to me now.
,
May 23 2017
,
Mar 30 2018
,
Mar 30 2018
,
May 31 2018
|
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by akes...@chromium.org
, Apr 21 2017