From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gnu.wildebeest.org (wildebeest.demon.nl [212.238.236.112]) by sourceware.org (Postfix) with ESMTPS id 3C35C3858D29 for ; Fri, 17 Sep 2021 15:06:05 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 3C35C3858D29 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 tarox.wildebeest.org (83-87-18-245.cable.dynamic.v4.ziggo.nl [83.87.18.245]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by gnu.wildebeest.org (Postfix) with ESMTPSA id 2E8293000648; Fri, 17 Sep 2021 17:06:03 +0200 (CEST) Received: by tarox.wildebeest.org (Postfix, from userid 1000) id 4B153404AC67; Fri, 17 Sep 2021 17:06:03 +0200 (CEST) Message-ID: <49932c2202b51969a8ee36648494eb0fa9e73dee.camel@klomp.org> Subject: Re: debuginfod: Query debuginfod servers before printing response From: Mark Wielaard To: Noah Sanci , elfutils-devel@sourceware.org Date: Fri, 17 Sep 2021 17:06:03 +0200 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Evolution 3.28.5 (3.28.5-10.el7) Mime-Version: 1.0 X-Spam-Status: No, score=-4.0 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: elfutils-devel@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Elfutils-devel mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Sep 2021 15:06:08 -0000 Hi Noah, On Fri, 2021-09-17 at 10:55 -0400, Noah Sanci via Elfutils-devel wrote: > While checking PR27277 on some buildbots, greping would fail in > run-debuginfod-response-headers.sh. This was because querying the > debuginfod server occurs after checking if the response headers had > arrived, leaving the possibility to leave the querying loop before > outputting the headers which caused the grep failure. Querying now > occurs before checking if response headers have arrived, so that they > will certainly be printed and grep will find them. Thanks for finding this issue. Please push. Cheers, Mark