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

Issue 761796 link

Starred by 1 user
Status: Fixed
Owner:
█ odeedee@google.com
Email to this user bounced
Closed: Sep 2017
Cc:
machenb...@chromium.org
hablich@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug


Participants' hotlists:
Cr8er


Sign in to add a comment

Clusterfuzz link should be shown even if the commit is not yet released to a Chrome build

Project Member Reported by hablich@chromium.org, Sep 4 2017 
It seems all of the stability information is dependent on the release of the commit via Chrome. For Chromecrash that is the case, for Clusterfuzz it is not. The Clusterfuzz link is valid at the time of the commit landing.

Please show the Clusterfuzz link right away.
XixtkZWad82.png
187 KB View Download

Comment 1 by odeedee@google.com, Sep 4 2017

Owner: odeedee@google.com
Status: Started (was: Unassigned)
Project Member

Comment 3 by bugdroid1@chromium.org, Sep 4 2017 

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/infra/infra_internal/+/0ad78d1f70b512215f883090eb542a4aff32393d

commit 0ad78d1f70b512215f883090eb542a4aff32393d
Author: odeedee <odeedee@google.com>
Date: Mon Sep 04 15:36:56 2017

Comment 4 by odeedee@google.com, Sep 5 2017

Status: Fixed (was: Started)
►

Sign in to add a comment