git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Matheus Tavares Bernardino <matheus.bernardino@usp.br>
Cc: git <git@vger.kernel.org>
Subject: Re: macOS builds having trouble at travis-ci.org?
Date: Sat, 21 Mar 2020 15:54:59 -0700	[thread overview]
Message-ID: <xmqqd0958gjg.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <CAHd-oW7B+Q+hGfAkbu8PYjhQ+-81u9L-swk-iHzasHuJOh5GLA@mail.gmail.com> (Matheus Tavares Bernardino's message of "Sat, 21 Mar 2020 19:35:53 -0300")

Matheus Tavares Bernardino <matheus.bernardino@usp.br> writes:

> On Sat, Mar 21, 2020 at 6:38 PM Junio C Hamano <gitster@pobox.com> wrote:
>>
>> Starting sometime yeserday, it appears that macOS builds of our
>> branches at travis-ci.org are having trouble in an undiagnosable
>> way.  All you see on their webpage is a helpful message "An error
>> occurred while generating the build script." and nothing else.
>
> It might be a problem at the travis-ci infrastructure. They reported
> an issue with macOS builds failing two days ago[1]. The issue is
> marked as solved, but there are still some reports[2] from people
> getting the same error message we are experiencing in git.git.
>
> [1]: https://www.traviscistatus.com/incidents/9861dc7dtsb0
> [2]: https://twitter.com/traviscistatus/status/1240759726905815040

I knew we have folks who have wider antennae on these things than I
do ;-)

Thanks.  This means that we can just wait to see what happens at
least fo now ;-)



      reply	other threads:[~2020-03-21 22:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-21 21:37 macOS builds having trouble at travis-ci.org? Junio C Hamano
2020-03-21 22:35 ` Matheus Tavares Bernardino
2020-03-21 22:54   ` 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=xmqqd0958gjg.fsf@gitster.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=matheus.bernardino@usp.br \
    /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).