yes, we need to apply that workaround.. 
Assigning to Ting-Yuan.
Ting-Yuan and I will discuss on a better way to handle this so that we can avoid having to do this for some branches.

This happens because there is no builder generating the profile. In R58, it is only used for 4 boards so we decided not to set up a dedicated builder. The solution discussed was to generate it manually. However, we forgot the staleness requirement so you saw the failure :(

I've triggered a build to generate the profile and that will keep samus-pre-flight-branch happy in the next two weeks. Let me write this to crontab to generate it daily.

Per discussed with Luis, I've created a CL to make AFDO profiles never expire on R58:

https://chromium-review.googlesource.com/c/492488/

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/chromite/+/0bc938a54e8b319ca4d0a66fbced74f273e61dd8

commit 0bc938a54e8b319ca4d0a66fbced74f273e61dd8
Author: Ting-Yuan Huang <laszio@chromium.org>
Date: Mon May 01 23:53:17 2017

AutoFDO: extend the expiration days to 8 weeks.

This basically make it never expire, assuming R58 will roughly live for
6 weeks.

TEST=none
BUG= chromium:717069 

Change-Id: I009e4e83e03f782e6515bddd90733c9db10ac68b
Reviewed-on: https://chromium-review.googlesource.com/492488
Reviewed-by: Bernie Thompson <bhthompson@chromium.org>
Commit-Queue: Ting-Yuan Huang <laszio@chromium.org>
Tested-by: Ting-Yuan Huang <laszio@chromium.org>
Trybot-Ready: Ting-Yuan Huang <laszio@chromium.org>

[modify] https://crrev.com/0bc938a54e8b319ca4d0a66fbced74f273e61dd8/cbuildbot/afdo.py