From: Junio C Hamano <gitster@pobox.com>
To: "SZEDER Gábor" <szeder.dev@gmail.com>
Cc: Taylor Blau <me@ttaylorr.com>,
"brian m. carlson" <sandals@crustytoothpaste.net>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
git@vger.kernel.org
Subject: Re: Travis not looking so good
Date: Thu, 27 Jun 2019 09:46:51 -0700 [thread overview]
Message-ID: <xmqqy31nasck.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <20190627132319.GB21574@szeder.dev> ("SZEDER =?utf-8?Q?G?= =?utf-8?Q?=C3=A1bor=22's?= message of "Thu, 27 Jun 2019 15:23:19 +0200")
SZEDER Gábor <szeder.dev@gmail.com> writes:
> However, we've always used the macOS build jobs as "build and test
> with the latest and greatest", i.e. they install the latest available
> Perforce and Git-LFS. To keep up with this tradition we'd need to run
> 'brew update' and in turn would need to 'brew install gcc'.
>
> [1] See e.g. a1ccaedd62 (travis-ci: make the OSX build jobs' 'brew
> update' more quiet, 2019-02-02) or
>
> https://public-inbox.org/git/20180907032002.23366-1-szeder.dev@gmail.com/T/#u
Is the reason why you did not submit your bonus patch [*1*] in the series at
https://public-inbox.org/git/20190614100059.13540-1-szeder.dev@gmail.com/
because it goes the opposite way, i.e. "build and test with whatever
happens to be in the image"?
Unless what happens to come in the image at travis-ci.org is
hopelessly outdated and does not match what normal users run, isn't
it is better to test with "whatever happens to be there" than not to
test at all due to missing compiler?
[Reference]
*1* ... what I picked up from your branch reproduced here
https://public-inbox.org/git/xmqqy324t4g0.fsf@gitster-ct.c.googlers.com/
It is missing explanation and sign-off, but if it lets the build
jobs run, even in a tad stale environment, it may be worth
resurrecting until those who want macOS port working can come up
with a real "with the latest and greatest" alternative.
next prev parent reply other threads:[~2019-06-27 16:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-30 19:32 Travis not looking so good Johannes Schindelin
2019-06-01 0:41 ` brian m. carlson
2019-06-02 11:22 ` SZEDER Gábor
2019-06-26 20:35 ` Taylor Blau
2019-06-27 13:23 ` SZEDER Gábor
2019-06-27 16:46 ` Junio C Hamano [this message]
2019-06-29 17:01 ` SZEDER Gábor
2019-07-03 10:47 ` [PATCH 1/2] ci: don't update Homebrew SZEDER Gábor
2019-07-03 10:47 ` [PATCH 2/2] ci: disable Homebrew's auto cleanup SZEDER Gábor
2019-07-03 11:49 ` Johannes Schindelin
2019-07-03 12:26 ` Thomas Braun
2019-07-03 13:04 ` SZEDER Gábor
2019-07-03 16:58 ` Junio C Hamano
2019-07-06 16:16 ` [PATCH] ci/lib.sh: update a comment about installed P4 and Git-LFS versions SZEDER Gábor
2019-07-06 16:21 ` [PATCH v1.1] " SZEDER Gábor
2019-07-08 10:00 ` Johannes Schindelin
2019-07-09 16:32 ` [PATCH 1/2] ci: don't update Homebrew Taylor Blau
2019-07-10 22:33 ` Junio C Hamano
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=xmqqy31nasck.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=me@ttaylorr.com \
--cc=sandals@crustytoothpaste.net \
--cc=szeder.dev@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.