From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 9A631C433F5 for ; Thu, 7 Oct 2021 14:10:53 +0000 (UTC) Received: from phobos.denx.de (phobos.denx.de [85.214.62.61]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id A2C01610A5 for ; Thu, 7 Oct 2021 14:10:52 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org A2C01610A5 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=denx.de Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=lists.denx.de Received: from h2850616.stratoserver.net (localhost [IPv6:::1]) by phobos.denx.de (Postfix) with ESMTP id 76891831A4; Thu, 7 Oct 2021 16:10:49 +0200 (CEST) Authentication-Results: phobos.denx.de; dmarc=none (p=none dis=none) header.from=denx.de Authentication-Results: phobos.denx.de; spf=pass smtp.mailfrom=u-boot-bounces@lists.denx.de DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=denx.de; s=phobos-20191101; t=1633615849; bh=3N8RAMXjFbd5ZM+etrwDxmoP6yXrqNPXPcl4+Zu26AI=; h=Subject:To:Cc:References:From:Date:In-Reply-To:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From; b=w3lOGYYyhtb/wuyZVnOihQ85+/ZgrQaJZsg/hpZkgI7086Q+/xVvszcNVEIMNwr7Q D0BTXTUv/prvCX+6e7wJUOd2ztYhzpCFXoeCHw99iqnGvif8D9z6/GlBcrxOsYH4kt uzavwjH8lmih4jKK8BtbS+1RroXkEB5la1NgNV4Zd3Cloa3CXR47MyxBXuXnKRM1Zw FTk4KNpfgxEhmeYpkYwvsUTZ+XPRn/wqgxJRwrNxal4bJaPbVteT1X/nkxevEvWh05 D5qucAq3z/l9vDAOMs9YGNexXttfwTcmN8Xm3P2iFiOF16lMuO9WLhRjJ7w8xj3O99 gtOKiZA0RA6aQ== Received: from [IPv6:2001:a61:617a:9501:5127:bd2d:c44a:a9fc] (unknown [IPv6:2001:a61:617a:9501:5127:bd2d:c44a:a9fc]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: sbabic@denx.de) by phobos.denx.de (Postfix) with ESMTPSA id 1127F82F1D; Thu, 7 Oct 2021 16:10:47 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=denx.de; s=phobos-20191101; t=1633615847; bh=3N8RAMXjFbd5ZM+etrwDxmoP6yXrqNPXPcl4+Zu26AI=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=ttqt6GHhZCAUmJgRooRokv30DCvYEJtHKo3uVmcfi1mE8Y+dNmu9hI/rJaa9r9K65 s+Qbv49NXJtFI22mvKi+Hy3hd9mB70dWJ/9xFrJmd7z6FNBweeM7vIlf8XERH83h0m qTXdSrDTqKUAkJ+nUqqtLwTPrmbFiDsC24USUEZ1E2882gx33aCB8qEOjgQK6he13e 9vjm3KL63eA4zSL24K/Q1+7NElr9us4UyLiSfXZB0zn6DgRr4Yg7dkV/8en2VjwYCA coYTWeK89vInMgjYLfj/sl9aDYRr1JEViHsRgMQfaRLWTI2XPv0iY6b0a4W2e54J4a RGy7t03lkXYCg== Subject: Re: buildman stops (crashed) on current master To: Simon Glass , Stefano Babic Cc: "U-Boot@lists.denx.de" References: <720a1fe2-894d-0e6c-ece5-b3c737857dd7@denx.de> From: Stefano Babic Message-ID: Date: Thu, 7 Oct 2021 16:10:46 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.13.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: de-DE Content-Transfer-Encoding: 7bit X-BeenThere: u-boot@lists.denx.de X-Mailman-Version: 2.1.34 Precedence: list List-Id: U-Boot discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: u-boot-bounces@lists.denx.de Sender: "U-Boot" X-Virus-Scanned: clamav-milter 0.103.2 at phobos.denx.de X-Virus-Status: Clean Hi Simon, On 07.10.21 15:43, Simon Glass wrote: > Hi Stefano, > > On Thu, 7 Oct 2021 at 04:37, Stefano Babic wrote: >> >> 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" > > I cannot see that link. Verified with Wolfgang. The CI's results are available only after having logged in to source.denxe.de. Without account, they are not shown and the server return not found (I was not aware of this). > I am not sure what is going on. Does it say > what signal killed it? Nothing, that makes an investigation difficult. It looks like it is bound (resource issue ?) with the runner or docker instance, because if I run the same buildman command on my host, it works until end and no errors are reported: aarch64: w+ xilinx_zynqmp_virt +===================== WARNING ====================== +This board uses CONFIG_SPL_FIT_GENERATOR. Please migrate +to binman instead, to avoid the proliferation of +arch-specific scripts with no tests. +==================================================== +WARNING: BL31 file bl31.bin NOT found, U-Boot will run in EL3 125 181 0 /306 xilinx_zynqmp_virt gitlab stops exactly with the last board, as if all work was done, but rather after a timeout and pipeline is set to failed (just a feeling). > > Does it sit there for an hour and timeout? If so, then I did see that > myself once recently, when the Kconfig needed stdin, but I could not > quitetie it down. I think buildman would provide it, but sometimes > not, apparently. So it can happen when there is an existing build > there and your new one which adds Kconfig options that don't have > defaults, or something like that? But anytime there is a new docker instance on gitlab runner, so this could happen only on local host. > > If that is it, you can repeat it by clearing out your .bm-work > directory then building just that board for one commit, then the next > (with the Kconfig change). > > Buildman is supposed to handle this, of course. I'm not sure what has changed. Ok, let's see. 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 =====================================================================