From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id BE9FA3858D33; Mon, 4 Mar 2024 16:52:25 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org BE9FA3858D33 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1709571145; bh=GfzZISyteOhDvxLhaX96ORAN1a3hP31HeC/ndP3bnr8=; h=From:To:Subject:Date:In-Reply-To:References:From; b=IOe5gOCelS8HMcSL/rjOxO3tEpjnqk1yfsGFr1EByS8m90fwDreT8cm21Ip8Lcb0M apkO938eYj9vmr/wt7r5v4BygntDtchWKYZuFrp0FBhrb4ouWdWDOjmy9FmD40lyq5 tnQeF4/rINjZgz4X0GQHkvaueUlGlF9IIcKQo+3U= From: "wcohen at redhat dot com" To: systemtap@sourceware.org Subject: [Bug runtime/31117] transport failures Date: Mon, 04 Mar 2024 16:52:24 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: systemtap X-Bugzilla-Component: runtime X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: wcohen at redhat dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: systemtap at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D31117 --- Comment #16 from William Cohen --- 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= =20 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 th= at 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 faili= ng. --=20 You are receiving this mail because: You are the assignee for the bug.=