From: | Chapman Flack <chap(at)anastigmatix(dot)net> |
---|---|
To: | Kartik Ohri <kartikohri13(at)gmail(dot)com> |
Cc: | pljava-dev(at)lists(dot)postgresql(dot)org |
Subject: | Re: Just one Travis Mac OS build failed |
Date: | 2020-07-15 12:03:56 |
Message-ID: | 5F0EF0AC.8090208@anastigmatix.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pljava-dev |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Chapman Flack | 2020-07-15 12:24:58 | Re: PL/Java new build plugin |
Previous Message | Kartik Ohri | 2020-07-15 11:57:07 | Re: Just one Travis Mac OS build failed |