logdog does not complete loading of buildpackages log |
||
Issue descriptionhttps://luci-logdog.appspot.com/logs/chromeos/buildbucket/cr-buildbucket.appspot.com/8924252895911936016/+/steps/BuildPackages/0/stdout This copies about 300k of logs, then hangs forever. Marking pri-1 because it blocks further analysis of failed CQ run. I'll mark it down if I find a workaround.
,
Jan 15
The build was cancelled, so the log hanging is WAI. You're not going to see any more log data than what you already see. https://screenshot.googleplex.com/RGuGU7GVW3G Gracefully closing the log stream is tracked in the dupe bug.
,
Jan 15
Something seems wrong though. The annotator summary seems to indicate that reef-paladin caused the build failure: https://chromiumos-build-annotator.googleplex.com/build_annotations/edit_annotations/master-paladin/3359014/? 10 builders: The BuildPackages stage failed: (15, 'Received signal 15; shutting down') | 56 builders: aborted by self-destruction | betty-arc64-paladin: The Uprev stage failed: /b/swarming/w/ir/cache/cbuild/repository/chromite/bin/cros_mark_as_stable failed (code=1) | reef-paladin: The BuildPackages stage failed: [Errno 2] No such file or directory: '/b/swarming/w/ir/cache/cbuild/repository/chroot/tmp/tmpWvah6w' The Report stage failed: board overlay not found: reef | winky-paladin,daisy_spring-paladin: The UpdateSDK stage failed: (15, 'Received signal 15; shutting down') Otherwise, which builder caused the failure? And how can I find more details?
,
Jan 15
Use the CommitQueueCompletion step to see which builders failed on which steps: https://ci.chromium.org/p/chromeos/builders/luci.chromeos.general/Prod/b8924254033478978400
,
Jan 15
I see---I can get there following the "Milo Build Details" link. I still cannot see which build failed, but let's discuss this on a different bug. Thanks. |
||
►
Sign in to add a comment |
||
Comment 1 by semenzato@chromium.org
, Jan 15