From: "Frank Ch. Eigler" <fche@redhat.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: Mark Wielaard <mark@klomp.org>,
Yonggang Luo <luoyonggang@gmail.com>,
elfutils-devel@sourceware.org
Subject: Re: ☠ Buildbot (GNU Toolchain): elfutils - failed test (failure) (master)
Date: Mon, 17 Oct 2022 10:09:48 -0400 [thread overview]
Message-ID: <20221017140948.GB8857@redhat.com> (raw)
In-Reply-To: <20221017110242.GA8857@redhat.com>
Hi -
> > Fatal error in GNU libmicrohttpd daemon.c:3831: Failed to remove FD
> > from epoll set.
> > Very odd. I don't have any hypothesis for why these are occuring.
>
> I believe this is an intermittent libmicrohttpd bug. :-(
Pushing this patch as obvious ... and will try to track this one down
more urgently.
commit 4cc429d2761846967678fb8cf5868d311d1f7862 (HEAD -> master)
Author: Frank Ch. Eigler <fche@redhat.com>
Date: Mon Oct 17 10:07:39 2022 -0400
debuginfod: report libmicrohttpd version on startup
To assist troubleshooting with intermittent bugs.
Signed-off-by: Frank Ch. Eigler <fche@redhat.com>
diff --git a/debuginfod/ChangeLog b/debuginfod/ChangeLog
index 8fb65133f3e1..59d50df1fc8a 100644
--- a/debuginfod/ChangeLog
+++ b/debuginfod/ChangeLog
@@ -1,3 +1,7 @@
+2022-10-17 Frank Ch. Eigler <fche@redhat.com>
+
+ * debuginfod.cxx (main): Report libmicrohttpd version.
+
2022-09-28 Aaron Merey <amerey@redhat.com>
* debuginfod-client.c (debuginfod_query_server): Switch sign of some
diff --git a/debuginfod/debuginfod.cxx b/debuginfod/debuginfod.cxx
index 8e7ee4997e0a..9dc4836bbe12 100644
--- a/debuginfod/debuginfod.cxx
+++ b/debuginfod/debuginfod.cxx
@@ -3956,6 +3956,8 @@ main (int argc, char *argv[])
}
}
+ obatched(clog) << "libmicrohttpd version " << MHD_get_version() << endl;
+
/* If '-C' wasn't given or was given with no arg, pick a reasonable default
for the number of worker threads. */
if (connection_pool == 0)
next prev parent reply other threads:[~2022-10-17 14:09 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-17 9:08 builder
2022-10-17 10:26 ` Mark Wielaard
2022-10-17 11:02 ` Frank Ch. Eigler
2022-10-17 14:09 ` Frank Ch. Eigler [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-01-14 2:51 builder
2022-12-21 18:22 builder
2022-12-19 23:56 builder
2022-12-12 14:31 builder
2022-11-28 13:30 builder
2022-11-04 22:29 builder
2022-11-03 15:27 builder
2022-11-02 13:39 builder
2022-11-02 14:19 ` Mark Wielaard
2022-11-02 1:15 builder
2022-11-02 12:06 ` Mark Wielaard
2022-11-01 21:28 builder
2022-10-31 13:51 builder
2022-10-27 19:25 builder
2022-10-17 14:59 builder
2022-10-16 21:02 builder
2022-10-16 15:47 builder
2022-10-16 16:26 ` Mark Wielaard
2022-10-13 16:51 builder
2022-09-14 19:36 builder
2022-07-31 23:54 builder
2022-08-01 0:09 ` Mark Wielaard
2022-08-01 9:13 ` Mark Wielaard
2022-05-28 9:15 builder
2022-05-28 9:35 ` Mark Wielaard
2022-05-28 9:43 ` Mark Wielaard
2022-06-02 15:44 ` Mark Wielaard
2022-05-27 16:02 builder
2022-05-27 22:30 ` Mark Wielaard
2022-05-28 2:34 ` Frank Ch. Eigler
2022-05-28 9:04 ` Mark Wielaard
2022-05-14 15:34 builder
2022-05-14 16:40 ` Mark Wielaard
2022-05-14 14:42 builder
2022-05-04 15:34 builder
2022-05-04 17:44 ` Mark Wielaard
2022-04-23 13:19 builder
2022-04-23 1:19 builder
2022-04-23 1:31 ` Mark Wielaard
2022-04-19 9:05 builder
2022-04-19 9:28 ` 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=20221017140948.GB8857@redhat.com \
--to=fche@redhat.com \
--cc=elfutils-devel@sourceware.org \
--cc=luoyonggang@gmail.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).