New issue
Advanced search Search tips

Issue 922301 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug
Build-Toolchain



Sign in to add a comment

look for a better place to fail when AFDO profiles have not been updated.

Project Member Reported by llozano@chromium.org, Jan 16

Issue description

Currently, we are breaking the PFQ if the profiles for PFQ have not been updated after certain period.

It has been argued that, while it is good that it is failing, not getting updated profiles should not break the PFQ since recent profiles are not required for correctness. 
Should we move this to somewhere where the failure does not break any of official builders? 
should we be more flexible with profiles that are used for dev releases and more strict for the beta and stable channels?


 

Sign in to add a comment