Re: Detecting test failures reported as warnings

From: Kartik Ohri <kartikohri13(at)gmail(dot)com>
To: Chapman Flack <chap(at)anastigmatix(dot)net>
Cc: pljava-dev(at)lists(dot)postgresql(dot)org
Subject: Re: Detecting test failures reported as warnings
Date: 2020-06-17 19:42:41
Message-ID: CAASLQ4PuYp-y8DdQPHytAcNCmR7u_th9SYYjYNB4_VM-tB5mXA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pljava-dev

>
> 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?

In response to

Responses

Browse pljava-dev by date

  From Date Subject
Next Message Chapman Flack 2020-06-17 19:53:59 Re: Detecting test failures reported as warnings
Previous Message Chapman Flack 2020-06-17 19:33:12 Re: Nashorn JavaScript removal coming in Java 15