Extract failed "target"s for compile step failures from build json data and pass over to try-job rerun |
||||
Issue descriptionAfter https://codereview.chromium.org/1766873002/, failed "target"s will be available as a build properties in the build json data. On Findit side, we need to extract the information from the build json data.
,
Mar 22 2016
,
Mar 22 2016
The CL for this is in https://codereview.chromium.org/1826633002/, but might need some tweaking after https://codereview.chromium.org/1766873002/ lands.
,
Apr 22 2016
,
May 1 2016
The following revision refers to this bug: https://chromium.googlesource.com/infra/infra.git/+/dd994dba70805597d2ce4af71fea0c7d690eb3bf commit dd994dba70805597d2ce4af71fea0c7d690eb3bf Author: stgao <stgao@chromium.org> Date: Sun May 01 05:17:47 2016 [Findit] Extract failed output nodes from stdio log of compile step. This is a temporary solution to start experiment and collect metrics as early as we could. BUG= 596970 TBR=chanli, lijeffrey Review-Url: https://codereview.chromium.org/1933013003 [modify] https://crrev.com/dd994dba70805597d2ce4af71fea0c7d690eb3bf/appengine/findit/waterfall/extractors.py [modify] https://crrev.com/dd994dba70805597d2ce4af71fea0c7d690eb3bf/appengine/findit/waterfall/failure_signal.py [modify] https://crrev.com/dd994dba70805597d2ce4af71fea0c7d690eb3bf/appengine/findit/waterfall/test/extractors_test.py [modify] https://crrev.com/dd994dba70805597d2ce4af71fea0c7d690eb3bf/appengine/findit/waterfall/test/failure_signal_test.py [modify] https://crrev.com/dd994dba70805597d2ce4af71fea0c7d690eb3bf/appengine/findit/waterfall/test/try_job_util_test.py [modify] https://crrev.com/dd994dba70805597d2ce4af71fea0c7d690eb3bf/appengine/findit/waterfall/try_job_util.py
,
Apr 25 2017
Mark as fixed because the recipe change to collect failed targets on the recipe side seems not preferred by nico. |
||||
►
Sign in to add a comment |
||||
Comment 1 by st...@chromium.org
, Mar 22 2016