From: Thomas Fitzsimmons <fitzsim@fitzsim.org>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: Mark Wielaard <mark@klomp.org>, elfutils-devel@sourceware.org
Subject: Re: run-debuginfod-webapi-concurrency.sh
Date: Sat, 23 Apr 2022 22:56:01 -0400 [thread overview]
Message-ID: <m3h76jfav2.fsf@fitzsim.org> (raw)
In-Reply-To: <20220423214525.GJ23969@redhat.com> (Frank Ch. Eigler's message of "Sat, 23 Apr 2022 17:45:25 -0400")
Hi,
"Frank Ch. Eigler" <fche@redhat.com> writes:
>> But there is another way to prevent the "Server reached connection
>> limit. Closing inbound connection." Pass the MHD_USE_ITC flag to
>> MHD_start_daemon:
>
> Yeah, that looked promising to me too. When I was last working on
> this, that would have been my next thing to try. I can't think of
> a relevant downside, so let's try it. (Add a #ifdef guard around
> that macro, for older libmicrohttpd, like rhel7 methinks.)
On debian-ppc64, with and without the MHD_USE_ITC patch, I ran the test
20 times in a shell loop. With MHD_USE_ITC, I got 20 passes, without
it, 9 passes and 11 failures.
With the patch applied, a full "make check" succeeded.
Thomas
next prev parent reply other threads:[~2022-04-24 2:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-23 1:19 ☠ Buildbot (GNU Toolchain): elfutils - failed test (failure) (master) builder
2022-04-23 1:31 ` Mark Wielaard
2022-04-23 20:19 ` run-debuginfod-webapi-concurrency.sh (Was: ☠ Buildbot (GNU Toolchain): elfutils - failed test (failure)) (master) Mark Wielaard
2022-04-23 21:45 ` Frank Ch. Eigler
2022-04-24 2:56 ` Thomas Fitzsimmons [this message]
2022-04-24 10:22 ` run-debuginfod-webapi-concurrency.sh Mark Wielaard
[not found] <m31qxoh1yi.fsf@fitzsim.org>
[not found] ` <YmPpq4OAsbrRKPB5@wildebeest.org>
2022-04-23 15:00 ` run-debuginfod-webapi-concurrency.sh Frank Ch. Eigler
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=m3h76jfav2.fsf@fitzsim.org \
--to=fitzsim@fitzsim.org \
--cc=elfutils-devel@sourceware.org \
--cc=fche@redhat.com \
--cc=mark@klomp.org \
/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).