Re: Travis not looking so good

From: brian m. carlson <sandals@crustytoothpaste.net>
Date: Jun 1, 2019, 00:41 UTC
Message-ID: <20190601004143.GN8616@genre.crustytoothpaste.net>
In-Reply-To: <nycvar.QRO.7.76.6.1905302125190.44@tvgsbejvaqbjf.bet>

On 2019-05-30 at 19:32:41, Johannes Schindelin wrote:

Show 19 quoted lines

> Hi Gábor,
> 
> do you have any idea why Travis is failing like this in the macOS/gcc
> job?
> 
> > +case "$jobname" in
> > +brew link gcc@8
> > Error: No such keg: /usr/local/Cellar/gcc@8
> > The command "ci/install-dependencies.sh" failed and exited with 1 during .
> 
> I usually only look at the Azure Pipelines (which gives me plenty enough
> to do, what with pu's individual branches being tested individually), but
> couldn't fail to notice that *all* four branches (maint, master, next and
> pu) fail in Travis' macOS/gcc job (and only there, the Azure Pipelines are
> all green):
> 
> https://github.com/git/git/branches/all
> 
> What's going on?

I'm certainly not an expert on macOS, so I could be getting things wrong here, but it looks like we don't ever explicitly install the gcc@8 package from Homebrew. It may have happened to be installed automatically by Travis in the past, but they may have upgraded now that GCC 9 has been released.

I suspect if we want to use GCC 8, we need to explicitly install it by using "brew install gcc@8", or we can just pick the latest released GCC by using "brew install gcc" if we like that better. We will still need to do "brew link gcc" (or "gcc@8"), since I suspect Homebrew won't auto-link it since macOS provides a gcc binary.

-- 
brian m. carlson: Houston, Texas, US
OpenPGP: https://keybase.io/bk2204