All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Glass <sjg@chromium.org>
To: Harald Seiler <hws@denx.de>
Cc: U-Boot Mailing List <u-boot@lists.denx.de>,
	Tom Rini <trini@konsulko.com>
Subject: Re: Two jobs at once on denx-vulcan?
Date: Mon, 20 Sep 2021 08:06:19 -0600	[thread overview]
Message-ID: <CAPnjgZ0PS-mTuvj-uJBy8u1ai1kQMCvDXwnQskE4F7rjdB5HAQ@mail.gmail.com> (raw)
In-Reply-To: <654d5288acac8259d2fe10abb882a66941b742ef.camel@denx.de>

Hi Harald,

On Mon, 20 Sept 2021 at 02:12, Harald Seiler <hws@denx.de> 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.

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.

Regards,
Simon

  reply	other threads:[~2021-09-20 14:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-18 16:37 Two jobs at once on denx-vulcan? Simon Glass
2021-09-20  8:12 ` Harald Seiler
2021-09-20 14:06   ` Simon Glass [this message]
2021-09-24 14:01     ` Harald Seiler
2021-09-24 14:20       ` Tom Rini
2021-09-24 14:38         ` Simon Glass
2021-09-24 14:55           ` Tom Rini
2021-09-24 23:36             ` Simon Glass
2021-09-27 13:36               ` Tom Rini

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=CAPnjgZ0PS-mTuvj-uJBy8u1ai1kQMCvDXwnQskE4F7rjdB5HAQ@mail.gmail.com \
    --to=sjg@chromium.org \
    --cc=hws@denx.de \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    /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.