All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: bakulinm@ispras.ru
Cc: Pavel Dovgalyuk <pavel.dovgalyuk@ispras.ru>,
	qemu-devel@nongnu.org, pbonzini@redhat.com,
	alex.bennee@linaro.org, philmd@redhat.com, crosa@redhat.com,
	wainersm@redhat.com, bleal@redhat.com
Subject: Re: [PATCH] tests/avocado: using several workers while testing
Date: Wed, 16 Nov 2022 14:42:51 +0000	[thread overview]
Message-ID: <Y3T26+ZNRsd7ELbB@redhat.com> (raw)
In-Reply-To: <99df713da53c1f8b726a1fdb63c8473f@ispras.ru>

On Wed, Nov 16, 2022 at 02:37:43PM +0000, bakulinm@ispras.ru wrote:
> Valid point, thank you.
> 
> I can see three options what to do:
> e1) Ignore older version of make and assume that 4.2 or newer is used
> (4.1 is in Ubuntu 18.04 that is no longer supported as a build platform
> as I was told; 20.04 has 4.2). In this case make provides number of
> jobs in $MAKEFLAGS and this makes getting it trivial. In case of an
> older make only two options will be available: (default) single-threaded,
> and using all cores.

> Which one should I choose?

Ignore older make. Ubuntu 18.04 is not a platform we target anymore,
so we shouldn't be writing compat code for handling it, and in any
case degrading to single threaded or all-cores is fine fallback IMHO.

With regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|



  reply	other threads:[~2022-11-16 14:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-16 13:48 [PATCH] tests/avocado: using several workers while testing Pavel Dovgalyuk
2022-11-16 14:06 ` Daniel P. Berrangé
2022-11-16 14:37   ` bakulinm
2022-11-16 14:42     ` Daniel P. Berrangé [this message]
2022-11-22 11:14       ` bakulinm

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=Y3T26+ZNRsd7ELbB@redhat.com \
    --to=berrange@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=bakulinm@ispras.ru \
    --cc=bleal@redhat.com \
    --cc=crosa@redhat.com \
    --cc=pavel.dovgalyuk@ispras.ru \
    --cc=pbonzini@redhat.com \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=wainersm@redhat.com \
    /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.