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/28583] FAIL run-debuginfod-response-headers.sh (exit status: 1) with 0.186
Date: Thu, 11 Nov 2021 13:24:09 +0000	[thread overview]
Message-ID: <bug-28583-10460-OQhr9a39F0@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28583-10460@http.sourceware.org/bugzilla/>

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

Mark Wielaard <mark at klomp dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mark at klomp dot org

--- Comment #1 from Mark Wielaard <mark at klomp dot org> ---
I don't know why yet, but the problem is:

[ 1937s] + kill -USR1 21045
[ 1937s] + wait_ready 9500 'thread_work_total{role="traverse"}' 2
[ 1937s] + port=9500
[ 1937s] + what='thread_work_total{role="traverse"}'
[ 1937s] + value=2
[ 1937s] + timeout=20
[ 1937s] + echo 'Wait 20 seconds on 9500 for metric
thread_work_total{role="traverse"} to change to 2'
[ 1937s] Wait 20 seconds on 9500 for metric thread_work_total{role="traverse"}
to change to 2
[ 1937s] + '[' 20 -gt 0 ']'
[ 1937s] ++ curl -s http://127.0.0.1:9500/metrics
[ 1937s] ++ awk '{print $NF}'
[ 1937s] ++ grep 'thread_work_total{role="traverse"}'
[ 1937s] + mvalue=3
[ 1937s] + '[' -z 3 ']'
[ 1937s] + echo 'metric thread_work_total{role="traverse"}: 3'
[ 1937s] metric thread_work_total{role="traverse"}: 3
[...]
[ 1937s] + echo 'metric thread_work_total{role="traverse"}: 3'
[ 1937s] metric thread_work_total{role="traverse"}: 3
[ 1937s] + '[' 3 -eq 2 ']'
[ 1937s] + sleep 0.5
[ 1937s] + (( timeout-- ))
[ 1937s] + '[' 0 -gt 0 ']'
[ 1937s] + '[' 0 -eq 0 ']'
[ 1937s] + echo 'metric thread_work_total{role="traverse"} never changed to 2
on port 9500'
[ 1937s] metric thread_work_total{role="traverse"} never changed to 2 on port
9500
[ 1937s] + err
[ 1937s] + trap - ERR
[ 1937s] + echo ERROR REPORTS

We are testing whether the SIGUSR1 signal triggers a new  scan. And so we are
waiting for 'thread_work_total{role="traverse"}' to change to 2, but it is
already 3... ?

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

  reply	other threads:[~2021-11-11 13:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-11 12:01 [Bug debuginfod/28583] New: " mliska at suse dot cz
2021-11-11 13:24 ` mark at klomp dot org [this message]
2021-11-11 14:50 ` [Bug debuginfod/28583] " mliska at suse dot cz
2022-04-24 18:56 ` mark at klomp dot org
2022-04-25  7:36 ` mliska at suse dot cz

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-28583-10460-OQhr9a39F0@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).