public inbox for [email protected]
help / color / mirror / Atom feedFrom: Kartik Ohri <[email protected]>
To: Chapman Flack <[email protected]>
Cc: [email protected]
Subject: Re: Just one Travis Mac OS build failed
Date: Wed, 15 Jul 2020 09:19:43 +0530
Message-ID: <CAASLQ4OQ_3nmgfxyh8=gDUXh3Ms+Xib9v2E6=tRkkN=E+rivTQ@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <CAASLQ4Mva7dAXiS_c9OLhV4VzNHF=XNKJosuS5gtZTB6b4TW1Q@mail.gmail.com>
<[email protected]>
<CAASLQ4MLFd6zhoh+sWWz+iu4d8+H2ML+y=kL990k7H=kk74pvA@mail.gmail.com>
<[email protected]>
<CAASLQ4Ms0QGf-Qh966HrsoaWzwf1SYHZ0WmZHApQePbcyPejCQ@mail.gmail.com>
<CAASLQ4NFHYH1pfGJtCZDfdcxf_ZzLA+X+ko86vpyRDKVYr489Q@mail.gmail.com>
<[email protected]>
<CAASLQ4PDcaAJ8fEwXXFW6XPakc7GCNVgPNGCxA8KYMzPDZw4+w@mail.gmail.com>
<[email protected]>
<CAASLQ4OuFQCiSMeypQtfRaAvj-4H-EAgszLwdAo6Tc1zS9B66g@mail.gmail.com>
<[email protected]>
<CAASLQ4PSizkzBKyyfkp9ccJ1qDPLRLu6g2bo9cN-XuTzGQFGfQ@mail.gmail.com>
<CAASLQ4P9zGxHda=HAGJ2eAa-oMmJtnPm=4a14mj4P-QpfFsYxg@mail.gmail.com>
<[email protected]>
<CAASLQ4NmornyOW8n-qyneLpDVPgV0Js=+=Eys6bw3Y-ZiVbVjA@mail.gmail.com>
<CAASLQ4OYvTQL7ssG4=QyEqhaB71=AM-svBUYj3uRdWXWoQgBPw@mail.gmail.com>
<[email protected]>
<[email protected]>
On Wed, Jul 15, 2020, 4:41 AM Chapman Flack <[email protected]> wrote:
> but for a very strange reason:
>
> /Users/travis/build/amCap1712/pljava/pljava-so/build.xml:72:
> /Users/travis/build/amCap1712/pljava/pljava-so/pg_config.h doesn't exist
>
> The line in build.xml says this:
>
> <filelist files="pg_config.h" dir="${PGSQL_INCLUDEDIR}"/>
>
> so it is very strange for Ant to complain about pg_config.h not being
> in its current directory. Of course it isn't, it's in $PGSQL_INCLUDEDIR!
>
> It is as if the dir= is being ignored, or $PGSQL_INCLUDEDIR is unset,
> or something. Just for this one build? Odd.
>
This is a known issue. Sometimes, one or two macOS builds fail. The
underlying cause is that macports is unable to connect using rsync protocol
to the outside world. This happens once in a while and since we have 10
macOS VMs in a build, it happens in every or every second build.
I had opened a ticket with the Travis support regarding this but they
rubbished it as an issue with Github availability. I'll rerun the build and
it passed https://travis-ci.com/github/amCap1712/pljava/builds/175645465.
This is a bit annoying. I do not know how to solve this yet. Last time I
checked, the macports devs themselves face this issue. I'll recheck with
them to know if a solution has been found. For the time being, the solution
is to manually rerun the failing job from Travis dashboard.
>
view thread (104+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: Just one Travis Mac OS build failed
In-Reply-To: <CAASLQ4OQ_3nmgfxyh8=gDUXh3Ms+Xib9v2E6=tRkkN=E+rivTQ@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox