From: Kirill Smelkov <kirr@navytux.spb.ru>
To: Junio C Hamano <gitster@pobox.com>
Cc: Kirill Smelkov <kirr@navytux.spb.ru>, git@vger.kernel.org
Subject: Re: [PATCH] t/Makefile: Use $(sort ...) explicitly where needed
Date: Fri, 20 Jan 2012 10:34:50 +0400 [thread overview]
Message-ID: <20120120063450.GA15371@mini.zxlink> (raw)
In-Reply-To: <7v8vl3ic6o.fsf@alter.siamese.dyndns.org>
On Thu, Jan 19, 2012 at 02:01:51PM -0800, Junio C Hamano wrote:
> Kirill Smelkov <kirr@navytux.spb.ru> writes:
>
> > Starting from GNU Make 3.82 $(wildcard ...) no longer sorts the result
> > (from NEWS):
> >
> > * WARNING: Backward-incompatibility!
> > Wildcards were not documented as returning sorted values, but the results
> > have been sorted up until this release.. If your makefiles require sorted
> > results from wildcard expansions, use the $(sort ...) function to request
> > it explicitly.
> >
> > http://repo.or.cz/w/make.git/commitdiff/2a59dc32aaf0681dec569f32a9d7ab88a379d34f
> >
> > so we have to sort tests list or else they are executed in seemingly
> > random order even for -j1.
>
> I do not necessarily buy your "so we HAVE TO, OR ELSE".
>
> Even though I can understand "We can sort the list of tests _if_ we do not
> want them executed in seemingly random order when running 'make -j1'", I
> tend to think that *if* is a big one. Aren't these tests designed not to
> depend on each other anyway?
Yes, they don't depend on each other, but what's the point in not
sorting them? I usually watch test progress visually, and if tests are
sorted, even with make -j4 they go more or less incrementally by their t
number.
On my netbook, adding $(sort ...) adds approximately 0.008s to make
startup, so imho there is no performance penalty to adding that sort.
Thanks,
Kirill
next prev parent reply other threads:[~2012-01-20 6:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-19 20:17 [PATCH] t/Makefile: Use $(sort ...) explicitly where needed Kirill Smelkov
2012-01-19 22:01 ` Junio C Hamano
2012-01-20 6:34 ` Kirill Smelkov [this message]
2012-01-20 7:14 ` Junio C Hamano
2012-01-20 7:19 ` Kirill Smelkov
2012-01-22 19:17 ` Kirill Smelkov
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=20120120063450.GA15371@mini.zxlink \
--to=kirr@navytux.spb.ru \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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 NNTP newsgroup(s).