From: Mark Wielaard <mark@klomp.org>
To: Noah Sanci <nsanci@redhat.com>
Cc: elfutils-devel@sourceware.org
Subject: Re: [Bug debuginfod/28577] Make run-...-fd-prefetch-caches.sh test something
Date: Fri, 03 Jun 2022 18:22:20 +0200 [thread overview]
Message-ID: <106eca2a41d639a34ff215e4b9d6650cba03806c.camel@klomp.org> (raw)
In-Reply-To: <bbf5012c940ed6f95ca2c129b40b5da64266e73c.camel@klomp.org>
Hi,
On Fri, 2022-06-03 at 17:02 +0200, Mark Wielaard wrote:
> On Fri, 2022-06-03 at 10:51 -0400, Noah Sanci wrote:
> > Nothing immediately jumps out, would you mind sending the entire
> > log?
>
> Attached.
And Noah figured it out. The machine where it failed has /tmp 92% full
and the default mintmp is 25%. Which triggers an fdcache emergency
flush. So with this it PASSes everywhere:
diff --git a/tests/run-debuginfod-fd-prefetch-caches.sh b/tests/run-debuginfod-fd-prefetch-caches.sh
index 8778d3a2..a538cd48 100755
--- a/tests/run-debuginfod-fd-prefetch-caches.sh
+++ b/tests/run-debuginfod-fd-prefetch-caches.sh
@@ -50,10 +50,12 @@ export DEBUGINFOD_CACHE_PATH=${PWD}/.client_cache
rm -rf $DEBUGINFOD_CACHE_PATH
rm -rf $DB
# Testing prefetch fd maximum (Set mb maximums to be beyond consideration)
+# Set --fdcache-mintmp=0 so we don't accidentially trigger an fdcache
+# emergency flush for filling tmpdir
env LD_LIBRARY_PATH=$ldpath DEBUGINFOD_URLS= ${abs_builddir}/../debuginfod/debuginfod $VERBOSE -p $PORT1 -d $DB \
--fdcache-fds=$FDCACHE_FDS --fdcache-prefetch-fds=$PREFETCH_FDS -vvvvv -g 0 -t 0 \
-Z .tar.bz2=bzcat Z --fdcache-mbs=100 --fdcache-prefetch-mbs=100 \
- --fdcache-prefetch=$PREFETCH > vlog$PORT1 2>&1 &
+ --fdcache-mintmp=0 --fdcache-prefetch=$PREFETCH > vlog$PORT1 2>&1 &
PID1=$!
tempfiles vlog$PORT1
errfiles vlog$PORT1
Pushed with that change.
Thanks,
Mark
prev parent reply other threads:[~2022-06-03 16:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-25 18:44 Noah Sanci
2022-05-27 16:20 ` Mark Wielaard
[not found] ` <CAJXA7qiYfeEpr5pHY5xPWcmnMoA1csnBvDnAHBoTubTVyBz+4g@mail.gmail.com>
2022-05-30 15:36 ` Mark Wielaard
2022-06-03 14:49 ` Mark Wielaard
[not found] ` <CAJXA7qjnhkwRaMWv2C7xnG+ruWFVsPgrvufDG94NUQe2Z067nA@mail.gmail.com>
2022-06-03 15:02 ` Mark Wielaard
2022-06-03 16:22 ` Mark Wielaard [this message]
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=106eca2a41d639a34ff215e4b9d6650cba03806c.camel@klomp.org \
--to=mark@klomp.org \
--cc=elfutils-devel@sourceware.org \
--cc=nsanci@redhat.com \
/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).