add count of non-CL-related maladin runs that failed, to CQ summary script |
|||||
Issue descriptionPer comment in https://docs.google.com/document/d/1KnpYx5wUxfrrfAnbsSncTVGts1khTCGZ_QyPRWMvNRs/edit This should be a small follow up to the work you've already done. Basically, we want a count of how many runs failed that were not blamed on any bad CL.
,
Dec 6 2016
From the summary script stdout: 11:15:48: INFO: Reasons why builds failed: 11:15:48: INFO: 7 failures in bad_cl 11:15:48: INFO: 2 failures in test_flake 11:15:48: INFO: 2 failures in lab_failure 11:15:48: INFO: 1 failures in infra_failure 11:15:48: INFO: 1 failures in gerrit_failure I plan on outputting the sum of all but the bad_cl.
,
Dec 6 2016
Here is the added output to the summary report: The pre-CQ <b>rejected 8 changes this week</b>, which would otherwise have broken a CQ run and affected other developers.
,
May 23 2017
,
May 24 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/chromite/+/bfd84917031d7881ebb08fa822fb3a02e91fa5d6 commit bfd84917031d7881ebb08fa822fb3a02e91fa5d6 Author: Chris Ching <chingcodes@chromium.org> Date: Wed May 24 17:27:02 2017 summarize_build_stats: fill in patch fail reasons table The "Top reasons that good changes where rejected" table is now filled in Fixed small formatting errors BUG= chromium:665620 TEST=ran script to generate this week's report Change-Id: Ic05388b7e1dd6c2e41ec433e9733895881270feb Reviewed-on: https://chromium-review.googlesource.com/512605 Commit-Ready: Chris Ching <chingcodes@chromium.org> Tested-by: Chris Ching <chingcodes@chromium.org> Reviewed-by: Chris Ching <chingcodes@chromium.org> [modify] https://crrev.com/bfd84917031d7881ebb08fa822fb3a02e91fa5d6/scripts/summarize_build_stats.py
,
Aug 1 2017
,
Jan 22 2018
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by autumn@chromium.org
, Nov 15 2016