Subject: Re: Just one Travis Mac OS build failed
To: Kartik Ohri <kartikohri13@gmail.com>
References: 
 <CAASLQ4Mva7dAXiS_c9OLhV4VzNHF=XNKJosuS5gtZTB6b4TW1Q@mail.gmail.com>
 <CAASLQ4NFHYH1pfGJtCZDfdcxf_ZzLA+X+ko86vpyRDKVYr489Q@mail.gmail.com>
 <5F0734AD.7060001@anastigmatix.net>
 <CAASLQ4PDcaAJ8fEwXXFW6XPakc7GCNVgPNGCxA8KYMzPDZw4+w@mail.gmail.com>
 <5F077926.2050806@anastigmatix.net>
 <CAASLQ4OuFQCiSMeypQtfRaAvj-4H-EAgszLwdAo6Tc1zS9B66g@mail.gmail.com>
 <5F07C2D5.5050904@anastigmatix.net>
 <CAASLQ4PSizkzBKyyfkp9ccJ1qDPLRLu6g2bo9cN-XuTzGQFGfQ@mail.gmail.com>
 <CAASLQ4P9zGxHda=HAGJ2eAa-oMmJtnPm=4a14mj4P-QpfFsYxg@mail.gmail.com>
 <5F0D35BA.30904@anastigmatix.net>
 <CAASLQ4NmornyOW8n-qyneLpDVPgV0Js=+=Eys6bw3Y-ZiVbVjA@mail.gmail.com>
 <CAASLQ4OYvTQL7ssG4=QyEqhaB71=AM-svBUYj3uRdWXWoQgBPw@mail.gmail.com>
 <5F0E3972.5070609@anastigmatix.net> <5F0E3B91.8080307@anastigmatix.net>
 <CAASLQ4OQ_3nmgfxyh8=gDUXh3Ms+Xib9v2E6=tRkkN=E+rivTQ@mail.gmail.com>
 <5F0EE9D4.2070500@anastigmatix.net>
 <CAASLQ4MOQsAqYot0pcQ-h9a1WYF9iuS4EWDYsGXn36Gi5BQrwQ@mail.gmail.com>
Cc: pljava-dev@lists.postgresql.org
From: Chapman Flack <chap@anastigmatix.net>
Message-ID: <5F0EF0AC.8090208@anastigmatix.net>
Date: Wed, 15 Jul 2020 08:03:56 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
 Thunderbird/38.7.0
MIME-Version: 1.0
In-Reply-To: 
 <CAASLQ4MOQsAqYot0pcQ-h9a1WYF9iuS4EWDYsGXn36Gi5BQrwQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Precedence: bulk

On 07/15/20 07:57, Kartik Ohri wrote:
>>
>> Does Travis have any third status for a build, between 'succeeded' and
>> 'failed', like 'skipped'?
>>
> It is not possible to mark skipped. It is possible to mark succeeded but I
> think that will be more dangerous than the red. I had a thought that we
> could have a serverless function in the cloud somewhere. We can try to
> detect if the failure is due to download error in macports and send a
> signal to the function. Then the job is terminated immediately. The
> function then triggers this failed job by submitting an API call. Since,
> the issue vanishes on retrying, doing such retries for at most a 2-3 times
> would work. What do you think?

That sounds rather elaborate. Maybe it would be enough to simply check
for the prerequisites early, and just fail the job with a very short
log file that says MACPORTS FAILED TO DOWNLOAD - RE-RUN JOB. There would
still be red on the dashboard but it would be easy to see why.

Regards,
-Chap