[Bug runtime/31117] transport failures

["wcohen at redhat dot com" <sourceware-bugzilla@sourceware.org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=31117

--- Comment #16 from William Cohen <wcohen at redhat dot com> ---
The test results are much improved after the fix for padding the end of the
small sub-buffer and writing the new packet in a new sub-buffer.  There are 
some RHEL8 and RHEL9 tests that appear to create a great amount of data and
warnings about transport failures are triggered (pr14546 and
systemtap.examples/general/callgraph in RHEL8,
systemtap.examples/profiling/sched_switch run in RHEL9).  The main place that
transport failures are still observed are the syscall tests.

f39
FAIL: 64-bit setitimer nd_syscall
FAIL: 32-bit sysctl nd_syscall
FAIL: 64-bit prctl syscall
FAIL: 32-bit aio syscall
FAIL: 32-bit prctl syscall

rawhide
FAIL: 32-bit arch_prctl nd_syscall
FAIL: 32-bit membarrier nd_syscall
FAIL: 32-bit arch_prctl syscall
FAIL: 32-bit exit_group syscall
FAIL: 32-bit modify_ldt syscall
FAIL: 32-bit openclose syscall
FAIL: 32-bit socketpair syscall

rhel8
FAIL: 32-bit memfd_create tp_syscall

rhel9
FAIL: 64-bit connect nd_syscall
FAIL: 64-bit readv nd_syscall
FAIL: 64-bit thread_area nd_syscall
FAIL: 32-bit syslog nd_syscall
FAIL: 64-bit fadvise64 syscall
FAIL: 64-bit getpeername syscall
FAIL: 64-bit getsockname syscall
FAIL: 64-bit readahead syscall
FAIL: 64-bit sigaltstack syscall
FAIL: 64-bit thread_area syscall
FAIL: 32-bit syslog syscall

There is a great deal of rhyme or reasons for which syscall tests are failing.

-- 
You are receiving this mail because:
You are the assignee for the bug.