public inbox for
 help / color / mirror / Atom feed
* Triage of systemtap examples test results
@ 2022-04-07 20:23 William Cohen
  0 siblings, 0 replies; only message in thread
From: William Cohen @ 2022-04-07 20:23 UTC (permalink / raw)
  To: systemtap


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

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2022-04-07 20:23 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-04-07 20:23 Triage of systemtap examples test results William Cohen

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).