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: Detecting test failures reported as warnings |
Date: | 2020-06-17 19:53:59 |
Message-ID: | 5EEA74D7.60302@anastigmatix.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pljava-dev |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Kartik Ohri | 2020-06-19 15:54:31 | Re: Starting build-system work (Windows/Mac users please speak up) |
Previous Message | Kartik Ohri | 2020-06-17 19:42:41 | Re: Detecting test failures reported as warnings |