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

Issue 810981 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Jul 27
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug
Build-Toolchain



Sign in to add a comment

AFDO staleness check in branches is incorrect.

Project Member Reported by laszio@chromium.org, Feb 10 2018

Issue description

The staleness check is basically: If the latest profile is more than 14 days old AND 7 builds away, then fail.

For example, if latest profile is generated with chrome RXX-1000.0.0 and current chrome version is 1006.0.0, it is considered OK.

This only works on master but not branches. Branches has chrome versions look like RXX-1000.100.0, which can be much older than RXX-1000.200.0. Their build distance is 0 according to current implementation.
 
Status: WontFix (was: Untriaged)
This only applies to benchmark profiles, which are no longer used.

Sign in to add a comment