Re: Travis not looking so good

From: Junio C Hamano <gitster@pobox.com>
Date: Jun 27, 2019, 16:46 UTC
Message-ID: <xmqqy31nasck.fsf@gitster-ct.c.googlers.com>
In-Reply-To: <20190627132319.GB21574@szeder.dev>

SZEDER Gábor <szeder.dev@gmail.com> writes:

Show 9 quoted lines

> 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.