Last successfull AFDO run was on Nov 18 so new afdo data is available.
https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?buildbucketId=8929470001275483008

However, the uprev can happen only when master-chromium-pfq will succeed.

btw, afdo job now runs on chell-chrome-pfq

I followed link from https://sites.google.com/a/google.com/chromeos-toolchain-team-home2/home/afdo-profile-guided-optimizations

this doc refers to lumpy:
https://docs.google.com/document/d/1vyrZKCUhoqOGcbC7DRWeDY3J7IdXOw38aTdVhm0Xbnk/edit#heading=h.voq84r47sfey

The AFDO profiles are now being generated by the chell pfq, not lumpy (which as you have noted is not there any more).  The document you are referring to is slightly out of date and needs to be updated.

I believe the afdo files uprevved with the successful master chromimum pfq build on Nov. 20.

uekawa@, just curious, what are you trying to do?

we're using afdo update as a signal for tracking chrome uprev because that was a convenient proxy (at the time) to monitor. So our constables (go/arc++constable) are alerted by this, probably not ideal.

b/119662546

yes, that is probably not a good signal.
afdo update may fail for various reasons not related to the chrome uprev.