public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug debuginfod/28708] run-debuginfod-webapi-concurrency.sh seems to be flaky
Date: Tue, 05 Apr 2022 14:09:01 +0000	[thread overview]
Message-ID: <bug-28708-10460-zB0LUtRTkH@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28708-10460@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=28708

--- Comment #13 from Mark Wielaard <mark at klomp dot org> ---
(In reply to Evgeny Vereshchagin from comment #12)
> FWIW with
> https://sourceware.org/git/?p=elfutils.git;a=commit;
> h=e646e363e72e06e0ed5574c929236d815ddcbbaf applied the test appears to be
> flaky on Packit on s390x:
> https://copr-be.cloud.fedoraproject.org/results/packit/evverx-elfutils-73/
> fedora-35-s390x/03942110-elfutils/builder-live.log.gz

So that log contains the feared:
error_count{libmicrohttpd="Server reached connection limit. Closing inbound
connection.\n"} 35

And sadly I have also been able to replicate that on another s390x setup even
with all the latest patches.

The thing they seem to have in common is that they are both s390x and have only
2 cores.

If I lower the -C100 to -C32 in run-debuginfod-webapi-concurrency.sh it does
seem to always pass. But with -C50 or higher is does occasionally fail (the
higher to more frequent it fails).

BTW. run-debuginfod-webapi-concurrency.sh seems stable on any other system I've
thrown it at. So it isn't exactly clear what "such a system" is? Is it s390x
specific?

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2022-04-05 14:09 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-17  1:02 [Bug debuginfod/28708] New: " evvers at ya dot ru
2021-12-17  1:25 ` [Bug debuginfod/28708] " evvers at ya dot ru
2021-12-17  1:53 ` fche at redhat dot com
2021-12-17  2:30 ` evvers at ya dot ru
2021-12-17  8:31 ` mark at klomp dot org
2021-12-17 18:48 ` fche at redhat dot com
2021-12-17 18:48 ` fche at redhat dot com
2021-12-17 18:49 ` fche at redhat dot com
2021-12-19 22:06 ` evvers at ya dot ru
2021-12-19 22:47 ` fche at redhat dot com
2021-12-20 17:17 ` mark at klomp dot org
2021-12-20 23:21 ` evvers at ya dot ru
2022-04-03  0:43 ` fche at redhat dot com
2022-04-04  2:27 ` evvers at ya dot ru
2022-04-05 14:09 ` mark at klomp dot org [this message]
2022-04-24 10:23 ` mark at klomp dot org

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=bug-28708-10460-zB0LUtRTkH@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=elfutils-devel@sourceware.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).