From owner-svn-ports-all@freebsd.org Sat Feb 8 08:05:24 2020 Return-Path: Delivered-To: svn-ports-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 8319023BA39; Sat, 8 Feb 2020 08:05:24 +0000 (UTC) (envelope-from danfe@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 48F4Tw2w0Vz4XKZ; Sat, 8 Feb 2020 08:05:24 +0000 (UTC) (envelope-from danfe@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 1033) id A29E96D5D; Sat, 8 Feb 2020 08:05:23 +0000 (UTC) Date: Sat, 8 Feb 2020 08:05:23 +0000 From: Alexey Dokuchaev To: Li-Wen Hsu Cc: ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: Re: svn commit: r525491 - head/security/nss Message-ID: <20200208080523.GA22496@FreeBSD.org> References: <202002071700.017H0AUF027444@repo.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <202002071700.017H0AUF027444@repo.freebsd.org> X-BeenThere: svn-ports-all@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: SVN commit messages for the ports tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Feb 2020 08:05:24 -0000 On Fri, Feb 07, 2020 at 05:00:10PM +0000, Li-Wen Hsu wrote: > New Revision: 525491 > URL: https://svnweb.freebsd.org/changeset/ports/525491 > > Log: > Put MAKE_JOBS_UNSAFE=yes back, there is report it still fails It would be helpful to whoever wants to address the problem in the future to include a short excerpt of the failure build log with a commit like this one. Otherwise someone may remove this knob again like you just did, having no way to check what was broken and how and whether it was fixed. Ideally, when removing MAKE_JOBS_UNSAFE knob, it should go with an explanation of how it was fixed and/or upstream commit that had fixed the problem. ./danfe