From: "evvers at ya dot ru" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug general/29180] New: run-debuginfod-fd-prefetch-caches.sh seems to fail on Ubuntu Focal when elfutils is built with --enable-gcov
Date: Wed, 25 May 2022 15:27:45 +0000 [thread overview]
Message-ID: <bug-29180-10460@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=29180
Bug ID: 29180
Summary: run-debuginfod-fd-prefetch-caches.sh seems to fail on
Ubuntu Focal when elfutils is built with --enable-gcov
Product: elfutils
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: general
Assignee: unassigned at sourceware dot org
Reporter: evvers at ya dot ru
CC: elfutils-devel at sourceware dot org
Target Milestone: ---
As far as I understand the most relevant part is
```
2022-05-25T01:03:03.3909087Z traversed_total{type="directory"} 10
2022-05-25T01:03:03.3909315Z traversed_total{type="file"} 32
2022-05-25T01:03:03.3909744Z traversed_total{type="other"} 10 =~
fdcache_prefetch_count ([0-9])+ ]]
2022-05-25T01:03:03.3910032Z + [[ 1 -ne 0 ]]
2022-05-25T01:03:03.3910197Z + err
2022-05-25T01:03:03.3910419Z + trap - ERR
2022-05-25T01:03:03.3910612Z + echo ERROR REPORTS
2022-05-25T01:03:03.3910799Z ERROR REPORTS
```
The full log can be found at
https://gist.github.com/evverx/362aa02f6ec8414d5a4f5bce59fbcd47
Since the test seems to pass on Ubuntu Jammy and Fedora Rawhide I "fixed" it by
skipping the test in https://github.com/evverx/elfutils/pull/85 and not
including it in the coverage report built on Ubuntu Focal.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2022-05-25 15:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-25 15:27 evvers at ya dot ru [this message]
2022-05-27 11:21 ` [Bug general/29180] " mark at klomp dot org
2022-05-27 15:37 ` evvers at ya dot ru
2022-06-06 11: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-29180-10460@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).