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 1jeduR-0007sw-8N for pljava-dev@arkaria.postgresql.org; Fri, 29 May 2020 12:14:47 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jeduQ-0006RO-75 for pljava-dev@arkaria.postgresql.org; Fri, 29 May 2020 12:14: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 1jeduP-0006NE-OJ for pljava-dev@lists.postgresql.org; Fri, 29 May 2020 12:14:46 +0000 Received: from anastigmatix.net ([68.171.219.55]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jeduN-0008Lk-Hi for pljava-dev@lists.postgresql.org; Fri, 29 May 2020 12:14:44 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=anastigmatix.net; s=default; h=Content-Transfer-Encoding:Content-Type: In-Reply-To:MIME-Version:Date:Message-ID:From:Cc:References:To:Subject:Sender :Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=f5K3t5/66Yc1mqHlgQ+eIi4D//S5pG+EsVoKXgleF5I=; b=dn2eE54noMHGRVo5tWtgHDOL20 vkn+ocy0bHJrGouoNv8JaiRd8wKje1vaO68eH4z91A2KolvvrFCGB/e52A4zZnM8HSrKnBa/sCylu MpOGldd4Pv06lMQF4tnDsG/foxnk3KVYsv6rE18Nfu+4V8qh9FIGAQJ8xnrP08bcqtpYy20ThiARL 6sDk7MPG+IHhi15Wp9VqnwGDH7uNF7lPPDRLOyWuJOaOdfEgI/hP+NQ3LzhQn8s3hlDLKoXq2dcXv /vvMsrDP04orZ2uYf8uigA27bqVBGMyGUkgoizl8zkv+lGW9rg51+LGBw4vgHU65IrnwffLkQYlbA Ly+fTCpw==; Received: from [184.19.31.139] (port=50989) by bay.acenet.us with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.93) (envelope-from ) id 1jeduL-008qEK-Jt; Fri, 29 May 2020 08:14:42 -0400 Subject: Re: Starting build-system work (Windows/Mac users please speak up) To: Kartik Ohri References: <5EC17E17.7070002@anastigmatix.net> <5ECED046.3000308@anastigmatix.net> Cc: pljava-dev@lists.postgresql.org From: Chapman Flack X-Enigmail-Draft-Status: N1110 Message-ID: <5ED0FCB0.405@anastigmatix.net> Date: Fri, 29 May 2020 08:14:40 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-OutGoing-Spam-Status: No, score=-95.0 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - bay.acenet.us X-AntiAbuse: Original Domain - lists.postgresql.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - anastigmatix.net X-Get-Message-Sender-Via: bay.acenet.us: authenticated_id: chap@anastigmatix.net X-Authenticated-Sender: bay.acenet.us: chap@anastigmatix.net X-Source: X-Source-Args: X-Source-Dir: X-From-Rewrite: unmodified, already matched List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 05/29/20 06:13, Kartik Ohri wrote: > 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. I think that's the right approach. Is it possible Travis also might allow a separate file to be saved as a result of the run, so it could be mentioned in the log and inspected separately? That might be how we want to treat hs_err_pid.log files in the case of a crash, too. My sense from running with -Xcheck:jni in the past is that a lot of the messages /are/ warnings, but apparently warnings about usage in the JRE itself that we're not in a position to fix (analogously to the C compiler sign-conversion warnings that mostly pertain to code in the PostgreSQL headers, not in PL/Java). It may take some study and iteration to figure out patterns to search for in that output that will be sensitive to the most useful messages. But just getting the output saved somewhere is a good start. Regards, -Chap