public inbox for [email protected]  

help / color / mirror / Atom feed

From: Chapman Flack <[email protected]>
To: Kartik Ohri <[email protected]>
Cc: [email protected]
Subject: Re: Starting build-system work (Windows/Mac users please speak up)
Date: Sun, 31 May 2020 23:23:54 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<CAASLQ4OdOma6h5Mu=hMEPyk0M4-MomYZLnhGH+2wVoL1vt_UEg@mail.gmail.com>
	<[email protected]>
	<CAASLQ4P11FFgefy_xK0Tcw3vWt1F1MNyVgK5eU=PFGvYrpZcyw@mail.gmail.com>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<CAASLQ4PAQ0PNAxJ5ad9U6o+RT2ip19FXvgoK2y1kGWaJbTZ1WQ@mail.gmail.com>
	<[email protected]>
	<CAASLQ4OXAb+_J=oK54PH5eYuXjkV9KMsoXEcp-TYaQPqxk1Xbg@mail.gmail.com>
	<[email protected]>
	<[email protected]>

On 05/31/20 12:00, Chapman Flack wrote:
>> - Messages from the JVM itself that are emitted through a 'vfprintf hook'
>>   are caught by PL/Java's hook [1] and injected into PostgreSQL's
>>   elog system at a selectable level, usually INFO. (That is probably
>>   the path being followed by the -Xcheck:jni messages, explaining
>>   why they have INFO: in front.)

Exploiting that fact, I decided to just condense out those messages (only
the ones coming from Java's own JMX classes, outside our power to fix)
right at the source, by putting a small state machine in the vfprintf hook
to recognize and not log them. That's in PR #276.

Also in that PR, changes to fix the remaining -Xcheck:jni messages that
were really coming from PL/Java. For the moment, in my environment,
with PR #275 and #276 applied, it builds and tests -Xcheck:jni clean.

That should eliminate any need for doing fancy stuff with those messages
in the CI configuration. Any new issues that crop up in development later
ought to produce a smaller volume of messages that we want to know about.

Regards,
-Chap

view thread (61+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: Starting build-system work (Windows/Mac users please speak up)
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox