From: Mark Wielaard <mark@klomp.org>
To: Dodji Seketeli <dodji@seketeli.org>,
Matthias Maennich <maennich@google.com>
Cc: kernel-team@android.com, libabigail@sourceware.org, gprocida@google.com
Subject: Re: [PATCH] make: add distcheck-fast target
Date: Wed, 22 Apr 2020 13:19:53 +0200 [thread overview]
Message-ID: <e438e380448864ace0ad615f0122ad61108c2741.camel@klomp.org> (raw)
In-Reply-To: <87tv1ee3h8.fsf@seketeli.org>
On Mon, 2020-04-20 at 14:38 +0200, Dodji Seketeli wrote:
> Matthias Maennich <maennich@google.com> a écrit:
>
> > The default compression flag defined by automake via GZIP_ENV is --best.
> > That is pretty expensive for when you just want to make sure your change
> > is done properly to pass 'make distcheck'.
> >
> > Hence add a convenience target 'make distcheck-fast' that sets GZIP_ENV
> > to --fast and runs distcheck with that.
> >
> > On my machine, this almost cuts the 'make distcheck' time in half:
> >
> > distcheck 4min 40s
> > distcheck-fast 2min 32s
> >
> > This is not invasive as it does not change the existing distcheck
> > target.
> >
> > * Makefile.am: add distcheck-fast make target
>
> Applied to master. Thanks!
It also saves minutes on my machine. So I am using make distcheck-fast
on the buildbot workers too now. Hopefully that will speed up things
there too.
Thanks,
Mark
P.S. The ppc64 and ppc64le workers are down at the moment. They should
hopefully get back online soon (and go through the backlog).
https://builder.wildebeest.org/buildbot/#/pendingbuildrequests
prev parent reply other threads:[~2020-04-22 11:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 7:46 Matthias Maennich
2020-04-20 12:38 ` Dodji Seketeli
2020-04-22 11:19 ` Mark Wielaard [this message]
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=e438e380448864ace0ad615f0122ad61108c2741.camel@klomp.org \
--to=mark@klomp.org \
--cc=dodji@seketeli.org \
--cc=gprocida@google.com \
--cc=kernel-team@android.com \
--cc=libabigail@sourceware.org \
--cc=maennich@google.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).