Reviewing systemtap test results on Fedora rawhide

[William Cohen]

Hi,

Now that we have a systemtap RPMS on Fedora Rawhide which has Linux 6.14-rcx kernels and gcc-15 with additional checks I took a little time to look over the results to see what common themes there are in the test failures. A lot passed

                === systemtap Summary ===

# of expected passes            10717
# of unexpected failures        1144
# of unexpected successes       10
# of expected failures          707
# of unknown successes          10
# of known failures             320
# of unresolved testcases       1
# of untested testcases         805
# of unsupported tests          12

However, when compared to Fedora 41 there are additional failures. Here are some of the common failure modes.


Fixed up ctime.stp tapset to  eliminate the warnings on Fedora rawhide.  The character arrays didn't have space for the NULL terminating character.  So the following should work now:
FAIL: systemtap.base/ctime.stp
FAIL: staprunwait


There were about a dozen tests such as the gtod tests that failed becuase of a problem compiling the runtime transport layer code. They all had error error messages of the form:

spawn -ignore SIGHUP gcc /home/wcohen/systemtap_write/systemtap/testsuite/systemtap.base/gtod.c -lm -o /home/wcohen/systemtap_write/systemtap/testsuite/gtod
spawn /home/wcohen/systemtap_write/systemtap/testsuite/systemtap.base/gtod.sh /home/wcohen/systemtap_write/systemtap/testsuite/systemtap.base/gtod.stp /home/wcohen/systemtap_write/systemtap/testsuite/gtod
In file included from stap_c0a3b83307720b4f0a3dee70756eb51a_3120_src.c:577:
In function 'stapkp_init',
    inlined from 'systemtap_module_init' at stap_c0a3b83307720b4f0a3dee70756eb51a_3120_src.c:1201:8,
    inlined from '_stp_handle_start' at /home/wcohen/systemtap_write/install/share/systemtap/runtime/transport/transport.c:274:14,
    inlined from '_stp_ctl_write_cmd' at /home/wcohen/systemtap_write/install/share/systemtap/runtime/transport/control.c:83:17:
/home/wcohen/systemtap_write/install/share/systemtap/runtime/linux/kprobes.c:807:18: error: 'strcmp' of a string of length 6 and an array of size 1 evaluates to nonzero [-Werror=string-compare]
  807 |               || strcmp(skp->module, "kernel") == 0)) {
      |                  ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
make[5]: *** [/usr/src/kernels/6.14.0-0.rc1.15.fc42.x86_64/scripts/Makefile.build:207: stap_c0a3b83307720b4f0a3dee70756eb51a_3120_src.o] Error 1
make[4]: *** [/usr/src/kernels/6.14.0-0.rc1.15.fc42.x86_64/Makefile:2040: .] Error 2
make[3]: *** [Makefile:263: __sub-make] Error 2
WARNING: kbuild exited with status: 2
Pass 4: compilation failed.  [man error::pass4]

About 150 tracepoints could not be found by systemtap when compared to Fedora 41.  This might be due to the tracepoint finding code failing to compile with the additional gcc-15 checks.


A number of tests unable to find  kernel.trace("sys_enter") or kernel.trace("sys_exit")
+FAIL: systemtap.examples/general/stopwatches build
+FAIL: systemtap.examples/general/stopwatches build_bpf
+FAIL: systemtap.examples/lwtools/syscallbypid-nd build
+FAIL: systemtap.examples/process/errsnoop build
+FAIL: systemtap.examples/process/strace build
+FAIL: systemtap.examples/process/syscalls_by_pid build
+FAIL: systemtap.examples/process/syscalls_by_proc build
+FAIL: systemtap.examples/process/syscalltimes run
+FAIL: systemtap.examples/process/thread-business build
+FAIL: systemtap.examples/profiling/container_check build
+FAIL: systemtap.examples/profiling/errno build
+FAIL: systemtap.examples/profiling/syscallerrorsbypid build
+FAIL: systemtap.examples/profiling/syscalllatency build
+FAIL: systemtap.examples/profiling/syscallsbypid build
+FAIL: systemtap.examples/profiling/topsys build
+FAIL: systemtap.examples/profiling/ucalls build
+FAIL: exporter syscallsbypid 0
+FAIL: buildok/syscall_any.stp (interactive) - compile
+UNTESTED: buildok/nd_syscalls-all-probes.stp parse-semok - not semok
+UNTESTED: buildok/nd_syscalls-detailed.stp parse-semok - not semok
+UNTESTED: buildok/nd_syscalls2-detailed.stp parse-semok - not semok
+UNTESTED: buildok/syscall.stp parse-semok - not semok
+UNTESTED: buildok/tty-detailed.stp parse-semok - not semok

None of the tests passed for the tp_syscall.exp.  Looks like the tracepoint probes were not providing any output:
 Running /home/wcohen/systemtap_write/systemtap/testsuite/systemtap.syscall/tp_syscall.exp ...

-Will