Quarantine bad commits and implement a mechanism for manual inspection |
|
Issue descriptionIt is possible that some bad commmits generate unreasonable coverage number, there should be a mechanism to automatically quarantine bad commits and a process of manual inspection to understand what exactly happened.
,
Today
(7 hours ago)
The following revision refers to this bug: https://chromium.googlesource.com/infra/infra/+/61634f7035bed76c1bd0fc502714c8880b00e721 commit 61634f7035bed76c1bd0fc502714c8880b00e721 Author: Yuke Liao <liaoyuke@chromium.org> Date: Tue Jan 22 23:26:26 2019 [code coverage] Hide suspicious full-repo coverage reports This CL hides suspicious full-repo coverage reports from users while make them visible to admins for investigations. Bug: 918899 Change-Id: I69819679497d902cf19b83fb471efbc755448a5c Reviewed-on: https://chromium-review.googlesource.com/c/1426074 Commit-Queue: Yuke Liao <liaoyuke@chromium.org> Reviewed-by: Roberto Carrillo <robertocn@chromium.org> Cr-Commit-Position: refs/heads/master@{#20124} [modify] https://crrev.com/61634f7035bed76c1bd0fc502714c8880b00e721/appengine/findit/templates/coverage/codebase_view.html [modify] https://crrev.com/61634f7035bed76c1bd0fc502714c8880b00e721/appengine/findit/handlers/code_coverage.py |
|
►
Sign in to add a comment |
|
Comment 1 by liaoyuke@chromium.org
, Jan 3