Issue metadata
Sign in to add a comment
|
unable to build asuka R67: chomeos-chrome: perfetto checkout error |
||||||||||||||||||||||||
Issue descriptionChrome Version: chromeos-chrome-67.0.3396.127_rc-r1 OS: Auska Did a repo init with minilayout to build R67 After adding some ebuild manually [cros_workon --board asuka start cr50-utils chromeos-base/autotest-cheets-libs media-libs/dlm chromeos-base/easy-unlock-crypto chromeos-base/arc-oemcrypto chromeos-base/chromeos-assets chromeos-base/shill autotest-private] Compilation fails for chromeos-chrome: * ERROR: chromeos-base/chromeos-chrome-67.0.3396.127_rc-r1::chromiumos failed (unpack phase): * (no error message) Looking deeper running sync_chrome /mnt/host/source/chromite/bin/sync_chrome --tag=67.0.3396.127 --reset --gclient=/home/gwendal/depot_tools/gclient /var/cache/chromeos-cache/distfiles/target/chrome-src 2>&1 | tee /tmp/fail_sync_chrome.txt There is a problem with perfetto, its directory is already present, so moved out. However, later it is reported missing. Trying a full repo.
,
Oct 8
Fails for full repo as well. * ERROR: chromeos-base/chromeos-chrome-67.0.3396.127_rc-r1::chromiumos failed (unpack phase): * (no error message)
,
Oct 8
Looking at /mnt/host/source/chromite/bin/sync_chrome --tag=67.0.3396.127 --reset --gclient=/home/gwendal/depot_tools/gclient /var/cache/chromeos-cache/distfiles/target/chrome-src 2>&1 | tee /tmp/fail_sync_chrome.txt [in progress] still see "[0:01:11] fatal: Unable to find remote helper for 'persistent-https'" Looking at .gitconfig for real.
,
Oct 8
have you tried what i recommended in comment #1 ?
,
Oct 8
I removed 'persistent-https' but it still failed. I think we need https://chromium-review.googlesource.com/c/chromiumos/overlays/chromiumos-overlay/+/1269640 backported to R67. In the log, I see the same error message: OSError: Execution failed with error: [Errno 2] No such file or directory. Check that None or cipd exist and have execution permission.
,
Oct 9
,
Oct 9
Reopened, still fails checkout. Potential problems: Error: Command 'git checkout --quiet 89c6af1578dd6ed086fd144fdd19ae5fa7183435' returned non-zero exit status 128 in /var/cache/chromeos-cache/distfiles/target/chrome-src/src/third_party/webrtc fatal: reference is not a tree: 89c6af1578dd6ed086fd144fdd19ae5fa7183435 But this error is gone during the second try. This error persists: OSError: Execution failed with error: [Errno 2] No such file or directory. Check that None or cipd exist and have execution permission. ^[[0msync_chrome: Unhandled exception:
,
Oct 9
I did not mark new chromeos-chrome as stable like e22314e7eeef5e7ecc89a52fec3106816d4f7bbd did. I then need to rebuild an asuka image. Interestingly, building asuka works in the builder as is: https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?buildbucketId=8933167920938626912
,
Oct 9
regarding #8, as noted in BUG 833678 , sync problem was limited to chroot builds, but builders were fine.
,
Oct 11
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/5607da4712b97da437d38c951ed9c57e73337a81 commit 5607da4712b97da437d38c951ed9c57e73337a81 Author: Gwendal Grignou <gwendal@chromium.org> Date: Thu Oct 11 06:55:54 2018 Manually marking chromeos-chrome ebuild as stable Updated ebuild from 9999 after changes from https://chromium-review.googlesource.com/c/1269640 BUG= chromium:833678 , chromium:892963 TEST=build_packages and build_image works. Image install on asuka. Change-Id: I20efa3179d21f4df8dbcc5852bf153ccab271412 Signed-off-by: Gwendal Grignou <gwendal@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/c/1274174 Reviewed-by: Mike Frysinger <vapier@chromium.org> [rename] https://crrev.com/5607da4712b97da437d38c951ed9c57e73337a81/chromeos-base/chromeos-chrome/chromeos-chrome-67.0.3396.127_rc-r2.ebuild
,
Oct 15
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by vapier@chromium.org
, Oct 7Owner: gwendal@chromium.org