All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Glass <sjg@chromium.org>
To: u-boot@lists.denx.de
Subject: [PATCH 1/1] test/py: use actual core count for parallel builds
Date: Sun, 31 May 2020 08:08:27 -0600	[thread overview]
Message-ID: <CAPnjgZ1pXPf6LGZQL=7OF-7dXvSuFxWLB1tnSB-h=Z7+-e2fBA@mail.gmail.com> (raw)
In-Reply-To: <20200530224424.140021-1-xypron.glpk@gmx.de>

On Sat, 30 May 2020 at 16:44, Heinrich Schuchardt <xypron.glpk@gmx.de> wrote:
>
> When building U-Boot we should not blindly use make -j8 but consider the
> actual core count given by os.cpu_count().
>
> Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
> ---
>  test/py/conftest.py | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>

Reviewed-by: Simon Glass <sjg@chromium.org>

I did send a patch to make this use buildman, but people were not keen
on the extra dependency.


> diff --git a/test/py/conftest.py b/test/py/conftest.py
> index e3392ff6bc..30920474b3 100644
> --- a/test/py/conftest.py
> +++ b/test/py/conftest.py
> @@ -156,7 +156,7 @@ def pytest_configure(config):
>                  o_opt = ''
>              cmds = (
>                  ['make', o_opt, '-s', board_type + '_defconfig'],
> -                ['make', o_opt, '-s', '-j8'],
> +                ['make', o_opt, '-s', '-j{}'.format(os.cpu_count())],
>              )
>              name = 'make'
>
> --
> 2.26.2
>

  reply	other threads:[~2020-05-31 14:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-30 22:44 [PATCH 1/1] test/py: use actual core count for parallel builds Heinrich Schuchardt
2020-05-31 14:08 ` Simon Glass [this message]
2020-05-31 19:14 ` Stephen Warren
2020-06-03 16:27 ` 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='CAPnjgZ1pXPf6LGZQL=7OF-7dXvSuFxWLB1tnSB-h=Z7+-e2fBA@mail.gmail.com' \
    --to=sjg@chromium.org \
    --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.