From: William Cohen <wcohen@redhat.com>
To: systemtap@sourceware.org
Subject: Triage of systemtap examples test results
Date: Thu, 7 Apr 2022 16:23:22 -0400 [thread overview]
Message-ID: <953bd7b8-362b-0c01-a694-f6646e2b1ce1@redhat.com> (raw)
Hi,
I have been reviewing the systemtap examples testsuite results on
various distro to see what issues pop up and what can be done to fix
them. Typically the examples fail because changes in data and code
structure and the compiler more agressively.
On x86_64 Rawhide:
Examples tweaked this week to work with newer kernel/app software:
FAIL: systemtap.examples/io/ttyspy build
FAIL: systemtap.examples/process/threadstacks build
=== systemtap Summary ===
# of expected passes 375
# of unexpected failures 16
# of untested testcases 29
runtest completed at Wed Apr 6 16:34:36 2022
Examples failed due to issue with struct bitfield member access (PR29037):
FAIL: systemtap.examples/network/tcp_trace build
FAIL: systemtap.examples/network/tcpdumplike build
FAIL: systemtap.examples/process/schedtimes build
Example fails because systemtap can't find nsproxy in task_struct, but pahole shows that the task_struct has nsproxy
FAIL: systemtap.examples/process/futexes2 build
Examples failed due to function return probe on inlined function:
FAIL: systemtap.examples/io/eatmydata build
FAIL: systemtap.examples/memory/cachestat build
FAIL: systemtap.examples/memory/cachestat build_bpf
FAIL: systemtap.examples/process/sleeptime build (looks to fallback and use tracepoints for some syscall monitoring)
Examples failed due to variable not available at probe point:
FAIL: systemtap.examples/general/badname build
FAIL: systemtap.examples/network/tcpipstat build
Examples failed due to probe point not available:
FAIL: systemtap.examples/lwtools/fslatency-nd build
FAIL: systemtap.examples/lwtools/fsslower-nd build
Examples failed due to changes in data structures:
FAIL: systemtap.examples/io/iostat-scsi build
Example failed due to glibc moving around pthread related functions:
FAIL: systemtap.examples/process/mutex-contention build
Example failed due to kernel_getsockopt() being removed from kernel and fcheck_files() function changed name:
FAIL: systemtap.examples/process/pfiles build
Examples failed due to not finding kvm_exit trace argument $reason:
FAIL: systemtap.examples/virtualization/kvm_service_time build
On x86_64 RHEL8:
Examples tweaked this week to work with newer kernel/app software:
FAIL: systemtap.examples/process/threadstacks build
=== systemtap Summary ===
# of expected passes 414
# of unexpected failures 8
# of untested testcases 10
Seems to be some unhandled signal 5 (Trace/breakpoint trap):
FAIL: systemtap.examples/apps/php-trace run
FAIL: systemtap.examples/apps/php-trace run_dyninst
child exits abnormally
FAIL: systemtap.examples/general/badname run
ERROR: user string copy fault -14 at 0x59 [man error::fault] near identifier 'user_string_n' at /usr/share/systemtap/tapset/uconversions.stp:128:10
FAIL: systemtap.examples/general/py2example build
Unable to access target variable at address:
FAIL: systemtap.examples/network/tcpipstat build
unresolved struct nsproxy in task_struct, looks like nsproxy is actually defined in struct (need to investigate more as failed on rawhide also)
FAIL: systemtap.examples/process/futexes2 build
Running on virtual machine so likely to fail because PMU not available:
FAIL: systemtap.examples/profiling/perf run
Unable to get SDT args:
FAIL: systemtap.examples/virtualization/qemu_count build
reply other threads:[~2022-04-07 20:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=953bd7b8-362b-0c01-a694-f6646e2b1ce1@redhat.com \
--to=wcohen@redhat.com \
--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).