Use post_process to test coverage recipes |
||
Issue descriptionA comment in https://chromium-review.googlesource.com/c/chromium/tools/build/+/1079206/1/scripts/slave/recipes/chromium_clang_coverage_reports.py mentioned that "Generating a test for every builder is liable to result in unusable noise. I've been trying to advocate for using post_process (https://codesearch.chromium.org/chromium/infra/recipes-py/recipe_engine/post_process.py) in new code to explicitly assert on what you care about & then drop the expectations."
,
Jun 12 2018
|
||
►
Sign in to add a comment |
||
Comment 1 by bugdroid1@chromium.org
, Jun 12 2018