All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefano Babic <sbabic@denx.de>
To: "U-Boot@lists.denx.de" <U-Boot@lists.denx.de>
Cc: Simon Glass <sjg@chromium.org>
Subject: buildman stops (crashed) on current master
Date: Thu, 7 Oct 2021 12:37:20 +0200	[thread overview]
Message-ID: <720a1fe2-894d-0e6c-ece5-b3c737857dd7@denx.de> (raw)

Hi all,

CI stops by building aarch64 without notice, for reference:

https://source.denx.de/u-boot/custodians/u-boot-imx/-/jobs/332319

There is no error, just process is killed. It looks like it stops at 
xilinx_zynqmp_virt,

./tools/buildman/buildman -o /tmp -P -E -W aarch64but board can be built 
without issues.

If I build on my host (not in docker, anyway), it generally builds fine 
- but it crashes sometimes, too. On gitlab instance , it crashes.
Issue does not seem that depends on merged patches, and introduces 
boards were already built successfully. Any hint ? I have also no idea 
what I should look as what I see is just

"usr/bin/bash: line 104:    24 Killed 
./tools/buildman/buildman -o /tmp -P -E -W aarch64"

Regards,
Stefano


-- 
=====================================================================
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic@denx.de
=====================================================================

             reply	other threads:[~2021-10-07 10:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-07 10:37 Stefano Babic [this message]
2021-10-07 13:43 ` buildman stops (crashed) on current master Simon Glass
2021-10-07 14:10   ` Stefano Babic
2021-10-19 15:39   ` Stefano Babic
2021-10-19 15:52     ` Simon Glass
2021-10-19 20:10       ` Stefano Babic
2021-10-19 22:53     ` Tom Rini
2021-10-19 22:59       ` Simon Glass
2021-10-19 23:01         ` Tom Rini
2021-10-20  3:42           ` Simon Glass
2021-10-20  9:54             ` Stefano Babic
2021-10-20 13:39               ` Simon Glass

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=720a1fe2-894d-0e6c-ece5-b3c737857dd7@denx.de \
    --to=sbabic@denx.de \
    --cc=U-Boot@lists.denx.de \
    --cc=sjg@chromium.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.