From: "mcermak at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/31117] New: transport failures
Date: Wed, 06 Dec 2023 15:39:43 +0000 [thread overview]
Message-ID: <bug-31117-6586@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=31117
Bug ID: 31117
Summary: transport failures
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: runtime
Assignee: systemtap at sourceware dot org
Reporter: mcermak at redhat dot com
Target Milestone: ---
Created attachment 15241
--> https://sourceware.org/bugzilla/attachment.cgi?id=15241&action=edit
testcase patch allowing to demonstrate the problem
In the recent past, there were some problems with transport failures (PR29108).
This was fixed. But apparently the situation still isn't 100% perfect.
Pretty much
all the syscall tests are now failing on RHEL-9.4 with transport failures. It
is reliably reproducible. By default, the problem is hidden in the testsuite's
expect gates. To visualize it, I've used the attached patch. With that patch
applied (on top of systemtap commit b2a1261c434788cb and
kernel-5.14.0-394.el9.x86_64), I have:
el9 x86_64 # make installcheck RUNTESTFLAGS=syscall.exp CHECK_ONLY=futex
[ ... stuff deleted ... ]
Running /root/systemtap/testsuite/systemtap.syscall/syscall.exp ...
[ ... stuff deleted ... ]
Comparing ^futex: futex \(0x0, FUTEX_CMP_REQUEUE, 1, 0, 0x[f]+, 0\) = [\-0-9]+
against futex: futex (0x0, FUTEX_CMP_REQUEUE, 1, 0, 0xffffffffffffffff, 0) =
-14 (EFAULT)
Comparing ^futex: futex \(0x0, FUTEX_CMP_REQUEUE, 1, 0, 0x0, -1\) = [\-0-9]+
against futex: futex (0x0, FUTEX_CMP_REQUEUE, 1, 0, 0x0, -1) = WARNING: There
were 1 transport failures. Try stap -s to increase the buffer size from 16.
I've tested that simpler syscall tests (e.g. those having most of their
<testcase>.c content commented out) the test result is sometimes PASS and
sometimes FAIL. But using a "normal" syscall test involving 10+ system calls
and their checks, the failure is guaranteed..
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2023-12-06 15:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-06 15:39 mcermak at redhat dot com [this message]
2023-12-06 21:17 ` [Bug runtime/31117] " wcohen at redhat dot com
2023-12-13 21:27 ` mcermak at redhat dot com
2023-12-14 20:23 ` wcohen at redhat dot com
2023-12-18 18:55 ` wcohen at redhat dot com
2023-12-21 21:43 ` wcohen at redhat dot com
2024-01-04 22:34 ` wcohen at redhat dot com
2024-01-05 14:50 ` mcermak at redhat dot com
2024-01-05 15:21 ` mcermak at redhat dot com
2024-01-08 14:56 ` wcohen at redhat dot com
2024-01-09 12:11 ` mcermak at redhat dot com
2024-01-10 12:37 ` mcermak at redhat dot com
2024-01-22 15:54 ` wcohen at redhat dot com
2024-01-23 18:24 ` wcohen at redhat dot com
2024-02-02 15:07 ` mcermak at redhat dot com
2024-02-02 15:15 ` mcermak at redhat dot com
2024-02-05 15:32 ` wcohen at redhat dot com
2024-03-04 16:52 ` wcohen at redhat dot com
2024-03-04 21:30 ` wcohen at redhat dot com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-31117-6586@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).