Chrome PFQ and pre-CQ keep failing |
||||||||||||
Issue descriptionhttps://cros-goldeneye.corp.google.com/chromeos/console/listChromePfqBuild#/ tricky-chrome-pfq and peppy-chrome-pfq showed: Command <mosys memory spd print geometry -s size_mb> failed, rc=-6, Command returned non-zero exit status
,
Sep 4
,
Sep 4
,
Sep 4
This looks not limited to Chrome PFQ. I hit the same issue on my pre-cq try. https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?buildbucketId=8936345568402580784
,
Sep 4
I seem to have this on my local build.
,
Sep 4
The error message:
ERROR : Command 'sudo syslinux -d /syslinux "${ESP_DEV}"' exited with nonzero code: 1
started from 11031.0.0
,
Sep 4
,
Sep 4
,
Sep 4
Wait, are the errors in OP and c#1 happening at the same time?
,
Sep 4
Not at the same time. The bug in c#1 seemed to be fixed.
,
Sep 4
If c#1 seems to be fixed, then mosys will likely be fixed soon by https://chromium-review.googlesource.com/c/chromiumos/platform/mosys/+/1203572.
,
Sep 4
,
Sep 4
,
Sep 4
,
Sep 5
This: ... Segmentation fault (core dumped) mattrib -h -r -s s:/ldlinux.sys 2> /dev/null syslinux: failed to create ldlinux.sys no longer happens for me after sync this morning.
,
Sep 5
Yeah, so I think this is actually another case of the mosys crash.
,
Sep 5
I think we can probably close this bug since the main issues (mosys and the build_image failures) have been fixed? Please re-open if there's some work pending.
,
Sep 24
FWIW, I ran into the symptoms described in comment #1 for a few days - i.e. mattrib crashes. mattrib is a symlink to mtools and my problems went away after I did "sudo emerge mtools" inside the chroot. INFO : Extracting the kernel command line from /mnt/host/source/src/build/images/caroline/R71-11032.0.0-rc1/vmlinuz.image sh: line 1: 11344 Segmentation fault (core dumped) mattrib -h -r -s s:/ldlinux.sys 2> /dev/null syslinux: failed to create ldlinux.sys |
||||||||||||
►
Sign in to add a comment |
||||||||||||
Comment 1 by edcourtney@chromium.org
, Sep 4Labels: -Pri-2 Pri-0
Owner: chuntsen@chromium.org
Status: Assigned (was: Untriaged)
In particular, it looks like build image is failing. Here are some suspicious logs: INFO : Extracting the kernel command line from /mnt/host/source/src/build/images/caroline/R71-11032.0.0-rc1/vmlinuz.image sh: line 1: 11344 Segmentation fault (core dumped) mattrib -h -r -s s:/ldlinux.sys 2> /dev/null syslinux: failed to create ldlinux.sys ERROR : Mon Sep 3 19:04:15 PDT 2018 ERROR : PGID PPID PID ELAPSED TIME %CPU COMMAND ERROR : Arguments of 11122: '--arch=amd64' '--image_type=usb' '--to=/mnt/host/source/src/build/images/caroline/R71-11032.0.0-rc1/chromiumos_base_image.bin' '--from=/mnt/host/source/src/build/images/caroline/R71-11032.0.0-rc1/rootfs_dir/boot' '--vmlinuz=/mnt/host/source/src/build/images/caroline/R71-11032.0.0-rc1/rootfs_dir/boot/vmlinuz' '--to_offset=127926272' '--to_size=33554432' '--kernel_partition='/mnt/host/source/src/build/images/caroline/R71-11032.0.0-rc1/vmlinuz.image'' '--install_syslinux' ERROR : Backtrace: (most recent call is last) ERROR : update_bootloaders.sh:203:main(), called: die_err_trap ERROR : ERROR : Command failed: ERROR : Command 'sudo syslinux -d /syslinux "${ESP_DEV}"' exited with nonzero code: 1 umount: /tmp/esp.Rh73DU: not mounted. WARNING : Initial unmount failed. Possibly crosbug.com/23443. Retrying umount: /tmp/esp.Rh73DU: not mounted. INFO : Unmounting image from /mnt/host/source/src/build/images/caroline/R71-11032.0.0-rc1/stateful_dir and /mnt/host/source/src/build/images/caroline/R71-11032.0.0-rc1/rootfs_dir INFO : Unmounting temporary rootfs /mnt/host/source/src/build/images/caroline/R71-11032.0.0-rc1/rootfs_dir//build/rootfs. Cleaning up /usr/local symlinks for /mnt/host/source/src/build/images/caroline/R71-11032.0.0-rc1/stateful_dir/dev_image ERROR : Mon Sep 3 19:04:21 PDT 2018 ERROR : PGID PPID PID ELAPSED TIME %CPU COMMAND ERROR : Arguments of 9341: '/mnt/host/source/src/build/images/caroline/R71-11032.0.0-rc1' 'chromiumos_base_image.bin' '--adjust_part=' ERROR : Backtrace: (most recent call is last) ERROR : cros_make_image_bootable:443:main(), called: make_image_bootable '/mnt/host/source/src/build/images/caroline/R71-11032.0.0-rc1/chromiumos_base_image.bin' ERROR : cros_make_image_bootable:1:make_image_bootable(), called: die 'cros_make_image_bootable failed.' ERROR : ERROR : Error was: ERROR : cros_make_image_bootable failed. AFAICT this is affecting a lot of PFQs (including Android PFQ, but most chrome PFQs). PFQ is high priority I think so bumping this to P0 and CC'ing ChromeOS sheriffs and gardeners.