From: "me at serhei dot io" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/27728] New: at_*.exp regressions (from bunsen data)
Date: Tue, 13 Apr 2021 20:49:36 +0000 [thread overview]
Message-ID: <bug-27728-6586@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=27728
Bug ID: 27728
Summary: at_*.exp regressions (from bunsen data)
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: runtime
Assignee: systemtap at sourceware dot org
Reporter: me at serhei dot io
Target Milestone: ---
Analysis of the systemtap buildbot data shows the following regressions
after e3287bd PR27044: fix lock loop for conditional probes
- breakage in at_deref.exp
FAIL: at_uderef unexpected output
after a790dc6 PR27251: support buildid probing on --x--x--x perm binaries
or ea81249 PR27273: port to linux 5.11
(exact location unclear)
- breakage in at_var_mark,at_var_mark_func,at_var_pie,at_var_timer_profile
- more breakage in at_deref.exp
FAIL: at_var_mark unexpected output
FAIL: at_var_mark_func startup (eof)
FAIL: at_var_pie
after cd7b3e0 PR27030 bpf/uconversions.stp: other sizes user_*_error()
or (MUCH more likely) d1b5548 fix symbol lookups when the first section isn't
executable
- more breakage in at_var_mark,at_var_mark_func,at_var_pie
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2021-04-13 20:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-13 20:49 me at serhei dot io [this message]
2021-04-14 18:35 ` [Bug runtime/27728] " me at serhei dot io
2021-04-14 20:06 ` me at serhei dot io
2022-05-25 15:58 ` scox at redhat dot com
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-27728-6586@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@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).