From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 770683858409; Mon, 5 Feb 2024 15:32:51 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 770683858409 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1707147171; bh=HzPvAEEVgi6GTeBe5pHfMkPzDkRR0IZpSNA441IRue0=; h=From:To:Subject:Date:In-Reply-To:References:From; b=I6HPe4LnVVPzTVwBIVL8O0OPCXbF+ssmXpJCzzPPnxaXCRb56AEoP8krPqgdn8iJg JzADBeBUG7cSKP6sph9uFqta7zlLFcsR13CHhhsP2a5UsLswd3ECaJLPVA20Bbya8c NxN3mlv3eFnWdlDxGw3F7wf1TV8OssqNqd4mrxLc= From: "wcohen at redhat dot com" To: systemtap@sourceware.org Subject: [Bug runtime/31117] transport failures Date: Mon, 05 Feb 2024 15:32:50 +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 #15 from William Cohen --- The fix merged in helps, but doesn't eliminate all the transport failures.= =20 Looking through the RHEL8/9 runs I did this weekend see "transport failures= ".=20 Both had warning for systemtap.base PR14546. However, this test looks lik= e it might just have a huge volume of data as it is printing backtraces each tim= e an irq_* function is entered. on RHEL9 see some "transport failures" on the syscall tests: WARNING: There were 1 transport failures. Try stap -s to increase the buffer size from 16. FAIL: 32-bit chmod nd_syscall WARNING: There were 1 transport failures. Try stap -s to increase the buffer size from 16. FAIL: 32-bit handle_at nd_syscall WARNING: There were 1 transport failures. Try stap -s to increase the buffer size from 16. FAIL: 32-bit openclose nd_syscall WARNING: There were 1 transport failures. Try stap -s to increase the buffer size from 16. FAIL: 32-bit rt_signal nd_syscall WARNING: There were 1 transport failures. Try stap -s to increase the buffer size from 16. FAIL: 32-bit statfs nd_syscall WARNING: There were 1 transport failures. Try stap -s to increase the buffer size from 16. FAIL: 32-bit msg_queue syscall For RHEL8 syscall tests it looks like the return probes failed to print for mmap2 and read for these particular failures: WARNING: There were 1 transport failures. Try stap -s to increase the buffer size from 16. FAIL: 64-bit remap_file_pages syscall WARNING: There were 1 transport failures. Try stap -s to increase the buffer size from 16. FAIL: 64-bit set_tid_address syscall WARNING: There were 1 transport failures. Try stap -s to increase the buffer size from 16. Testing 64-bit setgroups syscall Looking through the results syscall tests there certainly seem to be cases where some output seems to be missing. On some seeing "WARNING: Child proce= ss exited with status 255". Might be some other issue going on with some of t= he syscall tests. --=20 You are receiving this mail because: You are the assignee for the bug.=