Subject: feature/master/ci [was Re: Detecting test failures reported as
 warnings]
To: pljava-dev@lists.postgresql.org
References: <5EC17E17.7070002@anastigmatix.net>
 <5ED15825.9060504@anastigmatix.net>
 <CAASLQ4OXAb+_J=oK54PH5eYuXjkV9KMsoXEcp-TYaQPqxk1Xbg@mail.gmail.com>
 <5ED270BA.9010001@anastigmatix.net> <5ED3D488.1010401@anastigmatix.net>
 <5ED474CA.3000106@anastigmatix.net>
 <CAASLQ4PfvmgKPp+aFf_r5RsBwigc+EC5Hm2CuzwJSTDCT64i-A@mail.gmail.com>
 <5ED4EA10.4030801@anastigmatix.net>
 <CAASLQ4Px21jyb2vJYSrjF5P0RqhA-G_DDWR9QHG68r+W+AqbxQ@mail.gmail.com>
 <CAASLQ4NYE-TW6hjbkSOuAY2Z4NM2cYzqSQ9ahO2LAUhdP9axeQ@mail.gmail.com>
 <5ED7E74B.9020800@anastigmatix.net>
 <CAASLQ4Od6-0=3+4ENKh1Z-Wcu5Wir-bwUn_ccO2UCmDhoR4vtQ@mail.gmail.com>
 <5EDA576E.2000204@anastigmatix.net>
 <CAASLQ4OzPwZB6GG_cXNW4WU4zpHa6wm8Q3WRWNv5pZpis+gf3w@mail.gmail.com>
 <5EDBA5D9.8090506@anastigmatix.net>
 <CAASLQ4P8e9XfUh17HFhYE4eMtq5-C4dpHQAX+hCsia-UFNAjtA@mail.gmail.com>
 <5EE7AE8C.2040201@anastigmatix.net>
 <CAASLQ4PoMTiTZUPxTR7VS8LLo9tosAMu-89T5ikWub7VbM+r4Q@mail.gmail.com>
 <5EEA6F85.9040009@anastigmatix.net> <5F063C86.3070301@anastigmatix.net>
From: Chapman Flack <chap@anastigmatix.net>
Message-ID: <5F47EB62.2060306@anastigmatix.net>
Date: Thu, 27 Aug 2020 13:20:34 -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: <5F063C86.3070301@anastigmatix.net>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Precedence: bulk

Hi Kartik,

When convenient, could you merge PR #16 into your feature/master/ci
branch, and then open a pull request for that branch in the main
repository?

It has just completed builds in Travis and Appveyor, with just one
failed job each. In Travis it was a spurious failure where MacPorts
sometimes fails to find the openssl package, and as I mentioned earlier[1],
once your plugin work is integrated, we should not even need that
MacPorts package.

The one job that has been failing very consistently in Appveyor is
PG 10 MSVC, and I suspect there is an actual bug there I need to find,
not a problem with CI. So I think the CI is ready to go.

When you open the PR for it, please describe in the PR notes anything
that needs to be done in the main repo when the PR is merged. I.e., will
it just start working because the files are there, or do some administrative
actions need to be taken, registering with Travis / Appveyor, etc.

Then I will merge that PR relatively promptly (I generally try to let
them breathe for a day at least), and you can rebase your plugin branch
over it then.

Regards,
-Chap


[1] https://www.postgresql.org/message-id/5F470163.2080300%40anastigmatix.net