From: Chapman Flack <chap@anastigmatix.net>
Subject: Re: Detecting test failures reported as warnings
To: Kartik Ohri <kartikohri13@gmail.com>
References: <5EC17E17.7070002@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>
 <CAASLQ4PuYp-y8DdQPHytAcNCmR7u_th9SYYjYNB4_VM-tB5mXA@mail.gmail.com>
Cc: pljava-dev@lists.postgresql.org
Message-ID: <5EEA74D7.60302@anastigmatix.net>
Date: Wed, 17 Jun 2020 15:53:59 -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: 
 <CAASLQ4PuYp-y8DdQPHytAcNCmR7u_th9SYYjYNB4_VM-tB5mXA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Precedence: bulk

On 06/17/20 15:42, Kartik Ohri wrote:
>> There's a lot to like about a Java and JDBC approach. It shouldn't be hard
>> to get off the ground, JDBC has a nice standard API for finding out about
>> warnings (and reading through the pgJDBC code, I believe it is implemented,
>> though I haven't done a test yet).
>>
>> Later on, as the prerequisites for migrating to TAP get accomplished,
>> that code could just be evolved to match.
>>
> As of now, setting client log level seems to work very well. Should I try
> to work out this approach or go ahead?

That sounds adequate for now. Especially if log_min_messages is still
at INFO (or could even go finer than that), and you can limit just the
client messages to warning, use that to detect success/failure, but put
the backend log into the build log.

Regards,
-Chap