From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug debuginfod/28708] run-debuginfod-webapi-concurrency.sh seems to be flaky
Date: Fri, 17 Dec 2021 01:53:33 +0000 [thread overview]
Message-ID: <bug-28708-10460-ZVYRTvd0ss@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28708-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=28708
Frank Ch. Eigler <fche at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2021-12-17
CC| |fche at redhat dot com
Ever confirmed|0 |1
Status|UNCONFIRMED |NEW
--- Comment #2 from Frank Ch. Eigler <fche at redhat dot com> ---
Thanks for the report. The logs indicate some unexplained glitch within
libmicrohttpd (rejecting connections for no explained reason). Maybe the
builder is somehow strangely resource constrained? We could make the test less
assertive about 100% success of all those parallel curl jobs.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-12-17 1:53 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 [this message]
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
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-ZVYRTvd0ss@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).