From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id C006EC71153 for ; Tue, 29 Aug 2023 16:44:02 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S237500AbjH2Qnd (ORCPT ); Tue, 29 Aug 2023 12:43:33 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:35796 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S237508AbjH2Qna (ORCPT ); Tue, 29 Aug 2023 12:43:30 -0400 Received: from pb-smtp2.pobox.com (pb-smtp2.pobox.com [64.147.108.71]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 9BF4D19A for ; Tue, 29 Aug 2023 09:43:27 -0700 (PDT) Received: from pb-smtp2.pobox.com (unknown [127.0.0.1]) by pb-smtp2.pobox.com (Postfix) with ESMTP id 6C4141AEBA1; Tue, 29 Aug 2023 12:43:26 -0400 (EDT) (envelope-from junio@pobox.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=pobox.com; h=from:to:cc :subject:references:date:in-reply-to:message-id:mime-version :content-type; s=sasl; bh=0pQzjchWsbpFi/wJS6iJ8JXrSGsw+bKBOUQqjt yDgXA=; b=lZQRRlkyo84onxZ+CLLXr7CYXb7WwRmhBBwTSkB1IX9HcgudVmopm4 CZu9eJsZnkSTRGM+AIp8KICUT6vfbFBUXim719zDTA5YFBsqXPIqaUqm3vtE2bbs IcU5pBANvShirhksvqyGF/6W/QqE7jZwWtBlA1wKWHlvNS0XUlDNw= Received: from pb-smtp2.nyi.icgroup.com (unknown [127.0.0.1]) by pb-smtp2.pobox.com (Postfix) with ESMTP id 623071AEBA0; Tue, 29 Aug 2023 12:43:26 -0400 (EDT) (envelope-from junio@pobox.com) Received: from pobox.com (unknown [35.185.212.55]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pb-smtp2.pobox.com (Postfix) with ESMTPSA id CA0481AEB9F; Tue, 29 Aug 2023 12:43:25 -0400 (EDT) (envelope-from junio@pobox.com) From: Junio C Hamano To: Jeff King Cc: Taylor Blau , git@vger.kernel.org, =?utf-8?B?w4Z2?= =?utf-8?B?YXIgQXJuZmrDtnLDsA==?= Bjarmason Subject: Re: [PATCH v2 0/4] leak tests: mark remaining tests leak-free as such References: <20230829010000.GC3876652@coredump.intra.peff.net> Date: Tue, 29 Aug 2023 09:43:24 -0700 In-Reply-To: <20230829010000.GC3876652@coredump.intra.peff.net> (Jeff King's message of "Mon, 28 Aug 2023 21:00:00 -0400") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Pobox-Relay-ID: 2CA44E56-468B-11EE-9641-25B3960A682E-77302942!pb-smtp2.pobox.com Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Jeff King writes: > On Mon, Aug 28, 2023 at 06:52:52PM -0400, Taylor Blau wrote: > >> Here is a reroll of my (I guess now mine and Peff's!) series to update >> our test scripts to accurately mark which ones are leak-free. >> >> This is mostly unchanged from the previous round, modulo cleaning up the >> first (now second) patch's message, and inserting a new patch from Peff >> at the beginning to ignore noisy LSan output. > > Perhaps needless to say, but this all looks good to me. :) Thanks, both of you. These look good to me, too ;-).