Issue metadata
Sign in to add a comment
|
afdoupdateebuild is breaking chrome pfq |
||||||||||||||||||||||
Issue descriptionhttps://uberchromegw.corp.google.com/i/chromeos/builders/master-chromium-pfq/builds/6153 22:13:18: INFO: Found latest AFDO info file gs://chromeos-prebuilt/afdo-job/llvm/latest-chromeos-chrome-amd64-67.afdo but it is too old [1;31m22:13:18: ERROR: Could not find appropriate AFDO profile[0m 22:13:18: INFO: Translating result Could not find appropriate AFDO profile to fail. Root cause is AFDODataGenerate in chell-chrome-pfq is broken as create_llvm_prof cannot parse new perf events. https://uberchromegw.corp.google.com/i/chromeos/builders/chell-chrome-pfq/builds/2301 RunCommandError: return code: 250; command: cros_sdk -- /usr/bin/create_llvm_prof '--binary=/tmp/chrome.unstripped' '--profile=/tmp/chromeos-chrome-amd64-67.0.3390.0.perf.data' '--out=/tmp/chromeos-chrome-amd64-67.0.3390.0_rc-r1.afdo' E0406 20:05:55.187001 10 perf_reader.cc:996] Unsupported event type 79 F0406 20:05:55.187199 10 perf_parser.cc:240] Check failed: reader_.ReadPerfSampleInfo(*parsed_event.raw_event, &sample_info)
,
Apr 7 2018
there is already a fix for this from lakshmana@. The next PFQ run should fix the issue.
,
Apr 7 2018
There might also be some problem in email notifications: WARNING: Could not send e-mail from cros-beefy343-c2.c.chromeos-bot.internal to chromeos-toolchain-sheriff@grotations.appspotmail.com via 'mail.golo.chromium.org': [Errno -2] Name or service not known
,
Apr 8 2018
https://uberchromegw.corp.google.com/i/chromeos/builders/master-chromium-pfq/builds/6155 is green. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by manojgupta@chromium.org
, Apr 7 2018