From owner-freebsd-ports@freebsd.org Fri May 6 00:10:26 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5F205B2F90F for ; Fri, 6 May 2016 00:10:26 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-io0-x22a.google.com (mail-io0-x22a.google.com [IPv6:2607:f8b0:4001:c06::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2A12B1771; Fri, 6 May 2016 00:10:26 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by mail-io0-x22a.google.com with SMTP id 190so100689086iow.1; Thu, 05 May 2016 17:10:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc; bh=3ZkqkaawLPnrx7gBYwdmYM94PVZi8Ov3PqIcGbMy/pU=; b=Ptcz8MxA/N0B+3VrGffeccZuky7yDFbTzKVga0zTeovXz4eZdqnfjhMhzi3DTkerj3 Ea0gmc6QywU6m2TrW+88GfmNVqvqLDKMezRa3P86yy994i4/WCgZrAaNsWFkN4hd30l+ 2ADVVO2bWwkOsBEq1MjbWsEGvBj2wNKvaxaF7NNntXPwrrF7MsdU2nTKA/PNJ9oqUcqv JyaMmTdKp8Ggg6SacoKWQtudAcdJzBp+HS/s91rGScON8LEu/K45f3GUAqKASVxdriH+ VNFaET4mGlmmZbpUNNPDuxnAXc6OWna1cUBH9e/yF+hWykOFrV9tg9+WGpHlO6vhcrwz ExZw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc; bh=3ZkqkaawLPnrx7gBYwdmYM94PVZi8Ov3PqIcGbMy/pU=; b=GVS1dvQy6nldM4AqK7LmnF43jFyBYNsDZPjiT5XE/JOC0vFPjUEbuVJk43DKghttW0 K2wVsk0GRIVMDCQJyjRYAcRu+gOq41Y1lHVRECZ0bseXAaFWbg2mJ2M2CxN29cb46kF4 6mQBuJrTBtwZ76+u4x9fJrtCav2M40IyRrSHuHK8ckCT8X/2d5sGuqMlQNrW9TiE7brW 7z9wWab0Ksl1e20Or6fgiVQVZDe/77R3hWoPlIAR2ChenNBAStF1ES2ftSlrGCss6h9l fnlukujyEsXX1gizicMEU5S0t9iLhXBtPT6J2YhIZbg8ok+5dR4nUQhyfJDjn/JCeIiu wHVw== X-Gm-Message-State: AOPr4FVuTEOuK5A7SPTRgtVIjZIWYOD93hJcozMciqhEj7nkIPfniZrcHRrurUCqmHs8DxGRVYLMTm8gmF/jUw== MIME-Version: 1.0 X-Received: by 10.107.47.37 with SMTP id j37mr19829024ioo.168.1462493425381; Thu, 05 May 2016 17:10:25 -0700 (PDT) Sender: kob6558@gmail.com Received: by 10.79.20.70 with HTTP; Thu, 5 May 2016 17:10:25 -0700 (PDT) In-Reply-To: <201605052116.u45LGTXj055344@gw.catspoiler.org> References: <20160505133206.GB7010@home.opsec.eu> <201605052116.u45LGTXj055344@gw.catspoiler.org> Date: Thu, 5 May 2016 17:10:25 -0700 X-Google-Sender-Auth: n3MKc9ZHdWzN3tNCe1Dpbldim8k Message-ID: Subject: Re: PRs ready for commit From: Kevin Oberman To: Don Lewis Cc: Kurt Jaeger , FreeBSD Ports ML , bradleythughes@fastmail.fm Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 May 2016 00:10:26 -0000 On Thu, May 5, 2016 at 2:16 PM, Don Lewis wrote: > On 5 May, Kurt Jaeger wrote: > > Hi! > > > > One thing: There are issues with buildlogs attached to PR due > > to them blowing up the database of bugzilla. If all is fine, > > it's OK to just list the architectures tested. Second best > > is putting broken buildlogs on some external site and put the link > > in the PR. Third is adding broken buildlogs as attachment 8-} > > > > Yes, I know, disk space is infinite, but this is real life 8-) > > For broken builds, I prefer to just include the part of the build log > showing the error in the comment. If someone thinks that there is still > some info necessary for debug that is missing, I can extract it from the > log and add it as another comment. That way the info is easy to access > and permanently part of the PR. > > _______________________________________________ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" > I suggest that it should be the end of the build log with the build done with "MAKE_JOBS_UNSAFE" defined so the error is likely to actually be at the end of the log. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683