MIME-Version: 1.0
References: <5EC17E17.7070002@anastigmatix.net>
 <CAASLQ4OdOma6h5Mu=hMEPyk0M4-MomYZLnhGH+2wVoL1vt_UEg@mail.gmail.com>
 <5ECED046.3000308@anastigmatix.net>
In-Reply-To: <5ECED046.3000308@anastigmatix.net>
From: Kartik Ohri <kartikohri13@gmail.com>
Date: Fri, 29 May 2020 15:43:53 +0530
Message-ID: 
 <CAASLQ4P11FFgefy_xK0Tcw3vWt1F1MNyVgK5eU=PFGvYrpZcyw@mail.gmail.com>
Subject: Re: Starting build-system work (Windows/Mac users please speak up)
To: Chapman Flack <chap@anastigmatix.net>
Cc: pljava-dev@lists.postgresql.org
Content-Type: multipart/alternative; boundary="0000000000007d533e05a6c6b424"
Precedence: bulk

--0000000000007d533e05a6c6b424
Content-Type: text/plain; charset="UTF-8"

>
> I don't think it will make much difference ... maybe start with a build
> that's against the latest supported PG. Once things are going, maybe we
> can get a better sense of which outputs from -Xcheck:jni are innocuous
> and which ones really deserve attention, and write a filter that cuts
> down that volume effectively, then it might be desirable to add the option
> to more of the builds.
>
I tested a build these -enableassertions and -Xcheck:jni flag enabled. The
output is at least over 30000 lines and causes the build to terminate
unsuccessfully as the it exceeds maximum supported log length. Please see
https://travis-ci.com/github/amCap1712/pljava/jobs/341362356 . I tried to
find but I couldn't find a flag to limit its log level to warning or above.
I have an idea to try to direct the output to a separate file instead to
standard output. And then search, the file for warnings and output those to
the standard log. There may be a few caveats I need to iron out but I think
it might work. Let me know your views on this.

--0000000000007d533e05a6c6b424
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_quote"><blockquote class=3D"gmail_quot=
e" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204)=
;padding-left:1ex">I don&#39;t think it will make much difference ... maybe=
 start with a build<br>
that&#39;s against the latest supported PG. Once things are going, maybe we=
<br>
can get a better sense of which outputs from -Xcheck:jni are innocuous<br>
and which ones really deserve attention, and write a filter that cuts<br>
down that volume effectively, then it might be desirable to add the option<=
br>
to more of the builds.<br></blockquote><div>I tested a build these -enablea=
ssertions and -Xcheck:jni flag enabled. The output is at least over 30000 l=
ines and causes the build to terminate unsuccessfully as the it exceeds max=
imum supported log length. Please see=C2=A0<a href=3D"https://travis-ci.com=
/github/amCap1712/pljava/jobs/341362356">https://travis-ci.com/github/amCap=
1712/pljava/jobs/341362356</a>=C2=A0. I tried to find but I=C2=A0couldn&#39=
;t find a flag to limit its log level to warning or above. I have an idea t=
o try to direct the output to a separate file instead to standard output. A=
nd then search, the file for warnings and output those to the standard log.=
 There may be a few caveats I need to iron out but I think it might work. L=
et me know your views on this.<br></div></div></div>

--0000000000007d533e05a6c6b424--