unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: libc-alpha@sourceware.org
Subject: Re: [PATCH 01/13] nptl: Use .NOTPARALLEL in Makefile only if actually running tests
Date: Wed, 19 Feb 2020 14:28:54 -0300	[thread overview]
Message-ID: <14e408f8-f50f-9811-573d-44df1e0567ae@linaro.org> (raw)
In-Reply-To: <8c70433fadec18875b9114fd97f09bd527a7bd16.1581418947.git.fweimer@redhat.com>



On 11/02/2020 08:06, Florian Weimer wrote:
> It is safe to build the tests in parallel.

LGTM, thanks.

Reviewed-by: Adhemerval Zanella <adhemerval.zanella@linaro.org>

> ---
>  nptl/Makefile | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/nptl/Makefile b/nptl/Makefile
> index 6f210d60e3..40f27ea7cd 100644
> --- a/nptl/Makefile
> +++ b/nptl/Makefile
> @@ -693,7 +693,9 @@ tst-audit-threads-ENV = LD_AUDIT=$(objpfx)tst-audit-threads-mod1.so
>  
>  CFLAGS-tst-unwind-thread.c += -funwind-tables
>  
> -# The tests here better do not run in parallel
> +# The tests here better do not run in parallel.
> +ifeq ($(run-built-tests),yes)
>  ifneq ($(filter %tests,$(MAKECMDGOALS)),)
>  .NOTPARALLEL:
>  endif
> +endif
> 

  reply	other threads:[~2020-02-19 17:29 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-11 11:05 [PATCH 00/13] nptl: Move more functions from libpthread to libc Florian Weimer
2020-02-11 11:06 ` [PATCH 01/13] nptl: Use .NOTPARALLEL in Makefile only if actually running tests Florian Weimer
2020-02-19 17:28   ` Adhemerval Zanella [this message]
2020-02-11 11:06 ` [PATCH 02/13] nptl: Sort routines list in Makefile alphabetically Florian Weimer
2020-02-19 17:34   ` Adhemerval Zanella
2020-02-20  7:54     ` Florian Weimer
2020-02-11 11:06 ` [PATCH 03/13] nptl: Move pthread_attr_getschedpolicy implementation into libc Florian Weimer
2020-02-19 17:38   ` Adhemerval Zanella
2020-02-11 11:06 ` [PATCH 04/13] nptl: Move pthread_attr_setschedpolicy " Florian Weimer
2020-02-19 17:39   ` Adhemerval Zanella
2020-02-11 11:06 ` [PATCH 05/13] nptl: Move pthread_attr_getscope " Florian Weimer
2020-02-19 17:40   ` Adhemerval Zanella
2020-02-11 11:06 ` [PATCH 06/13] nptl: Move pthread_attr_setscope " Florian Weimer
2020-02-19 17:41   ` Adhemerval Zanella
2020-02-11 11:06 ` [PATCH 07/13] nptl: Move pthread_condattr_destroy " Florian Weimer
2020-02-19 17:42   ` Adhemerval Zanella
2020-02-11 11:06 ` [PATCH 08/13] nptl: Move pthread_condattr_init " Florian Weimer
2020-02-19 17:42   ` Adhemerval Zanella
2020-02-11 11:06 ` [PATCH 09/13] nptl: Move pthread_cond_destroy " Florian Weimer
2020-02-19 17:48   ` Adhemerval Zanella
2020-02-11 11:06 ` [PATCH 10/13] nptl: Move pthread_cond_init " Florian Weimer
2020-02-19 17:50   ` Adhemerval Zanella
2020-02-11 11:06 ` [PATCH 11/13] Add hidden prototypes for __sched_getparam, __sched_getscheduler Florian Weimer
2020-02-19 17:50   ` Adhemerval Zanella
2020-02-11 11:06 ` [PATCH 12/13] nptl: Move pthread_getschedparam implementation into libc Florian Weimer
2020-02-19 17:51   ` Adhemerval Zanella
2020-02-11 11:06 ` [PATCH 13/13] nptl: Move pthread_setschedparam " Florian Weimer
2020-02-19 17:52   ` Adhemerval Zanella

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

  List information: https://www.gnu.org/software/libc/involved.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=14e408f8-f50f-9811-573d-44df1e0567ae@linaro.org \
    --to=adhemerval.zanella@linaro.org \
    --cc=libc-alpha@sourceware.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).