From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Philippe Blain <levraiphilippeblain@gmail.com>,
git@vger.kernel.org, sunshine@sunshineco.com,
Johannes Schindelin <johannes.schindelin@gmx.de>
Subject: Re: [PATCH] ci/install-depends: attempt to fix "brew cask" stuff
Date: Wed, 27 Jan 2021 21:23:10 -0800 [thread overview]
Message-ID: <xmqqr1m5y6rl.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <YBHnV80bBQOxZH1O@coredump.intra.peff.net> (Jeff King's message of "Wed, 27 Jan 2021 17:21:11 -0500")
Jeff King <peff@peff.net> writes:
> The downside, of course, is that a failure that will happen on every
> platform will mean wasted CPU to trigger the same failure over and over.
> But:
>
> - I rarely see that myself, because I wouldn't bother pushing up to CI
> until "make test" passed locally. So usually I'm finding portability
> issues via CI. Other people might be different, though.
This is the same for me.
> - we already have the Windows tests in a separate matrix anyway, so a
> failure on Linux would run the whole Windows suite (which is an
> order of magnitude more expensive)
But they tend to finish earlier than OSX and Ubuntu jobs; their
sharding of the tests into 10 jobs may probably have something to do
with this.
> - even within the Windows matrix, I think running the rest of the
> tests after a failure is still valuable. If there's a second
> failure, you save a round-trip to CI (so it doesn't reduce CPU, but
> it may help latency to reach a passing state).
prev parent reply other threads:[~2021-01-28 5:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-15 3:14 [PATCH] ci/install-depends: attempt to fix "brew cask" stuff Junio C Hamano
2021-01-15 5:48 ` Junio C Hamano
2021-01-15 6:05 ` Eric Sunshine
2021-01-15 14:27 ` Derrick Stolee
2021-01-15 19:52 ` Junio C Hamano
2021-01-15 19:59 ` Jeff King
2021-01-15 20:07 ` Eric Sunshine
2021-01-15 20:46 ` Jeff King
2021-02-01 22:11 ` SZEDER Gábor
2021-01-24 2:41 ` Philippe Blain
2021-01-24 6:18 ` Junio C Hamano
2021-01-25 0:56 ` Taylor Blau
2021-01-27 22:21 ` Jeff King
2021-01-28 5:23 ` Junio C Hamano [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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqr1m5y6rl.fsf@gitster.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=johannes.schindelin@gmx.de \
--cc=levraiphilippeblain@gmail.com \
--cc=peff@peff.net \
--cc=sunshine@sunshineco.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).