From: Mark Wielaard <mark@klomp.org>
To: Noah Sanci <nsanci@redhat.com>, elfutils-devel@sourceware.org
Subject: Re: debuginfod: Query debuginfod servers before printing response
Date: Fri, 17 Sep 2021 17:06:03 +0200 [thread overview]
Message-ID: <49932c2202b51969a8ee36648494eb0fa9e73dee.camel@klomp.org> (raw)
In-Reply-To: <CAJXA7qgr7uafdVKN+ArV6CvFqU41hu9PsFfA9kzgQ=K9+hZ+xw@mail.gmail.com>
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
next prev parent reply other threads:[~2021-09-17 15:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-17 14:55 Noah Sanci
2021-09-17 15:06 ` Mark Wielaard [this message]
2021-09-17 17:38 ` Noah Sanci
2021-09-17 17:49 ` Mark Wielaard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49932c2202b51969a8ee36648494eb0fa9e73dee.camel@klomp.org \
--to=mark@klomp.org \
--cc=elfutils-devel@sourceware.org \
--cc=nsanci@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).