From: Mark Wielaard <mark@klomp.org>
To: builder@sourceware.org
Cc: "наб via Elfutils-devel" <elfutils-devel@sourceware.org>
Subject: Re: ☠ Buildbot (GNU Toolchain): elfutils - failed test (failure) (master)
Date: Sat, 23 Apr 2022 03:31:04 +0200 [thread overview]
Message-ID: <YmNW2POIJz9V7YZO@wildebeest.org> (raw)
In-Reply-To: <20220423011953.1D7713858430@sourceware.org>
[-- Attachment #1: Type: text/plain, Size: 1016 bytes --]
On Sat, Apr 23, 2022 at 01:19:53AM +0000, builder--- via Elfutils-devel wrote:
> A new failure has been detected on builder elfutils-debian-ppc64 while building elfutils.
>
> Full details are available at:
> https://builder.sourceware.org/buildbot/#builders/63/builds/4
>
> Build state: failed test (failure)
> Revision: 7b046b7c060acc32c00748ee66ac350f77bc6571
> Worker: debian-ppc64
> Build Reason: (unknown)
> Blamelist: наб via Elfutils-devel <elfutils-devel@sourceware.org>
>
> Steps:
> [...]
> - 7: make check ( failure )
> Logs:
> - stdio: https://builder.sourceware.org/buildbot/#builders/63/builds/4/steps/7/logs/stdio
> - test-suite.log: https://builder.sourceware.org/buildbot/#builders/63/builds/4/steps/7/logs/test-suite_log
Gah. It is run-debuginfod-webapi-concurrency.sh again with
error_count{libmicrohttpd="Server reached connection limit.
Closing inbound connection.\n"} 9
I guess 100 parallel lookups really is too much. I am going to lower
it to 64.
Cheers,
Mark
[-- Attachment #2: 0001-tests-Lower-parallel-lookups-in-run-debuginfod-webap.patch --]
[-- Type: text/x-diff, Size: 1851 bytes --]
From 318807e7f968fd70b80408e3df029c04365c47d8 Mon Sep 17 00:00:00 2001
From: Mark Wielaard <mark@klomp.org>
Date: Sat, 23 Apr 2022 03:20:17 +0200
Subject: [PATCH] tests: Lower parallel lookups in
run-debuginfod-webapi-concurrency.sh
With 100 parallel lookups we sometimes see:
Server reached connection limit. Closing inbound connection.
Lower parallel lookups to 64
Signed-off-by: Mark Wielaard <mark@klomp.org>
---
tests/ChangeLog | 4 ++++
tests/run-debuginfod-webapi-concurrency.sh | 7 ++++---
2 files changed, 8 insertions(+), 3 deletions(-)
diff --git a/tests/ChangeLog b/tests/ChangeLog
index c734b260..2286f53f 100644
--- a/tests/ChangeLog
+++ b/tests/ChangeLog
@@ -1,3 +1,7 @@
+2022-04-23 Mark Wielaard <mark@klomp.org>
+
+ * run-debuginfod-webapi-concurrency.sh: Lower parallel lookups.
+
2022-03-01 Di Chen <dichen@redhat.com>
* alldts.c (dtflags): Put DT_NULL last.
diff --git a/tests/run-debuginfod-webapi-concurrency.sh b/tests/run-debuginfod-webapi-concurrency.sh
index 402a6307..4928f6d0 100755
--- a/tests/run-debuginfod-webapi-concurrency.sh
+++ b/tests/run-debuginfod-webapi-concurrency.sh
@@ -47,12 +47,13 @@ do
wait_ready $PORT1 'thread_busy{role="scan"}' 0
# Do a bunch of lookups in parallel
- for jobs in `seq 100`; do
+ lookup_nr=64
+ for jobs in `seq $lookup_nr`; do
curl -s http://localhost:$PORT1/buildid/cee13b2ea505a7f37bd20d271c6bc7e5f8d2dfcb/debuginfo > /dev/null &
done
- # all 100 curls should succeed
- wait_ready $PORT1 'http_responses_transfer_bytes_count{code="200",type="debuginfo"}' 100
+ # all curls should succeed
+ wait_ready $PORT1 'http_responses_transfer_bytes_count{code="200",type="debuginfo"}' $lookup_nr
(sleep 5;
curl -s http://localhost:$PORT1/metrics | egrep 'error|responses';
--
2.30.2
next prev parent reply other threads:[~2022-04-23 1:31 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-23 1:19 builder
2022-04-23 1:31 ` Mark Wielaard [this message]
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 ` run-debuginfod-webapi-concurrency.sh Thomas Fitzsimmons
2022-04-24 10:22 ` run-debuginfod-webapi-concurrency.sh Mark Wielaard
-- strict thread matches above, loose matches on Subject: below --
2023-01-14 2:51 ☠ Buildbot (GNU Toolchain): elfutils - failed test (failure) (master) 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-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
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-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=YmNW2POIJz9V7YZO@wildebeest.org \
--to=mark@klomp.org \
--cc=builder@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).