New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 798748 link

Starred by 1 user
Status: Fixed
Owner:
█ pho...@chromium.org
Last visit > 30 days ago
Closed: Feb 2018
Cc:
akes...@chromium.org
xixuan@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Feature
okr



Sign in to add a comment

Provide CL-Scanner report in build's reportstage.

Project Member Reported by pho...@chromium.org, Jan 3 2018 
Add a build message text to the ReportStage that indicates which, if any, CLs are risky according to the scanner.

Comment 1 by pho...@chromium.org, Jan 4 2018

Cc: akes...@chromium.org xixuan@chromium.org
Status: Assigned (was: Untriaged)

Comment 2 by pho...@chromium.org, Jan 17 2018 

Suggestions on team chat:

+ Add links to risky CLs found
+ Provide full risk report in ReportStage log.

Comment 3 by pho...@chromium.org, Feb 7 2018

Status: Fixed (was: Assigned)
Project Member

Comment 4 by bugdroid1@chromium.org, Mar 28 2018 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/infra/bad_cl_detector/+/9c045e959b6fed88662167c01ad4fe4945377340

commit 9c045e959b6fed88662167c01ad4fe4945377340
Author: Paul Hobbs <phobbs@google.com>
Date: Wed Jan 17 22:47:15 2018

Fix for nonexistant CLs.

BUG= chromium:798748 
TEST=Local server

Change-Id: Ic02d6381f00c8ba33080904519049b0be4c12f93

[modify] https://crrev.com/9c045e959b6fed88662167c01ad4fe4945377340/lib/fetch_data_engine.py
►

Sign in to add a comment