From: Matthias Maennich <maennich@google.com>
To: Thomas Schwinge <thomas@codesourcery.com>
Cc: libabigail@sourceware.org
Subject: Re: [PATCH] Better highlight 'make distcheck-fast'
Date: Thu, 9 Dec 2021 12:13:32 +0000 [thread overview]
Message-ID: <YbHy7KwRmHpjnhhS@google.com> (raw)
In-Reply-To: <20211209120701.1606881-1-thomas@codesourcery.com>
On Thu, Dec 09, 2021 at 01:07:01PM +0100, Thomas Schwinge wrote:
>... for the reasons stated.
>
> * CONTRIBUTING: Better highlight 'make distcheck-fast'.
>
>Signed-off-by: Thomas Schwinge <thomas@codesourcery.com>
>---
Thanks! That makes totally sense. :-)
> CONTRIBUTING | 20 +++++++++++---------
> 1 file changed, 11 insertions(+), 9 deletions(-)
>
>diff --git CONTRIBUTING CONTRIBUTING
>index 7e3e8561..4e70d381 100644
>--- CONTRIBUTING
>+++ CONTRIBUTING
>@@ -63,25 +63,27 @@ is important, because that is how we do to actually release the
> tarball of the project that you can download from the internet) then
> you can do:
>
>- make distcheck
>+ make distcheck-fast
>
> This actually builds the tarball, then untars it, configure/compile
> the untarred source code and launches the regression checks from
> there.
>
>+Here, "make distcheck-fast" is a variant of the standard "make distcheck".
>+It compresses with "--fast" instead of default "--best", and is
>+significantly faster, given the size of the distribution. You very likely
>+want to use that one for local regression testing.
>+
> You can also launch this in parallel by doing:
>
>- make -jN -lN distcheck
>+ make -jN -lN distcheck-fast
>
> with N being the number of processor core you have on your system.
>
>-Please make sure you always launch "make distcheck" before sending a
>+Please make sure you always launch "make distcheck-fast" before sending a
> patch, so that you are sure that we can always build a tarball after
> your patch is applied to the source tree.
>
>-A variant of distcheck is "make distcheck-fast". It's like "make
>-distcheck" but it's faster. You can just use that one.
>-
Instead mention that `make distcheck-fast` is not supposed to be used to
create artifacts for distribution, because it creates _different_
results.
> A complementary regression checking target is "check-self-compare".
> You invoke it by doing "make check-self-compare". That target
> analyzes the ABI of the libabigail.so shared object, serializes it
>@@ -89,11 +91,11 @@ into the ABIXML format and then compares the ABI internal
> representation gathered from the libabigail.so binary against the one
> gathered from the ABIXML format. The two should be equal if
> everything goes right. This is an important regression test. The
>-problem is that it can takes twice as much time as make distcheck. So
>-we've put it into its own separate target.
>+problem is that it can takes twice as much time as "make distcheck-fast".
>+So we've put it into its own separate target.
I would skip this occurrence or talke about "the `make distcheck*`
targets".
With the above:
Reviewed-by: Matthias Maennich <maennich@google.com>
Cheers,
Matthias
>
> So, to be complete the regression checking command to run against your
>-patch should be: "make check-self-compare distcheck -j16", if you have
>+patch should be: "make check-self-compare distcheck-fast -j16", if you have
> a machine with a 16 threads processors, for instance.
>
> Coding language and style
>--
>2.25.1
>
next prev parent reply other threads:[~2021-12-09 12:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-09 12:07 Thomas Schwinge
2021-12-09 12:13 ` Matthias Maennich [this message]
2021-12-09 21:38 ` Thomas Schwinge
2021-12-13 16:34 ` Dodji Seketeli
2021-12-14 16:44 ` [PATCH] Further update " Thomas Schwinge
2021-12-17 19:23 ` Dodji Seketeli
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=YbHy7KwRmHpjnhhS@google.com \
--to=maennich@google.com \
--cc=libabigail@sourceware.org \
--cc=thomas@codesourcery.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 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).