Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jcCLh-0003xn-1l for pljava-dev@arkaria.postgresql.org; Fri, 22 May 2020 18:24:49 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jcCLe-00051d-Od for pljava-dev@arkaria.postgresql.org; Fri, 22 May 2020 18:24:46 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jcCLe-0004yD-Gg for pljava-dev@lists.postgresql.org; Fri, 22 May 2020 18:24:46 +0000 Received: from mail-ej1-x643.google.com ([2a00:1450:4864:20::643]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1jcCLb-0006sb-J0 for pljava-dev@lists.postgresql.org; Fri, 22 May 2020 18:24:45 +0000 Received: by mail-ej1-x643.google.com with SMTP id yc10so14001706ejb.12 for ; Fri, 22 May 2020 11:24:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=1m4hxQt2ofHKvidtomszYUfA4ZnbAL9/kY/kkm6C/lw=; b=rS4BNe/20V56lfM7cY5qqhcAJPa0pTFuhs/dxbfMca1yBHaBCV35Qa8q/rQ0iCzORp y8sddgUN4KDI79PYl5TQOHyWh5vNA0Xql6TY11FieG5URRXZaE+OIEpyVbe60RjWgWhw 6TsvrZdj+wHnpl+s0un2xRKymAvNSm/NNuvz6aLAOJQMWhf6VTF9zLxiqAEYVty6ktt5 UKRJ6YXah6Ln0FMg6qreANZ10f+F2qSFLOaLju7muSrpy3TA/g/9uTotJchFcmizr7sY 92TZkRUdXqitC4bA5/RljNi7LV92ZIfyfd8+V/sma+5qNtkrTnVia6X7LtIZFbPlHlG8 6tPg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=1m4hxQt2ofHKvidtomszYUfA4ZnbAL9/kY/kkm6C/lw=; b=bHXZDe1FnHXS56bvBwsBjjFROrN4fIba2K73ClDKLcJ57Z4GEzyxy3hzGJKV9VqxsY V+ATQ9Ac667i0Jz0e2hD1X3omE2X4+XW08HoQQ6G0XEcrfD1IfNodZiVFuo9Alg6VGFR WKzUcJ7TrDmtNRd+nmPdREnjYw7Lp3VzOX73YwHkLmAepT+objgqcvNoXTKZ34qPQAhc nnID2NGTPiXPeoRjejvYK02/ZHunHbTRUw2/OsWOyCqFwGQ9+3kP8DIpXWKK8sN/j+WV TvSnJtrbsI/Sl2460oh1W/j3embbUMUkkLtImdj62aOmMIf3WqPwuN8jt5YMF/tv9CTI +4jA== X-Gm-Message-State: AOAM530Kpri7csBC2qiafKSPkGfcZtxtjkMHTAOR0Q6qCg+sBRv1TB/z 5jdFK/uaoTplT3N03NJcWxvzaKWDy+eeX2mMBmJaQfqT9fU= X-Google-Smtp-Source: ABdhPJzy13qhe6woy0DiNCFd+XEJ98v6seeygNIfymxmOKtwyRDkEeBLGKSFlMpY5pjuuerHIbymLMrTByjtW0jycuM= X-Received: by 2002:a17:906:14d3:: with SMTP id y19mr9269016ejc.466.1590171881396; Fri, 22 May 2020 11:24:41 -0700 (PDT) MIME-Version: 1.0 References: <5EC17E17.7070002@anastigmatix.net> <5EC66741.4030208@anastigmatix.net> <5EC6FB8B.7080806@anastigmatix.net> In-Reply-To: <5EC6FB8B.7080806@anastigmatix.net> From: Kartik Ohri Date: Fri, 22 May 2020 23:54:29 +0530 Message-ID: Subject: Re: Starting build-system work (Windows/Mac users please speak up) To: Chapman Flack Cc: pljava-dev@lists.postgresql.org Content-Type: multipart/alternative; boundary="0000000000001f613c05a640be3a" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --0000000000001f613c05a640be3a Content-Type: text/plain; charset="UTF-8" > > I will look soon. > Please take a look at this https://travis-ci.com/github/amCap1712/pljava/builds/167810527 instead. I have added builds for both linux and macOS here. (The previous one had only macOS). #77.19 test pljava against PostgreSQL 12 built from source with the relevant flags you mentioned earlier. > I agree that a Cartesian product of PG versions and Java versions would > be more than necessary. What is important is to confirm that every > supported PG version works (built with some Java version), and every > supported Java version can be used to build (with some PG version). > > Ideally, that much would be confirmed on each supported platform. I have reduced the build matrix to the minimum builds required to meet these conditions. > > Some of the build combinations fail intermittently but work just fine > when > > ran again. It seems to be an error on Travis CI side. I am investigating > > the issue and am working to fix it. > > Thanks! > #77.8 and #77.17 illustrate this issue. In #77.8, macports is unable to install openssl which is installed properly in all of the remaining builds. #77.17 fails with some include path error due to nar-maven. #77.16 had failed with the same error. But when I ran it again without any changes, it passed the build as you can see on the page. Both #77.8 and #77.17 will pass the build if run again without any changes. I am trying to contact with the people at #macports on freenode IRC to find a solution for the issue with #77.8. For #77.17, I have seen this issue in PL/Java Github issues. The problem is I do not have to change anything to fix it. It automatically breaks and fixes itself. Can you shed some light on this one ? Sorry for sending it multiple times. I had pressed both Reply and Reply All by mistake. --0000000000001f613c05a640be3a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I will look soon.
Please take a look at thi= s=C2=A0https://travis-ci.com/github/amCap1712/pljava/buil= ds/167810527=C2=A0instead. I have added builds for both linux and macOS= here. (The previous one had only macOS). #77.19 test pljava against Postgr= eSQL 12 built from source with the relevant flags you mentioned earlier.=C2= =A0
I agree that a Cartesian product of P= G versions and Java versions would
be more than necessary. What is impor= tant is to confirm that every
supported PG version works (built with som= e Java version), and every
supported Java version can be used to build (= with some PG version).

Ideally, that much would be confirmed on each= supported platform.
I have reduced the build matri= x to the minimum builds required to meet these conditions.=C2=A0
> Some of the build combinations fail intermitte= ntly but work just fine when
> ran again. It seems to be an error on = Travis CI side. I am investigating
> the issue and am working to fix = it.

Thanks!
=C2=A0#77.8 and #77.17 illus= trate this issue. In #77.8, macports is unable to install openssl which is = installed properly in all of the remaining builds. #77.17 fails with some i= nclude path error due to nar-maven. #77.16 had failed with the same error. = But when I ran it again without any changes, it passed the build as you can= see on the page.

Both #77.8 and #77.17 will pass = the build if run again without any changes.=C2=A0I am trying to contact wit= h the people at #macports on freenode IRC to find a solution for the=C2=A0i= ssue with=C2=A0#77.8. For #77.17, I have seen this issue in PL/Java Github = issues. The problem is I do not have to change anything to fix it. It autom= atically breaks and fixes itself. Can you shed some light on this one ?

Sorry for sending it multiple times. I had pressed bo= th Reply and Reply All by mistake.
--0000000000001f613c05a640be3a--