From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gnu.wildebeest.org (gnu.wildebeest.org [45.83.234.184]) by sourceware.org (Postfix) with ESMTPS id 45EA9382BC16 for ; Wed, 26 Jan 2022 19:23:09 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 45EA9382BC16 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=klomp.org Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=klomp.org Received: from reform (deer0x12.wildebeest.org [172.31.17.148]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gnu.wildebeest.org (Postfix) with ESMTPSA id 75AC2302FB94; Wed, 26 Jan 2022 20:23:07 +0100 (CET) Received: by reform (Postfix, from userid 1000) id 0136C2E80784; Wed, 26 Jan 2022 20:23:06 +0100 (CET) Date: Wed, 26 Jan 2022 20:23:06 +0100 From: Mark Wielaard To: Joseph Myers Cc: alexandra.khirnova@gmail.com, libc-alpha@sourceware.org, Alexandra =?iso-8859-1?Q?H=E1jkov=E1?= Subject: Re: [PATCH] Add valgrind smoke test Message-ID: References: <20211206144043.858697-1-ahajkova@redhat.com> <20220112171539.3205267-1-ahajkova@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spam-Status: No, score=-3.7 required=5.0 tests=BAYES_00, JMQ_SPF_NEUTRAL, KAM_DMARC_STATUS, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=no autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: libc-alpha@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Libc-alpha mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Jan 2022 19:23:10 -0000 On Wed, Jan 26, 2022 at 06:40:10PM +0000, Joseph Myers wrote: > On Wed, 26 Jan 2022, Mark Wielaard wrote: > > > If your analysis is correct then the attached patch should solve the > > issue. Could you try that out? > > I confirm that this fixes the problem. Great. I did a local make && make check and tst-valgrind-smoke.out is still generated and the testcase still PASSes locally. Can I push the patch as is to master, or are we that close to a release that a release manager needs to ack the patch first? Thanks, Mark