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

Issue 747089 link

Starred by 0 users
Status: Available
Owner: ----
Cc:
█ robert...@chromium.org
chanli@chromium.org
lijeffrey@chromium.org
liaoyuke@chromium.org
st...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: ----



Sign in to add a comment

flake detector should pull current milestone and automatically created bugs with it

Project Member Reported by serg...@chromium.org, Jul 20 2017 
Milestones are represented via M-<X> labels on each bug (i.e. the same kind of tagging as the Priority, in crbug).  When a bug is P-1 (Need) or P-2 (Want), it needs a Milestone label so we know _when_ we Need/Want it.

We should be able to grab the MAJOR version number from src/chrome/VERSION and use that to tag the bug. The main benefit in setting the milestone is that if folks are looking at their bugs for the "current" milestone, or ordered by milestone, these will be visible - otherwise they won't be, or will at least be mis-represented as lower priority.

Comment 1 by serg...@chromium.org, Jul 20 2017 

Open question: should we update milestone tags on each update or is there some bot that will update bugs automatically?
Project Member

Comment 2 by sheriffbot@chromium.org, Jul 23

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 3 by st...@chromium.org, Aug 6

Owner: liaoyuke@chromium.org
Status: Assigned (was: Untriaged)
Not sure whether we want to move on with this bug in the new flake detection

Comment 4 by liaoyuke@chromium.org, Jan 8

Components: -Infra>Flakiness>Pipeline Tools>Test>FindIt>Flakiness
Owner: ----
Status: Available (was: Assigned)
Summary: flake detector should pull current milestone and automatically created bugs with it (was: chromium-try-flakes should pull current milestone and automatically created bugs with it)
try-flakes is deprecated. I don't see any feature request for this, leaving to Chan to further triage if it's worth doing this in flake detector.

Comment 5 by chanli@chromium.org, Jan 8 

I can see benefit of this feature, especially if we want to make developers pay more attention on fixing flakes. I may mention this with some stakeholders to collect their feedback.
►

Sign in to add a comment