From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: "SZEDER Gábor" <szeder.dev@gmail.com>, git@vger.kernel.org
Subject: Re: Travis not looking so good
Date: Sat, 1 Jun 2019 00:41:43 +0000 [thread overview]
Message-ID: <20190601004143.GN8616@genre.crustytoothpaste.net> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.1905302125190.44@tvgsbejvaqbjf.bet>
[-- Attachment #1: Type: text/plain, Size: 1452 bytes --]
On 2019-05-30 at 19:32:41, Johannes Schindelin wrote:
> 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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 868 bytes --]
next prev parent reply other threads:[~2019-06-01 0:41 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 [this message]
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
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
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=20190601004143.GN8616@genre.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--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.
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).