Chrome PFQ failing -- Wrong file version in settings_resources.pak |
|||
Issue descriptionAll Chrome PFQ are failing in BuildPackages. https://uberchromegw.corp.google.com/i/chromeos/builders/cyan-chrome-pfq/builds/1430 chromeos-chrome-61.0.3163.0_rc-r1: [124/28611] ACTION //chrome/browser/resources/settings:unpak(//build/toolchain/cros:target)[K chromeos-chrome-61.0.3163.0_rc-r1: FAILED: gen/chrome/browser/resources/settings/settings_resources.unpak chromeos-chrome-61.0.3163.0_rc-r1: python ../../../../../../../home/chrome-bot/chrome_root/src/chrome/browser/resources/unpack_pak.py --out_folder gen/chrome/browser/resources/settings/settings_resources.unpak --pak_file gen/chrome/browser/resources/settings/settings_resources.pak chromeos-chrome-61.0.3163.0_rc-r1: Wrong file version in gen/chrome/browser/resources/settings/settings_resources.pak chromeos-chrome-61.0.3163.0_rc-r1: Traceback (most recent call last): chromeos-chrome-61.0.3163.0_rc-r1: File "../../../../../../../home/chrome-bot/chrome_root/src/chrome/browser/resources/unpack_pak.py", line 67, in <module> chromeos-chrome-61.0.3163.0_rc-r1: main() chromeos-chrome-61.0.3163.0_rc-r1: File "../../../../../../../home/chrome-bot/chrome_root/src/chrome/browser/resources/unpack_pak.py", line 63, in main chromeos-chrome-61.0.3163.0_rc-r1: unpack(args.pak_file, args.out_folder) chromeos-chrome-61.0.3163.0_rc-r1: File "../../../../../../../home/chrome-bot/chrome_root/src/chrome/browser/resources/unpack_pak.py", line 24, in unpack chromeos-chrome-61.0.3163.0_rc-r1: data = data_pack.DataPack.ReadDataPack(pak_path) chromeos-chrome-61.0.3163.0_rc-r1: File "/usr/lib64/python2.7/site-packages/grit/format/data_pack.py", line 60, in ReadDataPack chromeos-chrome-61.0.3163.0_rc-r1: raise WrongFileVersion chromeos-chrome-61.0.3163.0_rc-r1: grit.format.data_pack.WrongFileVersion chromeos-chrome-61.0.3163.0_rc-r1:
,
Jul 21 2017
,
Jul 21 2017
Maybe this one: https://codereview.chromium.org/2969123002, Add deduplication logic to .pak files
,
Jul 21 2017
|
|||
►
Sign in to add a comment |
|||
Comment 1 by wuchengli@chromium.org
, Jul 21 2017