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 X-Spam-Level: X-Spam-Status: No, score=-5.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id EF92DC433EF for ; Fri, 24 Sep 2021 14:01:27 +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 14AA56105A for ; Fri, 24 Sep 2021 14:01:27 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org 14AA56105A 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 A5B8A83490; Fri, 24 Sep 2021 16:01:24 +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=1632492085; bh=5dEJMs4CUmR8HBKBYvJKO6Uq1VNoIIoiYxTQ2I2tdBE=; h=Subject:From:To:Cc:Date:In-Reply-To:References:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From; b=NufmKO+gYWphukcWuc5KOnqZP9oz/i3THp6LsueHhV6IIejWdiEbxtBRf9oT8DcLZ Jbkijzuat04z5fQ7/mGCg/CZw5LAc9A5D7EfP0BRO5r9AFOfOhVgEo0f3wvqjBsYP7 suk+dHE47uTAD9/cL7nVEB8rXepDZ+xB4Qk4GrcxoYm22sS1qB8fdFD1qzPNSntEys vmEiuTXo7nKb+Ays/Zd4+qJ5mnzpgqLxhIpdQKMceXgQRTBcGc7euvzfwwF1KOCzHq jUNawj2nVUhUBRNb9qvPbp8wmVKF5U6rpnUn1fk4v/VBthwTa8lgwyCNyDW7VP30Dr pP4VF5AHPmFtw== Received: from maia.denx.de (p578adb1c.dip0.t-ipconnect.de [87.138.219.28]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: hws@denx.de) by phobos.denx.de (Postfix) with ESMTPSA id 4AB428020E; Fri, 24 Sep 2021 16:01:22 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=denx.de; s=phobos-20191101; t=1632492082; bh=5dEJMs4CUmR8HBKBYvJKO6Uq1VNoIIoiYxTQ2I2tdBE=; h=Subject:From:To:Cc:Date:In-Reply-To:References:From; b=AevQOUpPEcrrfPTuhP/5xe9B5RTuxWLBASN9ukx6Jfj/MQ+15erffoID2ghxl8wiH xMbw/3u9N7Sr97Fb7dmwCuVEkalSVPX8bAsc3TsN8duBVt0tWlKSbpX4VYuTHVHn5j dHWfZ3PhvK+NLN5OeygLWQ8LJGjlpfqdGtQNDUV4ycJ0v5Q6lGRHAzpGl7FTQYgbcD EVaadjpoFiLTC6X5yZKwaHHAUokcNiKiBZ7Vq2WurRBAZUQR1s5++6FOM1j715Xzmp D3AokIiFgw6nFlVF1CCBkWYedUqAejksF7oWi+xfyxbIt/OB1VIl8tmmrZBLMNs4Jw VTbYlgjPBnulw== Message-ID: Subject: Re: Two jobs at once on denx-vulcan? From: Harald Seiler To: Simon Glass Cc: U-Boot Mailing List , Tom Rini Date: Fri, 24 Sep 2021 16:01:21 +0200 In-Reply-To: References: <654d5288acac8259d2fe10abb882a66941b742ef.camel@denx.de> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.40.4 (3.40.4-1.fc34) MIME-Version: 1.0 Content-Transfer-Encoding: 8bit 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 Mon, 2021-09-20 at 08:06 -0600, Simon Glass wrote: > Hi Harald, > > On Mon, 20 Sept 2021 at 02:12, Harald Seiler wrote: > > > > Hi, > > > > On Sat, 2021-09-18 at 10:37 -0600, Simon Glass wrote: > > > Hi, > > > > > > Is there something screwy with this? It seems that denx-vulcan does > > > two builds at once? > > > > > > https://source.denx.de/u-boot/custodians/u-boot-dm/-/jobs/323540 > > > > Hm, I did some changes to the vulcan runner which might have caused > > this... But still, even if it is running multiple jobs in parallel, they > > should still be isolated, so how does this lead to a build failure? > > I'm not sure that it does, but I do see this at the above link: > > Error: Unable to create > '/builds/u-boot/custodians/u-boot-dm/.git/logs/HEAD.lock': File > exists. This is super strange... Each build should be running in its own container so there should never be a way for such a race to occur. No clue what is going on here... > Re doing multiple builds, have you set it up so it doesn't take on the > very large builds? I would love to enable multiple builds for the qemu > steps since they mostly use a single CPU, but am not sure how to do > it. Actually, this was more a mistake than an intentional change. I updated the runner on vulcan to also take jobs for some other repos and wanted those jobs to run in parallel. It looks like I just forgot setting the `limit = 1` option for the U-Boot runner. Now, I think doing what you suggest is possible. We need to tag build and "test" jobs differently and then define multiple runners with different limits. E.g. in `.gitlab-ci.yml`: build all 32bit ARM platforms: stage: world build tags: - build cppcheck: stage: testsuites tags: - test And then define two runners in `/etc/gitlab-runner/config.toml`: concurrent = 4 [[runners]] name = "u-boot builder on vulcan" limit = 1 ... [[runners]] name = "u-boot tester on vulcan" limit = 4 ... and during registration they get the `build` and `test` tags respectively. This would allow running (in this example) up to 4 test jobs concurrently, but only ever one large build job at once. -- Harald DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: +49-8142-66989-62  Fax: +49-8142-66989-80   Email: hws@denx.de